Sales Enablement Aside—Buyer Persona Development: How to Build B2B Personas That Actually Sharpen Your Messaging
By Rick Elmore ·
Most buyer personas I see are useless. They're a slide deck that someone built two years ago, named "Marketing Mary," and never opened again. Mary is 42. She has two kids. She likes coffee and hates jargon. None of that has ever helped a single rep close a single deal.
I've watched teams spend weeks on persona workshops and come out with documents that read like dating profiles. Then the same teams wonder why their outbound gets ignored and their discovery calls feel like interrogations. The problem isn't that personas are a bad idea. It's that almost nobody builds them from the thing that actually matters: how specific people inside a buying committee make decisions, what they fear, and what moves them to act.
A real b2b buyer persona is a working model of a decision-maker's psychology tied to the signals you can actually observe in your pipeline. If it doesn't change what you write in an email or ask on a call, it's decoration.
- Personas are not your ICP. ICP tells you which accounts to target. Personas tell you how each human inside those accounts thinks, decides, and resists.
- Build personas from deal data and buyer language, not demographics. Won/lost reasons and call transcripts beat survey guesses every time.
- B2B buying is a committee sport. You need a persona per role (economic buyer, champion, technical evaluator, blocker), each with its own messaging.
- A persona earns its place only when it's operationalized—baked into outbound sequences, content briefs, and discovery frameworks.
- Personas are living models. Review them quarterly against new deal signals or they rot.
Why demographic personas fail in B2B
In B2C, demographics can correlate with behavior. In B2B, they almost never do. Knowing that your buyer is a 45-year-old VP of Operations tells you nothing about whether she'll champion your product or quietly kill it in committee.
What actually predicts a deal is the stuff demographics skip: the pressure she's under this quarter, the internal politics she has to manage, what a failed purchase would cost her personally, and the specific words she uses to describe the problem. Two VPs of Operations with identical LinkedIn profiles can behave like completely different buyers depending on whether one is defending a budget and the other is trying to justify a promotion.
The demographic model also flattens the buying committee into one fictional person. Real B2B deals involve four to seven people, and they want contradictory things. The economic buyer cares about risk and ROI. The end user cares about whether this makes their day harder. The IT reviewer is looking for a reason to say no. If your persona is a single composite human, your messaging will be mush that speaks to everyone and moves no one.
Persona vs ICP: what's the difference?
These get used interchangeably, which creates sloppy targeting. They answer different questions.
| Dimension | Ideal Customer Profile (ICP) | Buyer Persona |
|---|---|---|
| Unit of analysis | The company / account | The individual decision-maker |
| Core question | Which accounts should we pursue? | How does this person decide, and what moves them? |
| Built from | Firmographics, tech stack, revenue band, trigger events | Psychology, goals, fears, buying role, language |
| Drives | Account selection and territory | Messaging, discovery questions, objection handling |
| Typical count | One to three per motion | One per role in the buying committee |
You need both. ICP without personas means you reach the right companies with messaging that lands on no one. Personas without ICP means you write beautiful, resonant emails to accounts that will never buy. The two work as a pair: ICP picks the room, personas tell you how to talk to each person in it.
How to build B2B personas from real deal signals
Here's the process I actually run. It takes data you already have, not a survey vendor.
Start with your won and lost deals. Pull your last 20 to 30 closed opportunities, won and lost. For each one, who was involved? What role did they play in the decision? What did the deal hinge on? Most teams discover their win reasons and loss reasons cluster into a handful of patterns. Those patterns are the raw material for personas. If deals keep dying because a security reviewer wasn't brought in early, that reviewer is a persona you've been ignoring.
Mine the language, not just the facts. This is the step that separates a sharp persona from a flat one. Go into your call recordings, your discovery notes, your email replies. Pull the exact phrases buyers use to describe their problem, their goal, and their hesitation. Not how your marketing describes it. How they describe it. When a champion says "I'm tired of stitching five tools together and still not trusting the numbers," that sentence is worth more than any demographic field. It becomes a headline, a cold email opener, a discovery prompt.
Separate the committee by role. For each deal, map who held which job: the economic buyer with budget authority, the champion pushing it internally, the technical or security evaluator, the end users who live in the product, and the blocker who benefits from the status quo. Build a persona for each recurring role. The economic buyer persona and the champion persona should read differently, because their motivations genuinely are different.
For each persona, answer four things. What outcome are they personally accountable for? What happens to them if this purchase goes wrong? What's the status quo they're comparing you against (usually "do nothing" or a spreadsheet, not a competitor)? And what internal objection will they raise or hear? If you can answer those four, you can write to that person. If you can't, you don't know them well enough yet.
Validate against the people who talk to buyers. Run your draft personas past your best reps and SDRs before you ship them. The people on the phones will tell you fast if a persona is fiction. They know the champion's real anxiety and the blocker's real excuse because they hear it weekly.
Mapping personas to the buying committee
The reason to build a persona per role is that your message has to change by role or it falls flat. Let me make this concrete.
The economic buyer doesn't want to read about features. She wants to know this won't blow up, that the ROI is defensible to her boss, and that the rollout won't eat her team's time. Lead with risk reduction and payback, not product depth.
The champion is your inside seller, and he's taking personal reputational risk to push you. Your job is to arm him. Give him the numbers, the one-pager, the answer to the question his CFO will ask. Make him look smart in the room you're not in.
The technical evaluator is scanning for reasons to disqualify you. Integrations, security, data handling, admin overhead. Speak to those directly and early. Vague reassurance reads as evasion to this person.
The blocker is the one who loses something if you win—maybe the owner of the tool you'd replace. You rarely convert a blocker, but you can neutralize one by acknowledging their concern before your champion has to defend against it.
When these roles each get tailored messaging, deals move faster because every person in the committee hears an argument built for them. When they all get the same generic pitch, the deal stalls in consensus limbo.
How to operationalize personas across outbound, content, and discovery
A persona that lives in a Google Doc is worthless. The whole point is to change the work. Here's where ours actually show up.
Outbound. Every sequence gets built for a specific persona. The opener uses that persona's own language about the problem. The angle maps to what that role is accountable for. We don't send the economic buyer the same email as the end user. When we build sequences inside a client's revenue engine, the persona is the first input, not an afterthought. If you want to see how this fits into a full outbound and RevOps buildout, that's exactly what our packages are designed around.
Content. Every content brief names the persona it serves and the stage of their thinking. A piece for the technical evaluator comparing integration approaches looks nothing like a piece for the economic buyer on quantifying ROI. Tagging content by persona and buying role also means your nurture can route the right asset to the right committee member automatically.
Discovery. This is the most underused application. Each persona should come with a short set of discovery questions designed to confirm you're talking to that role and to surface their specific fear. When a rep knows they're on a call with a likely blocker, they can ask different questions than they would with a champion. Personas turn discovery from a generic checklist into a targeted conversation.
AI agents and automation. This is where it compounds. Once personas are structured data—not prose—your AI qualification and routing can act on them. An inbound lead gets classified by likely role, scored against the right persona, and routed with messaging that already fits. The persona stops being a reference document and becomes logic your system runs on.
Keeping personas alive
The last mistake is treating personas as a one-time project. Markets shift, your product changes, and the committee evolves. We revisit personas every quarter against the newest batch of won and lost deals. If a new role keeps showing up in the committee, or an old objection stops mattering, the persona changes. A persona you built 18 months ago and never touched is just a prettier version of Marketing Mary.
Frequently asked questions
How many buyer personas do I actually need?
One per distinct role in your buying committee, not one per job title. Most B2B companies land on three to five: an economic buyer, a champion, a technical or functional evaluator, and sometimes an end user and a blocker. If you're building ten personas, you're probably slicing by demographics instead of decision-making role.
What's the difference between a buyer persona and an ICP?
Your ICP describes the ideal company to sell to—firmographics, size, tech stack, trigger events. A buyer persona describes an individual inside that company: how they decide, what they're accountable for, and what they fear. ICP picks the accounts; personas tell you how to talk to the people in them. You need both working together.
How do I build personas if I don't have much deal data yet?
Start with conversations. Interview your best 5 to 10 customers and the prospects you lost, and record every call you can. Even 20 deals' worth of real buyer language beats a demographic guess. Treat your first personas as a hypothesis and sharpen them as pipeline data accumulates. The goal is a working model you improve, not a perfect document on day one.
If your personas are collecting dust while your outbound and discovery run on gut feel, that's a systems problem, not a copy problem. We'll map your buying committee to real deal signals and wire it into your outbound, content, and AI qualification. Book a Revenue Systems Audit.