ICP And Buyer Personas
Loose buyer definitions cost the most in sales time. A campaign aimed at "small and mid-size businesses" pulls in companies that can't afford the product, and reps spend weeks on deals that stall after the first demo. Marketing copy written for that same vague buyer ends up speaking to nobody in particular.
An ideal customer profile fixes the problem at the company level. It names the firms worth pursuing by size, industry, tools in use and the events that make them ready to buy. Personas then describe the people inside those firms: the one who feels the pain, the one who signs, and the one who can quietly stop the deal.
You'll leave with an ICP your sales team can qualify against, a persona card for each role in the deal and a map of who decides what.
Ideal Customer Profile
Write the ICP tightly enough that a rep can rule a lead in or out within two minutes of looking at it. Disqualifiers matter as much as the fit criteria, since they stop the team from chasing deals it can't win.
Industry, employee count and region, with the ranges stated as numbers.
The software they use today, especially the system your product would replace.
Events that make the problem urgent, such as a new hire, a funding round or a lost deal.
What you can observe from outside that shows the problem exists.
Conditions that rule a company out, however keen the contact sounds.
Expected contract value, sales cycle length and who usually signs.
Buyer Personas
A persona is worth keeping only if it changes what you write or how you sell. Each card should tell a copywriter or a rep what this person worries about, how their boss judges them and what makes them say no.
Job title and where it sits in the company.
What they're trying to achieve this year, in their terms.
The daily problems your product touches, quoted from interviews where possible.
The numbers their manager uses to judge them.
Evidence that would convince them, such as a demo, a reference or a trial.
What they'll push back on, and why.
Communities, publications and peers they trust.
Whether they start the search, use the product, approve the spend or can veto it.
Buying Committee Map
Even in a company of 50 people, a software purchase rarely rests with one person. The map shows who plays which part, so your content and sales outreach reach each of them before the decision is made.
| Role in the deal | Person | What they care about | How to reach them |
|---|---|---|---|
| Champion | |||
| Decision-maker | |||
| Day-to-day user | |||
| Blocker |
Worked Example
The company is fictional. The ICP and personas reflect the team's assumptions, to be tested in interviews.
Ideal Customer Profile
Professional services and B2B distribution firms with 10 to 200 employees and three to 25 people in sales.
Spreadsheets, shared inboxes or a free CRM tier the team has outgrown.
Hiring a second sales manager, a deal lost to a missed follow-up, or a founder stepping back from sales.
Job posts for sales operations roles, and reviews that complain about free CRM limits.
Fewer than three salespeople, or an enterprise CRM contract with more than a year left on it.
Annual contract under $15,000, a sales cycle of 30 to 60 days, signed by the founder or CEO. (Illustrative.)
Persona: Head Of Sales
| Field | Entry |
|---|---|
| Role | Runs a team of five to 15 reps and reports to the founder. |
| Goals | Hit the quarterly number without adding headcount. |
| Pains | Pipeline lives in three spreadsheets, and forecasts are a guess every month. |
| How they're measured | Revenue against target, win rate and forecast accuracy. |
| Proof they need | A trial with their own pipeline data, and a reference from a similar-sized team. |
| Objections | Reps won't log activity, and migration will cost a quarter. |
| Where they look | Sales leadership communities on LinkedIn and Slack, and peer recommendations. |
| Role in the deal | Champion. Starts the search and builds the case. |
Persona: Founder Or CEO
| Field | Entry |
|---|---|
| Role | Still close to sales, and signs every software contract above a set amount. |
| Goals | Predictable revenue they can plan hiring around. |
| Pains | Can't see the pipeline without asking someone for a spreadsheet. |
| How they're measured | Company growth and cash runway. |
| Proof they need | A clear price, a short setup time and evidence the team will use it. |
| Objections | Another tool the team will stop using in three months. |
| Where they look | Founder peers, review sites and their accountant or advisor. |
| Role in the deal | Decision-maker. Approves budget and has final say. |
Buying Committee Map
| Role in the deal | Person | What they care about | How to reach them |
|---|---|---|---|
| Champion | Head of Sales | Forecast accuracy and rep adoption | Trial invite and a peer case study |
| Decision-maker | Founder or CEO | Cost, setup time and visibility | A one-page business case from the champion |
| Day-to-day user | Sales reps | Less admin and faster logging | In-app guidance during the trial |
| Blocker | Operations or finance lead | Data migration and contract terms | A migration plan and transparent pricing |
Mistakes To Avoid
- Personas built from guesses - A persona written without interviews describes the team's hopes, and the copy built on it misses the real buyer.
- No disqualifiers - An ICP that only says who fits lets reps chase any company that replies to an email.
- One persona for the whole deal - Writing only for the champion leaves the decision-maker and the blocker without the answers they need to say yes.
- Job titles in place of roles - The same title can start a search in one company and block it in another, so map people by what they do in the deal.
Created by Archana Panda. Licensed under CC BY 4.0.