Ideal customer profile and buyer persona at a glance
The ideal customer profile glossary entry defines the profile as a description of the type of organisation most likely to buy, to succeed with what it buys, and to stay and grow, and it sets the two documents apart in one short paragraph. The tutorial on building an ideal customer profile from CRM data shows how the profile is made: from the accounts that renewed and paid back, compared with those that did not, written as fields and disqualifiers that two people applying it to the same company would read the same way. This page does not repeat that method.
The buyer persona glossary entry defines a persona as a research-based profile of one type of customer, usually a page long, about buying rather than lifestyle. In a business sale the buyer is a group, so a single persona per product rarely works; the guide to researching B2B buyers covers how to hear from each role in a Buying CommitteeThe group of people in an organisation who influence, evaluate and approve a purchase., and its findings are the material personas are written from. This page does not repeat that method either.
What neither of those pages does is set the two documents side by side as working tools: which decisions each one drives, which evidence each is built from, where each lives in the systems a team uses, and how they connect. That is the job here. The difference in one line: the profile is a filter on organisations, applied before any conversation; a persona is a brief about a person, used in every conversation after that.
Compare table
Ideal customer profile (ICP) vs Buyer persona
| Row label | Ideal customer profile | Buyer persona |
|---|---|---|
| What it describes | A kind of organisation that buys, succeeds and stays | One role inside those organisations, and how that person approaches the purchase |
| Unit | The account | The person, or the role they hold |
| Evidence it is built from | CRM outcomes: renewal, payback, expansion and churn, plus win and loss reviews | Interviews and research with people in the role, sales and support conversations, the words buyers use |
| Who usually owns it | Marketing and sales together, with finance and customer success agreeing what "good" means | Marketing or product marketing, with input from sales and research |
| Decisions it drives | Which accounts to pursue, which leads to pass on, which to let go | What each role hears, which proof it needs, which channel and moment reach it |
| Where it lives in systems | Account fields in the CRM, fit points in scoring, routing rules, the target account list | Briefs, messaging matrices, content plans, sales talk tracks, contact-level role fields |
| How often it changes | At a set review, once a new group of customers has reached renewal | When research shows a role's concerns or vocabulary have shifted |
| How it fails | Written from ambition: impressive logos instead of retained accounts, no disqualifiers | Written from guesswork: invented names, hobbies and a photo, nothing that changes a decision |
| What it cannot tell you | What any one person in the account needs to hear | Whether the company that person works for is worth selling to |
| Typical length | A short list of checkable fields and disqualifiers | About a page per role |
Two rows carry most of the difference. The unit row explains why the documents cannot substitute for each other: a profile cannot brief a writer, because companies do not read emails, and a persona cannot filter a list, because a person's worries say nothing about whether their employer will renew. The "what it cannot tell you" row is the mirror image, and it is the most useful test when a team is unsure which document a question belongs to.
When to choose Ideal customer profile
Reach for the profile whenever the question is about organisations. Choosing a target account list is the obvious case, and the account-based marketing guide uses the profile as the fit test before any account is tiered. The same applies to paid targeting by company attributes, to deciding which inbound enquiries go to a seller, and to agreeing with sales which leads should be politely declined.
Lead scoringAssigning points to leads for fit and behaviour to decide which are ready for sales. is where the profile does most of its daily work. The lead scoring guide separates fit from intent and notes that fit points are only as good as the profile behind them. Company-level fit, such as sector, size, region and systems in use, comes straight from the profile's fields, and a disqualifier should remove points or keep the lead out of the sales stage however active the person has been.
The profile is also the right document when the question is "where should we grow?". Sizing what is left after the disqualifiers, deciding whether a new segment deserves its own programme, and choosing between broad and narrow plays all start from which organisations the business is for. The comparison of account-based marketing and demand generation weighs those two kinds of play; both depend on the profile, one applying it to named accounts and the other to the market as a whole.
When to choose buyer persona
Reach for a persona whenever the question is about what a person needs to hear. Writing a campaign, planning content for one stage of a decision, preparing a sales call, choosing the proof for a landing page or deciding which role an event invitation should address are all persona questions. The profile has nothing to say about any of them, because it stops at the edge of the organisation.
In business buying the persona question is plural. The approver wants the case made and the risk removed, the daily user wants an easier week, the technical reviewer wants specific questions answered, and the champion needs material to make the case internally. Each role that shapes the decision may need its own persona, and the order in which they meet the business matters as much as what each one hears. The roles a persona set should cover are the ones the research found at accounts inside the profile, not every job title that has ever filled in a form.
Personas also guide person-level fit. A lead with the right company and the wrong role is a common source of disappointment, and naming which roles shape the purchase lets scoring give role fit its own points, separate from company fit. The comparison of buyer personas and jobs-to-be-done covers a different question, how a persona relates to the progress a buyer is trying to make; the jobs-to-be-done framework is the way to keep each role's persona anchored on the job that person is trying to get done rather than on demographic colour.
Decision table
| Situation | Use | Why |
|---|---|---|
| Building or pruning a target account list | Ideal customer profile | The list is the profile applied to named organisations |
| Setting fit points for companies in lead scoring | Ideal customer profile | Company fit and disqualifiers come from its fields |
| Deciding whether a lead's job title should score | Buyer persona set | Personas name the roles that shape the purchase |
| Writing an email sequence or ad for one role | Buyer persona | Message, proof and vocabulary change by role |
| Routing inbound enquiries to sellers | Ideal customer profile | Routing reads account fields, not the person's concerns |
| Preparing a seller for a first meeting | Both | The profile says why the account fits; the persona says what the person cares about |
| Choosing which roles to interview in research | Ideal customer profile, then the research | Recruit from accounts inside the profile so personas describe the right buyers |
| Deciding whether to enter a new segment | Ideal customer profile | It is a question about organisations, not people |
| Planning content for each stage of a long decision | Buyer persona set | Different roles join the decision at different stages |
From profile to personas: one targeting chain
The two documents work best as two links in one chain rather than as rival descriptions of the customer. The chain starts higher up: the segmentation guide covers how a market is divided and which segmentsDividing a market or customer list into groups that need different offers or messages. are chosen, and the STP framework is the sequence behind that choice. Inside a chosen segment, the profile narrows the field to the organisations most likely to buy, succeed and stay, and names the traits that rule an account out.
The profile then decides whom to research. Personas built from interviews with people at accounts the business should never have won will describe the wrong buyers. Recruiting from accounts inside the profile, across the roles that shape the decision, gives personas that describe the people the business actually wants to reach.
In operation, the two meet in three places. Scoring holds company fit from the profile and role fit from the persona set as separate parts, so a seller can see whether a lead scored for its company, its role or its behaviour. The account plan names the account's fit with the profile and the roles mapped inside it, each matched to a persona and a message. And reporting reads both: a campaign that reached the right roles at the wrong companies, or the wrong roles at the right companies, fails for different reasons and needs different fixes.
The chain also runs backwards when something changes. If renewals show a new kind of account doing well, the profile moves first, and the research that follows may find roles the persona set does not yet cover. If research shows a role's concerns have shifted, the personas move, and the profile stays as it was. Keeping the two documents separate is what makes each of those updates small.
An invented lab software firm separates its profile from its personas
Cradvelix Labware, an invented laboratory inventory software firm, had one "customer" deck: four personas, the lab manager, the purchasing officer, the IT reviewer and the head of research, each with a sector and company size written in. Marketing used the deck as its target list, so any lab with a lab manager counted. Of 120 accounts won over two years, 38 had churned at their first renewal. The team pulled the 82 that renewed and found most were contract testing and research labs with 20 to 150 staff, running a particular electronic lab notebook the product connected to, while most churned accounts were teaching labs that bought on a one-off grant. The rewritten profile named those traits and added two disqualifiers: grant-funded one-off purchases and labs under 10 staff. The target list fell from about 2,400 labs to about 640. The personas lost their company details and were rebuilt from 14 interviews at renewed accounts: the lab manager, the purchasing officer and the IT reviewer stayed, and the head of research was dropped because no interview found that role involved in the decision. Fit points now come from the profile and role points from the persona set, scored separately. Over the next two quarters, the share of proposals going to accounts outside the profile fell from 41% to 9%.
Common mistakes
- Using a persona deck as a target list. Personas describe people; any organisation employs someone who matches them. Account selection needs the profile's checkable fields and disqualifiers.
- Writing company traits into personas. A persona with a sector and headcount attached blurs the two documents and makes both harder to update.
- Building personas before the profile. Research recruited from every account describes the buyers the business has, including those it should not have won.
- One persona for a business sale. A purchase shaped by several roles needs a persona for each role that matters.
- A profile with no disqualifiers. Without them the profile approves every account and filters nothing.
- Blending company fit and role fit in one score. Keep them as separate parts so sales can see why a lead qualified.
- Updating both whenever one changes. A shift in which accounts renew moves the profile; a shift in what a role cares about moves the persona. The comparison library lists other pairs that are easy to confuse.
