Buyer Personas for B2B (That Aren't Fiction)
A useful B2B buyer persona captures what a role is measured on, what they fear, what they must justify internally, and where they look for answers. Demographic details and invented biographies change nothing about what you write, which is why most persona documents sit unused after the workshop that produced them.
- Build personas per buying-group role, not per company type. The company is the ICP's job.
- Capture what they are measured on and what they must justify. Skip the stock photo and the fictional biography.
- Five roles matter in most B2B deals. Most companies only write for the champion.
- Derive them from recorded sales calls, not from a workshop. The language should be your buyers' language.
- A persona that does not change a sentence you write is decoration.
Why most personas are useless
The standard persona document contains a stock photo, an invented name, an age range, a set of hobbies, and a paragraph of aspirational description. It is produced in a workshop, circulated, admired, and never referenced again.
It fails because none of that content changes what anyone writes. Knowing that Marketing Mary is 38 and enjoys hiking has no bearing on the first line of an email. The test for any persona detail is simple: does this change a sentence? If not, it does not belong in the document.
Personas are per role, not per company
A frequent structural error is building personas around company types — enterprise persona, mid-market persona. That is the ICP's job. Personas describe the people inside a target account, and in B2B there are always several.
| Role | Cares about | Kills deals by |
|---|---|---|
| Champion | Solving their own visible problem, and looking good doing it | Leaving the company |
| Economic buyer | Return, risk, and opportunity cost against other bets | Never being engaged at all |
| Technical evaluator | Security, integration, maintenance burden | A single unanswered objection |
| End user | Whether their day gets better or worse | Quiet non-adoption after purchase |
| Blocker | Status quo, their own prior decision, or budget control | Raising an objection late that nobody prepared for |
Most B2B content is written exclusively for the champion, because the champion is who marketing talks to. The economic buyer and the technical evaluator receive nothing written for them, then stall the deal late — which gets recorded as a sales execution problem rather than a content gap.
The four things worth capturing
- 01What they are measured on
The metric on their own performance review. This is the single most useful field in the document, because it tells you the frame in which anything you say will be evaluated. A VP of Sales measured on ramp time hears a different pitch from one measured on win rate.
- 02What they fear
Not abstract pain points — the specific outcome that would embarrass them. Buying something that does not get adopted, championing a vendor that fails, being blamed for a security incident. Fear drives more B2B behaviour than ambition does.
- 03What they must justify internally, and to whom
Every buyer has to explain the decision to someone. Knowing who and in what terms tells you exactly what material to give them — and giving a champion the deck they need for their own board is worth more than any amount of nurture email.
- 04Where they actually look
Which communities, which peers, which publications. Not where you would like to reach them — where they genuinely go. This determines distribution, and distribution is where most demand generation fails.
Research that produces real personas
The best source is already in your building and nobody uses it: recorded sales calls. Twenty recordings across won and lost deals contain the actual language your buyers use, the objections they actually raise, and the internal dynamics they describe unprompted.
- 01Listen to twenty calls — ten won, ten lost
The lost ones are more informative. Note the exact words used to describe the problem, and use those words rather than your own category language.
- 02Interview eight to ten recent buyers
Ask what happened before they contacted you, who else was involved, what nearly stopped it, and what they had to convince someone else of. Ask about the process, not about your product.
- 03Interview three people who chose someone else
Uncomfortable, high yield, and rarely done. They will usually tell you, and what they say is frequently different from what your sales team recorded as the loss reason.
- 04Ask the SDR team what objections open the conversation
SDRs hear the unfiltered first reaction more than anyone else in the company, and they are almost never consulted.
Turning a persona into content
A persona earns its existence when it produces a content decision. The mapping is direct.
| Role | What they need | Format that works |
|---|---|---|
| Champion | Ammunition for the internal case | Business case template, ROI model, a deck they can present |
| Economic buyer | Risk and return in their own terms | One page, peer evidence, and a clear cost of inaction |
| Technical evaluator | Answers before they have to ask | Documentation, security overview, integration detail |
| End user | Confidence their day improves | Short demo, onboarding preview, honest limitations |
| Blocker | A reason not to object | Migration and rollback plan, evidence from a comparable company |
Most companies have the first row and nothing else. Building even a single one-page asset for the economic buyer is frequently the highest-return content work available, because it addresses the role that most often stalls late-stage deals.
Keeping them honest
Personas drift as the market and product change. Two lightweight practices keep them current: re-listen to five recent calls each quarter and check whether the language still matches, and add a mandatory field to closed-lost records capturing which role blocked the deal.
That second practice produces the most useful persona data you will ever collect, at essentially no cost. If the technical evaluator blocks a third of your losses, you do not need a persona workshop — you need documentation, and you now have the evidence to fund it.
Want this diagnosed on your own numbers?
The RADAR™ Scan scores your revenue engine in 2 minutes — 12 questions, a 0–100 score, and your gate verdict. No email required.
Run your RADAR™ Scan→Questions this raises.
What is a B2B buyer persona?
What should a buyer persona include?
How many buyer personas do you need?
How do you research buyer personas?
Why do most buyer personas fail?
Related guides.
Build it from closed-won data rather than aspiration, write it as machine-checkable criteria, and include the exclusions most companies leave out.
Lead GenerationThe full process, the channel economics, and the qualification model — written for people who have to hit a pipeline number, not win a content award.
Lead GenerationSeven stages, what each must produce to pass to the next, and the two handoffs where most B2B pipeline actually leaks.
Lead GenerationFirst we build your pipeline. Then we build the machine that scales it.
Every engagement starts with the RADAR™ Reveal — a 2-week audit with a scored report, gate verdict, and roadmap. Yours to keep, whatever you do next.