ICP vs Buyer Persona: Use Both Without Mixing Them Up

Most early SaaS teams have one document called "our customer". Half of it describes a kind of business, the other half describes a person, and nobody can tell which sentence applies when. The result is ads that target the wrong companies and onboarding that speaks to the wrong human.

An ideal customer profile (ICP) and a buyer persona answer different questions. The ICP says which businesses are worth your time. The persona says which people inside those businesses you have to convince, and what each of them cares about. Keep them apart and both become sharper.

The one-line difference

• ICP: a filter on organisations. Industry, size, how they work, what they already use, what triggers a purchase. You can check it from the outside, often before you ever speak to anyone.
• Buyer persona: a portrait of a role. What their day looks like, what they are measured on, what they fear, what words they use. You only learn it by talking to people.

A useful test: if a sentence could be verified from a business's website, a job ad or a public register, it belongs in the ICP. If it needs a conversation to confirm, it belongs in a persona.

A worked example: job management for trade businesses

Say you are building job and quote software for small trade businesses. Here is what an ICP looks like when it is doing its job:

> Plumbing, electrical and air-conditioning businesses with 4 to 15 field staff, running jobs from a mix of paper job cards, a shared calendar and an accounting package. The owner still writes most quotes. They are hiring, or they have just lost a job because a quote went out late.

Every clause there is checkable. Headcount shows up on their site or in job ads. "Hiring" shows up on job boards. "Paper job cards" shows up when you ask one question on a discovery call.

Now the personas inside that same business:

| Persona | What they do all day | What they care about | What makes them say no | |---|---|---|---| | Owner-operator | Quotes, prices, chases late payers, still on the tools some days | Getting quotes out faster, cash coming in | Anything that takes a weekend to set up | | Office manager | Books jobs, answers the phone, reconciles invoices | Fewer calls asking "where is the tech?" | Double entry into the accounting package | | Field technician | Drives between jobs, takes photos, fills in job cards | Finishing the job and going home | An app that needs signal on a roof |

Same business, three very different conversations. The owner signs. The office manager decides whether it actually gets used. The technician can quietly kill it by never opening the app.

What each one is for

Mixing them up usually means using one where you needed the other. A simple way to keep them straight:

Use the ICP for:

• Deciding who to contact, list or advertise to.
• Qualifying inbound interest ("is this business worth a demo?").
• Choosing which beta applicants to accept.
• Saying no to feature requests from businesses outside the profile.

Use personas for:

• Writing landing page copy and onboarding emails.
• Deciding which screen someone sees first after signing up.
• Preparing for a sales call ("the office manager will ask about the accounting export").
• Interpreting feedback ("this complaint came from a technician, so it is about field use, not reporting").

If you find yourself writing copy from the ICP, it will read like a market report. If you target from a persona, you will end up with a list of people with the right job title at companies that will never buy.

How they drift apart, and why that is useful

Early on, your ICP and your primary persona often look like the same thing, because the owner is the buyer, the user and the admin. A two-person bookkeeping practice is like this: the principal chooses the software, uses it daily and pays the bill.

As you move up in size, they separate. At a bookkeeping firm with twelve staff, the principal still signs, but a senior bookkeeper runs the evaluation and the juniors do the daily work. Your ICP might barely change (still bookkeeping firms, still on the same ledger software), but you now need three personas instead of one.

That drift is a signal, not a problem. When a new persona keeps turning up in calls, it usually means the business size in your ICP has quietly shifted. Update the ICP deliberately rather than letting the product get pulled toward whoever shouts loudest.

Common mistakes

1. Fictional personas. "Sarah, 38, loves yoga and drinks oat lattes" tells you nothing about how she evaluates software. Keep personas to work: goals, constraints, triggers, objections, vocabulary.
2. An ICP with no exclusions. A good ICP says who you are not for. "Not for businesses with a dedicated IT person" is often more useful than the inclusion criteria.
3. Personas without evidence. Each line in a persona should trace back to at least one real conversation. If it came from brainstorming, mark it as a guess.
4. One persona per company size. Personas are roles, not segments. The office manager at a four-person electrical business and at a fifteen-person one have more in common with each other than with their own bosses.
5. Never revisiting either. Review both after every batch of five to ten customer conversations. Rules of thumb only, but if nothing has changed in a quarter, you probably have not been listening.

A template you can fill in this week

ICP (one paragraph, all checkable):

• Industry and sub-type:
• Size (staff, locations, vehicles, chairs, whatever the natural unit is):
• Current tools and workarounds:
• Trigger that makes them look for something new:
• Who we are not for:

Persona (one per role, half a page each):

• Role and what they are measured on:
• A normal day, in their words:
• The task this product touches, and how they do it today:
• What would make them champion it internally:
• What would make them quietly ignore it:
• Words they use (and words that make them switch off):

Write the ICP first. Then write personas only for the roles you have actually met inside ICP businesses.

Where LetsBeta fits

On LetsBeta, businesses apply to try your build and you accept or decline each application. That is your ICP at work: if you have written down who you are for, and who you are not for, the accept or decline decision takes seconds instead of a debate.

The personas show up in the reports. Every Early Adopter sends a mid-trial and an end-of-trial report covering what worked, what broke, whether they would pay and what price seems fair. Reading those alongside who in the business filed them tells you which persona you are winning and which one is quietly giving up.

If you are still unsure which businesses to start with, the Demand board shows what businesses are asking for, grouped by category, in their own words. It is a decent place to sanity-check whether the ICP you wrote exists outside your head.

For the next step, read Beachhead Market: How to Pick the First Segment You Can Actually Win, then turn your ICP and lead persona into a single line with How to Explain Your Startup in One Sentence.