ICP and targeting
One big list averages your best segment away. Here's how to split target accounts into cohorts that share a problem, how many to start with, and what message each one needs.
By Satvik Luthra, Founder11 October 20269 min read
Key takeaways
Account segmentation for outbound means splitting your target accounts into small groups, or cohorts, that share a specific problem, so each group can receive one message written for that problem. It turns one large, generic campaign into a few focused ones whose results you can read and compare.
Most teams segment by whatever the data tool offers: industry, then company size. That is a start, but two companies in the same industry and size band can have completely different reasons to buy. This guide shows how to segment by problem, with a worked example, a rule of thumb for how many cohorts to run and a template for the message each one needs.
Your ideal customer profile defines which companies are worth contacting at all. Segmentation divides that list into groups that can be spoken to in the same way. A good cohort passes three tests:
If a group fails the first two tests, the message will be vague. If it fails the third, you won't learn anything from it.
Imagine you send one campaign to 2,000 accounts and get a handful of positive replies. Was the message weak? Was the list wrong? Or did one part of the list respond well while the rest ignored you?
With a single list you can't tell. A strong response from 300 accounts in one corner of the market gets averaged away by silence from the other 1,700. Teams in that position often rewrite the copy, change the offer and switch subject lines all at once, and then can't say which change mattered.
Segmenting fixes this. Each cohort becomes its own small experiment with its own message. When one cohort responds and another doesn't, you know where to put more effort, and you have a much better idea of why.
Firmographic fields like industry, size and region are good filters but weak segments on their own. Start instead with the question "why would this company care right now?" and look for groups that share the answer. Useful axes, in rough order of value for messaging:
| Axis | What it captures | Example cohort |
|---|---|---|
| Problem or use case | The specific pain your product removes | Companies reconciling invoices across many locations |
| Trigger event | A recent change that makes the problem urgent | Companies that appointed a new CFO in the last six months |
| Ownership | Pressures that come from who owns the company | Private-equity owned companies with new reporting demands |
| Operating model | How the business is structured | Multi-entity groups that consolidate several sets of books |
| Industry | Workflows and vocabulary specific to a sector | Logistics companies paying hundreds of carrier invoices a month |
| Size band | Where buying process and priorities change | Companies large enough for a dedicated AP team |
The strongest cohorts usually combine two axes: an industry or operating model to make the language specific, and a problem or trigger to make the timing relevant. "Logistics companies" is a list. "Mid-market logistics companies drowning in carrier invoices" is a cohort.
Write a short problem statement for each candidate cohort before you build any list. If you can't write one sentence that every account in the group would nod at, it isn't a cohort yet.
Here is an illustrative example using a fictional company, Ledgerly, which sells accounts payable automation to mid-market companies in the US. The numbers are sample figures for illustration, not benchmarks. Suppose Ledgerly's ICP produces a market of about 8,420 accounts and 21,900 decision-makers. Grouped by shared problem, it splits into five cohorts:
| Cohort | Shared problem | Why now | First contact | Core message angle |
|---|---|---|---|---|
| Mid-market logistics | Hundreds of carrier and fuel invoices a month, matched by hand | Volume grows faster than the AP team | Controller | Clear carrier invoices without adding headcount |
| Multi-site healthcare | Invoices arrive at each location and approvals get lost | New sites added through acquisition | VP Finance | One approval flow across every site |
| PE-backed manufacturers | New owners want faster, cleaner monthly reporting | Recent change of ownership | CFO | Close faster for the board pack |
| Multi-entity service firms | Several sets of books and intercompany bills | Expansion into new regions or entities | Finance Director | Pay and record bills across entities in one place |
| Fast-growing distributors | Seasonal invoice spikes overwhelm a small team | Peak season approaching | AP Manager or Controller | Get through peak season without late payments |
Notice that each row could support a different first sentence, a different proof point and a different offer. That is the point. If two rows would get the same email, merge them.
Ledgerly wouldn't launch all five at once. It would pick the two or three where it has the strongest evidence, such as existing customers or a sharp, verifiable trigger, and hold the rest for later.
Start with two to three cohorts, and rarely more than five. The trade-off is simple:
A practical sizing check: each cohort should have enough reachable decision-makers to run a full sequence for at least several weeks at your sending pace. If a cohort is smaller than that, merge it with a close neighbor or keep it for hand-written, account-by-account outreach.
Prioritize cohorts with a simple score
Score each candidate cohort from 1 to 3 on: evidence (do you have customers like this?), urgency (is there a clear trigger?), reachability (can you find and verify the right people?) and deal value. Start with the top two or three totals.
Each cohort gets its own message. Not a different first name and company name: a different reason for writing. Use this template to brief each one before any email is drafted:
| Field | What to write |
|---|---|
| Cohort name | Short, descriptive, used in reporting |
| Problem statement | One sentence the reader would recognize as their own |
| Trigger | What makes it timely, and how you verify it |
| First contact | Role and seniority of the person you write to |
| Proof | A relevant customer, example or fact you can stand behind |
| Offer | What you propose, made easy to accept |
| Call to action | The one question you end on |
| Words to avoid | Jargon or claims that don't fit this audience |
To see the difference, compare how Ledgerly might open the first email to two of its cohorts:
Same product, same sender, but each opener names a problem the reader would recognize and a reason it matters now. Neither would work in the other cohort.
In RevFirst, cohorts are suggested after your market is sized, you approve the ones to start with, and the offer for each is shaped with a RevFirst strategist before the first campaign. Each cohort then runs as its own campaign, so results stay separate.
Once campaigns are live, report by cohort, never only in total. For each one, track:
Then act on the differences. A cohort with good replies and good meetings deserves more accounts.
A cohort with replies but poor meetings may have the right problem but the wrong contact. A cohort with silence needs a different angle, or may simply not have the problem you assumed. Change one thing at a time so you can tell what worked.
Good segmentation is less about clever categories and more about discipline: a clear problem per group, one message per problem, and results you can read separately. Get those right and every campaign teaches you something about your market.
Free Forever plan
Enter your website and RevFirst sizes your market and groups accounts into cohorts that share a problem, for you to approve. Get started for free.