# Checklist for segmenting AI lead groups
> Learn how to split LinkedIn leads into groups by persona and problem, write a prompt for each group, and test one segment before you send at volume.
- HTML: https://getkinlead.com/checklist-for-ai-lead-group-segmentation
- Markdown: https://getkinlead.com/checklist-for-ai-lead-group-segmentation.md

**Short answer:** Split LinkedIn leads into groups built around a buying situation, not a job title. Each group gets its own problem statement and its own prompt, and you test the group on 15 to 20 leads before you scale it.

## Define personas as buying situations, not job titles

A title tells you someone's rank. It doesn't tell you what they'll buy this quarter. Two sales directors on the same list can be in completely different places: one is backfilling a rep who quit, the other is building a team from scratch and has never bought a tool like yours. Send both the same message and one of them reads something written for someone else.

Write each persona as one sentence that combines role, company shape and something that changed recently. 'Head of marketing at a 50 to 200 person SaaS company that just hired its first sales rep' is a group you can search for and write to. 'Marketers' is a group you can only send generic mail to.

Three or four personas is enough for a first pass. If you can't place a lead after reading their profile, put them in a file called later. A lead that fits no group will pull your messages toward average.

**Title only**

- Marketing managers (no shared problem)
- Founders (company sizes from one person to two thousand)
- HR professionals (hiring, benefits and compliance in one bucket)

**Situation added**

- Demand gen managers at Series A SaaS companies hiring their first SDR
- Owners of 10 to 50 person agencies who run delivery and sales themselves
- HR directors at hospitals with 400 or more beds that posted nursing roles this month

## Map each persona to one problem you can say out loud

Write the problem in the prospect's words. 'Pipeline coverage' is your word. 'My reps book meetings that never close' is theirs. If you can't say the problem in one sentence without jargon, the group is still too wide.

Keep one problem per group. If a persona has two problems, that's two groups. The prompt you write later needs a single hook, and a hook that tries to cover two things covers neither.

| | Persona | Problem in their words | Opening line |
| --- | --- | --- | --- |
| Demand gen manager, Series A SaaS | Paid leads arrive and nobody follows up | You're hiring an SDR while running the same paid channels. Who touches those leads now? |
| Agency owner, 10 to 50 people | Every new client adds another project manager | You posted about a fourth PM hire this year. Is delivery growing faster than the team? |
| HR director, large hospital | Nursing roles stay open for months | The same three nursing posts have been up since spring. Is the bottleneck interviews or offers? |
| VP sales, 200+ person software company | Forecasts miss by a wide margin | Your Q3 post mentioned a forecast miss. Are reps calling deals late, or are the deals not there? |

> A segment is only real when you can write a first line that would be wrong for every other group on your list.

## Split your master list before you write a word

Most teams build one big file, upload it into a tool, and write a campaign that has to work for everybody in it. Sorting after the campaign is live means editing a queue instead of a spreadsheet.

Start from a search export, a CSV of profile URLs, or a saved list. Label the first hundred rows by hand, using the profile and not the headline. After that the patterns are obvious and you can move faster.

1. **Export the profile URLs.** Save your search or list as a CSV with one profile URL per row. Put the date in the file name so you know which version you're working from.
2. **Add a segment column.** Name the values after your persona sentences, not after your product lines. The label should describe the buyer, not what you sell them.
3. **Label from the profile, not the headline.** Open the profile. Look at company size, tenure, recent posts and open roles. Headlines are often written for investors and recruiters, not for you.
4. **Split into one file per segment.** Each group gets its own CSV. Keep a later file for people you couldn't place and revisit it when you add a persona.

## Write a prompt that carries the segment with it

AI writes to the level of detail you give it. 'Write a friendly message about our platform' produces a message that fits nobody, and the model has no way to know which of your four groups it's talking to.

A prompt for one group carries four things: the persona sentence, the problem in their words, one piece of evidence about that specific lead, and what you want them to do. Evidence is what makes a first line believable. A comment on a competitor's post, a job ad, a post they wrote last week, a role change. If you have no evidence for a lead, don't put them in a personalised campaign. Send a plain note or leave them out.

- **draft:** You commented on Northwind's post about leads sitting in a queue. We flag every lead nobody touched in 24 hours inside the CRM. Is the gap here follow-up or routing?
- **them:** Routing, mostly. Reps pick from the top of the list and the rest goes cold.
- **you:** That matches what demand gen teams tell me most weeks. Worth 15 minutes on Tuesday or Thursday to look at how the queue gets assigned?

```
You are writing one LinkedIn connection note for a segment.

Segment: [persona sentence]
Their problem, in their words: [one line]
What we do about it: [one line, no adjectives]
Evidence about this lead: [post, comment, job ad or role change]
Goal: [start a conversation / book a 15 minute call]

Rules:
- Open with the evidence, not with us.
- Under 200 characters.
- No compliments about their profile.
- No words they would not use themselves.
- One sentence of context, one question.
```

## Test a segment before you send at volume

Take 15 or 20 leads from one group and read the generated opening lines as a block, not one at a time. Three lines in a row that start the same way means the prompt is loose or the group is too wide. A line that repeats someone's headline back at them means the model had no evidence and filled the gap with their profile.

Send that batch and read the replies. If people answer with a different problem than the one you led with, you found a better segment. Rename the group and rewrite the problem line to match what they actually said.

Keep the version of the prompt that produced the replies. Prompts drift as people edit them, and a group that worked in one quarter often needs rewriting in the next.

> Judge a segment by the replies, not by how tidy the spreadsheet looks. A clean list of the wrong people is still the wrong people.

## Decide what to do when a group goes quiet

A group that got answers in spring can go silent in summer. Check the boring things first: are those leads still in the role, is the campaign still running, does the send window match their time zone. Then read the last twenty replies as a set. If three people raised the same objection, that objection belongs in the prompt, not in your follow-up.

Pick one change and give it a week. Changing the evidence, the problem line and the tone at once tells you nothing about which one mattered.

**Follow-ups that add nothing**

- Just checking in to see if you saw my last message.
- Bumping this to the top of your inbox.
- Did you get a chance to look at what I sent over?

**Follow-ups that use what they told you**

- You said routing was fine and the problem was reps never seeing the lead. Is that still true this quarter?
- Two SDR roles went up on your careers page since we spoke. Does that change who owns follow-up?

## Doing this with Kinlead

Kinlead handles the sorting if you describe the customer up front. It finds people on LinkedIn who match the description or your website and scores each lead from 0 to 100 against that profile. Leads below the fit line aren't kept.

From there, one campaign per group:

1. **Keep leads in groups.** Leads live in [lead groups](/features/lead-groups-and-scoring). Any campaign can point at any group, and leads can be exported to CSV or imported from a CSV of profile URLs.
2. **Watch competitors for buying signals.** The [Steal Customers agent](/features/steal-customers) watches competitor company pages and optional founder or employee profiles, reads the comments on their 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.
3. **Write the campaign once per group.** [AI outreach](/features/ai-linkedin-outreach) writes notes under 200 characters from the campaign's goal, tone and your own sales playbook. Queued messages can be read and edited on the Actions page before they send.
4. **Choose how replies are handled.** Hand the conversation to you at the first reply, let the AI reply until there's real interest, or let it reply until a meeting is booked on your scheduling link. Replies from every campaign land in [one inbox](/features/unified-inbox).

## Related

- [Lead groups and scoring](https://getkinlead.com/features/lead-groups-and-scoring.md)
- [Steal customers agent](https://getkinlead.com/features/steal-customers.md)
- [AI LinkedIn outreach](https://getkinlead.com/features/ai-linkedin-outreach.md)

## Common questions

**Should I segment by industry or job title?**

Segment by the problem. A VP of sales in healthcare and a VP of sales in fintech with the same problem belong in one group. If the problems differ, split them.

**How many lead groups are too many?**

One group per script you can actually write. If you can't produce a different first line for a group, it's too small to stand alone.

**Can I reuse one message across two personas?**

You can, and the message will read as written for neither of them. The specific line is what earns the reply.

**What do I do with leads that fit no group?**

Put them in a later file and leave them out of personalised campaigns. Revisit the file when you add a persona, or send a plain note without a hook.

**How often should I rewrite a segment prompt?**

When the replies change. If people start answering with a different objection, rewrite the problem line first and leave the rest alone for a week.

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