# How to organize LinkedIn leads for different outreach sequences
> Group LinkedIn leads by pain point, intent and persona, then point separate outreach sequences at each group without duplicating lists or messaging the same person twice.
- HTML: https://getkinlead.com/ai-sdr-lead-group-management
- Markdown: https://getkinlead.com/ai-sdr-lead-group-management.md

**Short answer:** Group prospects by the pain they have, the intent they show and the role they play, then point each outreach sequence at a separate group. Keep one master set of leads and move people between groups instead of copying lists, so nobody receives two offers at once.

## Define your lead segments

Most people start with job title. Title tells you who someone is, not why they should reply. A Head of Sales at a 10-person software company has a different week from a Head of Sales at a 500-person logistics firm. If both get the same sequence, the message has to be broad enough to fit both, which makes it easy to ignore.

Start with the problem that makes someone take a meeting. That might be a manual process, a missed handoff, a tool that costs too much or a report nobody trusts. Then note the intent you can see: they commented on a competitor post, they visited your pricing page, they downloaded a guide, or they came from a cold search with no prior signal.

Write the segment as a short sentence you can say out loud: 'Sales leaders at 10 to 50 person SaaS companies who complain about pipeline reviews' or 'Agencies that post about client reporting and mention a competitor.' If the sentence needs three 'and' clauses to work, split it. A segment should give one campaign one clear reason to exist.

| | Segment type | What you use to group leads | What the sequence does |
| --- | --- | --- | --- |
| Pain point | A repeated problem in posts, comments or calls | Names the problem and shows a fix |
| Intent | A visible action: competitor comment, pricing visit, event, reply | Opens with that action and moves to the next step |
| Persona | Role, seniority or department | Changes tone, proof and ask |
| Stage | Trial, former customer, current customer, cold | Avoids repeating a pitch they already rejected |

## Map your sequences to your groups

A sequence is a promise with a schedule. It should match the reason the lead entered the group. Someone who commented on a competitor's post already knows the category exists. Your first message can mention the post, the argument and the gap you saw. A cold search lead needs a reason you picked them out of everyone else.

Write the first line before you write the follow-up. If the first line could be sent to any lead in your file, the group is too broad or the hook is too weak. The follow-up then advances one idea: a proof point, a question, a short case, a meeting ask. Keep the same group through the sequence so the message stays coherent.

**One list for every sequence**

- Sending 'we help teams grow' to a competitor commenter and a cold lead.
- Using the same proof for a 10-person team and a 500-person team.
- Changing the offer in every follow-up because the group has no focus.

**Sequence tied to a group**

- Competitor commenters get an opening that names the thread they joined.
- Cold search leads get an opening that names the observation you made on their profile or company.
- Former customers get a check-in that references what changed since they left.

## Name groups so the sequence is obvious

You will forget what 'Group A' means two weeks later. Give every group a name with the segment, source and date or owner. A useful pattern is source, segment, reason: 'Competitor comments, RevOps leads, Acme.' Keep the name short enough to scan in a dropdown but specific enough that you can tell two similar groups apart.

Keep a short note in your own tracking doc for every group. The note should answer three questions: who is in it, how they got there, and what sequence points at it. That context is what lets you reuse the group later. When a campaign ends, update the note with what happened. Future you will need that context.

Use the same naming rule for campaigns. A campaign name like 'Q3 cold SaaS founders, observation hook' tells you the audience, quarter and angle. A name like 'Campaign 4' tells you nothing. If you have to open three screens to remember what a campaign does, rename it.

- Group name: source, segment, reason. Example: 'Competitor comments, agency owners, Acme.'
- Group note: who is in it, how they arrived, which campaign is active.
- Campaign name: audience, angle, month. Example: 'Agency owners, reporting hook, March.'

## Move leads between sequences

Your groups will go stale if they never change. People change roles, companies change priorities, and a lead who ignores one angle may reply to another. No reply is not always a no. It can mean the hook missed, the timing was wrong, or the person was not the buyer.

Move a lead only after the current sequence has stopped. If you move someone while a campaign is still queued to message them, they can get the old message after the new one. That looks careless and makes the data unreliable. Decide the rule now: a lead can sit in several groups for reporting, but only one active campaign can point at them at a time.

1. **Find the leads who stalled.** Filter the active campaign for people who fit your profile but did not reply after the planned follow-ups. Do not move people who replied and said no. Mark those as closed.
2. **Stop the old sequence.** Pause the campaign or remove those leads from the active set. Wait until no queued message remains for them.
3. **Choose the next reason.** Pick a different problem, a different proof point or a different role. Write the new opening before you create the group. If you cannot name the new reason in one sentence, do not move the lead yet.
4. **Point one campaign at the new group.** Start with a small batch, read the replies and edit the next queued messages. Keep the old group for history so you know which angle was already tried.

## Avoid the duplication trap

Copying a master list into three files feels tidy. It creates three versions of the same person. If two campaigns are active, the lead can receive two different openers on the same day. Even if the messages are good, the experience is bad, and your notes split across files.

Keep one lead record and use groups as views. A group should point to leads, and a campaign should point to a group. When you want to test a new offer, create a new group from the same source, exclude anyone already in an active sequence, and point the new campaign there. Export when you need a snapshot for reporting, not as your working copy.

> One lead, one active sequence. Use groups as pointers and exports as snapshots, so two campaigns never message the same person at the same time.

## Doing this with Kinlead

Kinlead keeps leads in lead groups and lets any campaign point at any group, so you do not clone lists to test a new angle. Lead search uses LinkedIn's standard search, so you can build a group without a Sales Navigator seat, or import a CSV of LinkedIn profile URLs. Kinlead scores each lead from 0 to 100 against the profile you describe and does not keep leads below the fit line.

For intent groups, the [Steal Customers agent](/features/steal-customers) watches competitor company pages and optional founder or employee profiles, reads comments on recent posts, and turns commenters who look like buyers into leads. Each lead keeps the post URL, what the post was about and what they commented, which gives your first line a real detail to use.

1. **Build the group.** Use lead search, your website or a CSV import. Name the group by source, segment and reason so the campaign target is obvious.
2. **Point a campaign at it.** Any campaign can point at any group. Pause the campaign or read and edit queued messages on the Actions page before they send.
3. **Handle replies in one place.** Replies from every campaign land in one inbox classified by intent. Choose hand-off at the first reply, AI until real interest, or AI until a meeting is booked with your scheduling link.

- **you:** Hi Sarah, I saw your comment on the Acme post about API docs drifting out of date. We handle that by generating the docs from the same source as the code. Worth a look?
- **them:** That is a real pain for us. How much setup does it take?
- **you:** Mostly a one-time connection to your repo. I can show you the flow on Tuesday if you have 15 minutes.

## Related

- [Lead groups and scoring](https://getkinlead.com/features/lead-groups-and-scoring.md)
- [Campaigns and send windows](https://getkinlead.com/features/campaigns-and-send-windows.md)
- [Book a demo](https://getkinlead.com/demo.md)

## Common questions

**Can one lead sit in more than one group?**

Yes. Groups are views for organization. Keep only one active campaign pointing at that lead at a time so they do not get two sequences at once.

**What should I do when a lead says no?**

Close the lead for that offer and note the reason. Do not move them to a new sequence right away. A clear no is different from silence.

**How often should I review groups?**

Review before each new campaign and after every batch of replies. Reuse groups that use the same reason and remove groups that no longer have an active campaign.

**Can I export a group to CSV?**

Yes, export groups to CSV when you need a snapshot for reporting or a review with someone else. Keep the group as the working source so the snapshot does not become a second master list.

[Create a Kinlead account](https://getkinlead.com/signup) or [book a call](https://getkinlead.com/demo) to talk through pricing and setup.
