finding your ICP · who exactly is this for?

The who behind every link in the Distribution Chain. What an ICP actually is, the six questions that produce one, and a full worked example deriving Mailover's ICP from its own website and feature list.

This essay is part of the Solving Distribution chain framework. The ICP is box one of every distribution attempt, and the input Link 2: Messaging runs on.

The Distribution Chain: the who behind every link

For a long time, if you had asked me who Mailover was for, I would have said: busy professionals who get too much email.

A version of that phrase is on the front page right now, as “1,000+ working professionals”.

That answer is true, and it’s worthless.

You can’t buy an ad against busy. There’s no room where the overwhelmed gather. No search box anywhere has a filter for “too much email”. Every word of that sentence describes a feeling, and feelings aren’t addressable.

Look back at the four parts of a single attempt: who → where → hook → action. The ICP is box one. Get it wrong and the other three boxes inherit the mistake. The hook talks past the reader, the channel is full of the wrong people, and the action never happens. You’ll spend months tuning boxes two and three because they’re the ones you can see.

So this piece is about box one.

what an ICP actually is

Here’s the definition I use:

Your ICP is the smallest group you can describe precisely enough to find, who feel the problem often enough to pay for it every month.

Two conditions, and you need both.

Findable. Every attribute has to survive being turned into a filter. LinkedIn will let you filter for a headcount of 11 to 50, a title of Chief Operating Officer, and a company founded after 2020. It has no filter for overwhelmed. The App Store will rank you against the keyword “email”. Reddit will hand you r/msp and r/agency whole. If an attribute can’t become a filter somewhere, it can’t become a channel, and it doesn’t belong in the sentence.

Hurting on a schedule. A monthly subscription needs at least a weekly pain. Daily is better. A problem that shows up twice a year gets solved by a spreadsheet and forgotten, no matter how much it stings when it happens.

Four words get used for the same thing and they aren’t the same thing:

Term	What it means	What it’s for
TAM	everyone who could conceivably buy	fundraising slides
Segment	a slice of the market with shared traits	deciding where to look
ICP	the slice you can find, who pays and stays	every decision in the chain
Persona	one imagined human inside the ICP, with a name and a bad Tuesday	writing the actual words

The ICP is the one that does the work. The persona is downstream of it, and TAM is mostly theatre.

the twenty names test

Here’s how to know whether you have one.

Can you write down twenty real people or companies that match your ICP, by name, by Friday, without buying a list?

If yes, you have an ICP. If no, you have a demographic. Demographics feel like knowledge and behave like fog: you can describe them all day and still not be able to reach a single one on Monday morning.

Those twenty names are also your first twenty sales calls. The test hands you the work as a side effect.

where an ICP comes from

Not from a brainstorm. Founders invent ICPs in a doc, and inventing is exactly the wrong verb. You already hold three pieces of evidence, and they’re better than anything you’d imagine.

Who paid, and stayed. Not who signed up. Retention is the filter that separates a curious visitor from a customer, which is why Link 1 sits upstream of this work.
What your product can do that few others can. Your feature list is a description of your customer, written in the wrong language.
Who your price lets in the door. Price decides whether one person can say yes alone or a committee has to.

Run those three against each other and the overlap is your answer.

the six questions

Work through these in order. Each one narrows the last.

1. Who paid, and stayed past 90 days? Sort your paying cohort by retention and look at the top decile. Job title, company size, what they were doing the week they signed up. If you have no paying users yet, use the ones who tried hardest to get in.

2. What does your product do that only a certain kind of person needs? Take your feature list and ask, one row at a time, who had to exist for this to get built. Most of the list is table stakes and tells you nothing; a login screen implies no one. You’re hunting for the handful of features that would be pointless for most of the market, because those are the ones somebody built on purpose, for somebody specific, usually without writing down who. Then do the same pass over what you deliberately didn’t build. The gaps are louder than the features, and they’re more honest, because nobody writes marketing copy about the thing they left out.

3. Who can say yes alone at your price? Under about €50 a month, one person decides with a personal card. Over a few hundred, someone has to ask a manager, and you’ve quietly signed up for a security questionnaire and a six-month cycle. Your price already chose your buyer.

4. What has to be true about their week? How often does this hurt, and what are they doing about it today? If the honest answer is that they live with it, the pain isn’t acute enough to bill for monthly.

5. Where do they already concentrate? Turn every attribute into a filter. If none of them produce a list, go back to question one.

6. Who is it explicitly not for? Write the anti-ICP. This is the most useful and most skipped step. The anti-ICP is what keeps you from optimising for the loudest user instead of the best one, and it’s what lets your landing page turn people away before they burn a trial.

Then write it as one sentence a stranger could check you on.

a worked example: deriving Mailover’s ICP

Mailover is an AI email client. It reads your inbox, pulls out the things you have to do with their deadlines, writes two-line summaries of the threads that matter, and files the rest. The headline on the site is “Your inbox has a to-do list buried in it.” It runs on the web and iOS, connects Gmail, Outlook and IMAP, and the plans go from $7.50 to $41.67 a month.

Let’s run the six questions against nothing but what’s public: the website and the 55-item feature page.

1. who paid and stayed

The public evidence is three named customers: a COO, an engineering leader, and a founder. The site says operators at fast-moving companies run their inbox on Mailover, and claims 1,000+ working professionals and 2M+ emails processed.

“Working professionals” is the fog again. But look at what those three named people have in common instead of what they’re called. Each one is a bottleneck: work waits on their answer. None of them has an assistant reading ahead of them. And each almost certainly runs more than one mailbox.

Hold that thought, because the feature list confirms it.

2. read the features backwards

This is the step nobody does, and it’s the highest signal one. Fifty-five features, and each one is a bet someone already made about who this is for.

Plans sold by inbox count (2, 4, 8): the product assumes more than one mailbox. Someone with a single work address is buying a discount on a product built for someone else.
Gmail, Outlook and plain IMAP: work mail and personal mail in the same brief. That’s a person whose life and job both arrive by email, on accounts nobody’s IT department manages.
Deadlines extracted from the body of a message: the marketing copy’s own example is turning “please counter-sign before Friday” into a task. That’s contract mail, invoice mail, recruiting mail. Mail from outside the company that creates an obligation you personally own.
AI credits at 600, 1,500 and 6,000 emails a month: roughly 20 to 200 emails a day. That’s a stated volume band. Below it, nothing hurts enough. Above it, you have a team and you delegate.
Tone-of-voice profile, suggested replies, secretary personalities: built for someone who still writes their own replies, at volume.
Zero-access encryption, blocked senders, 7–90 day auto-delete, GDPR export: someone with a concrete reason to care what a third party can see. Legal, finance, HR, board mail.

Now the more revealing half: what isn’t there. No shared team inbox. No assigning a thread to a colleague. No SLA timers. No CRM sync.

Those absences rule out the two biggest email-tool markets in one stroke: support teams and sales reps. The product was built for one person, working alone, who is the bottleneck.

3. who can say yes alone

$7.50 to $41.67 a month is a personal card. No procurement, no budget holder. That price says the buyer is an individual, even when they work at a company, and even when the company would benefit.

There’s also an Enterprise tier on the page, with custom pricing and unlimited inboxes. I’d take it down. It’s a different buyer, reached a different way, with a procurement cycle and a security review attached, and every hour it earns you is an hour stolen from the buyer who can already say yes in thirty seconds. A “contact us” button on a $12.50 product mostly serves as a place for the founder’s hope to sit.

4. what’s true about their week

The site is unusually specific about the pain: 5% of email needs you, 7% you want to see, 88% is noise. So the week looks like this. A few hundred messages arrive. A handful contain a commitment with a date on it. Missing one of those handful costs real money or real credibility. And the person has no one to hand it to.

Trigger: every single morning. That’s what a subscription needs.

5. where they concentrate

Turn the attributes into filters and see which ones survive.

Runs 2+ mailboxes → founders, agency and studio owners, consultants, fractional operators, anyone with a personal address and a company address and often a billing@ too.
No assistant → companies under roughly 50 people, or self-employed.
Personally on the hook for external deadlines → founders, ops leads, recruiters, anyone who signs things.
Already looking → App Store search for “email”, r/productivity, the build-in-public side of X, indie founder communities, agency owner groups.

Every one of those is a place you can actually go on Monday. Compare that to “busy professionals”, which is a place you can never go.

6. the anti-ICP

Who should be told, on the landing page, that this isn’t for them?

Employees at big companies: their IT blocks third-party mail access. They’ll love the demo and never get past the OAuth screen, and this failure is invisible in your funnel because it looks like a signup that just went quiet.
Anyone with an actual assistant: the problem is already solved by a human who’s better at it.
People getting 20 emails a day: the pain doesn’t clear the bar for a monthly charge.
Support and sales teams: they need a shared inbox and assignment, which the product deliberately doesn’t have.
Anyone whose inbox is mostly internal notifications: Jira and GitHub noise is a filter rule, not a job for an AI secretary.

the sentence

Put it together:

Founders and operators at companies of 2 to 50 people who run at least two mailboxes themselves, get 100+ emails a day, have no assistant, and are personally on the hook for deadlines that arrive from outside the company.

Every clause is checkable. Someone either has two mailboxes or they don’t. Either they have an assistant or they don’t. You can disagree with the sentence, which is the point: an ICP you can’t be wrong about is an ICP that can’t teach you anything.

the part I’d bet against

The weakest clause is company size. I put 2 to 50 people in there because that’s roughly where nobody has an assistant, but the real predictor might be mailbox count on its own, and mailbox count doesn’t care who signs your payslip. A freelance recruiter contracting inside a 4,000-person firm runs three inboxes and still has nobody to hand them to. If the retention data says mailbox count alone explains it, the size clause comes out and the market gets several times larger overnight.

And a limit that applies to this whole walkthrough. I derived all of it from a public website, which means I derived it from a hypothesis someone already committed to. Marketing copy is a claim about the customer, and a claim isn’t evidence. The thing that settles it is question one, sorting the paying cohort by 90-day retention and reading the top decile, which nobody outside the company can do. So this is the fastest route to a sentence worth testing, not proof of anything.

what changes if you accept it

This is the part that makes the exercise worth doing. A real ICP reaches back up the chain and rewrites things.

Messaging: “1,000+ working professionals” becomes the actual role. The multi-inbox capability moves from a line on the pricing table to the headline, because it’s the thing the ICP has that nobody else does.
Activation: the aha moment needs two mailboxes, so onboarding should ask for the second one on day one instead of celebrating the first. Half the value is invisible to a user with one account connected.
Product: the anti-ICP tells you what not to build. No shared inbox. No assignment. Every hour spent on those serves people who were never going to stay.
Channel: App Store keywords and founder communities, rather than generic productivity ads pointed at everyone with a job.
Honesty on the page: saying “if your company’s IT manages your mail, this probably won’t connect” saves you the trial signups that were always going to die at the OAuth screen, and saves those people twenty wasted minutes.

One sentence, five decisions. That’s the leverage.

redefining an ICP you already have

Most founders don’t need to find an ICP from nothing. They need to correct one they guessed at a year ago and never revisited.

Slow growth on its own tells you nothing here. The real signal is a specific disagreement between your sentence and your data:

Your best-retaining cohort has a different job title than your landing page. Trust the cohort. The page is a hypothesis and the cohort is a result.
Your support burden concentrates in a segment that also churns. You’re being pulled toward your worst customers because they’re the loudest.
One attribute predicts everything. If users with two inboxes retain at triple the rate of users with one, that attribute is the whole ICP, and it belongs in the first clause of the sentence.

Then move carefully, because this is the most expensive change on the chain. Changing your ICP invalidates your messaging, most of your channel work, and part of your roadmap. It’s cheap to get right in month one and brutal in year three.

So change the sentence when the data says so, and change it fully. A landing page written for last year’s ICP and a product built for this year’s is the worst of both.

the template

Fill this in for your own product. If any blank makes you uncomfortable, that discomfort is the finding.

[role] at [company type and size] who [observable situation], feel [specific pain] [how often], and today handle it with [current workaround]. Not for [anti-ICP].

Then run the twenty names test on it. If you can’t fill a list by Friday, the sentence is still describing a feeling.

The market doesn’t get bigger because you describe it vaguely. It just gets harder to find.

Write the sentence. Then go find twenty of them.