Sales Enablement Aside—Buyer Persona Development: How to Build B2B Personas That Actually Sharpen Your Messaging
By Rick Elmore ·
Last quarter I sat in on a pipeline review where the VP of Marketing proudly walked through four buyer personas. "Marketing Mary." "IT Ian." Each had a stock photo, a fake job title, and a list of hobbies. One of them liked kayaking. I asked a simple question: what does the CFO need to hear before she signs off on this deal? Silence. They had spent weeks building personas that told them nothing about how buyers actually decide.
That's the problem with most persona work. It's a demographics exercise dressed up as strategy. It makes a slide deck look finished, but it never changes a single sentence in your outbound sequence or your sales call. A useful b2b buyer persona does one job: it sharpens what you say to a specific person at a specific moment in the buying process. Everything else is decoration.
- Demographic personas ("Marketing Mary, 38, likes yoga") are useless for B2B. Build personas around the decision a person owns, not their age or hobbies.
- B2B purchases are made by committees. You need a persona for each role in the buying group, not one "ideal buyer."
- Ground personas in real buyer research — win/loss calls, sales recordings, support tickets, and intent data — not internal guesswork.
- A persona earns its place only if it changes your messaging. If it doesn't rewrite a sentence somewhere, delete it.
- Personas are different from your ICP. ICP tells you which accounts to target; personas tell you what to say to the humans inside them.
Personas and ICP are not the same thing
People use these terms interchangeably and it causes real damage. Your ideal customer profile is an account-level filter: company size, industry, tech stack, revenue, growth signals. It answers "which companies should we chase?" We've written about building a sharp ICP elsewhere, and if you don't have one yet, start there.
A buyer persona works one level down. Inside a target account there are five, eight, sometimes twelve people who influence the decision. They have different jobs, different fears, and completely different definitions of "success." The ICP tells you to call Acme Corp. The persona tells you that the Head of Security at Acme cares about audit trails while the CFO only cares about payback period. Same account, two conversations that share almost no vocabulary.
If you treat the whole committee as one blurry "buyer," you end up writing messaging that speaks to no one. The copy gets watered down to the lowest common denominator, and it stops landing. The entire point of personas is to let you speak precisely to each role.
Build personas around decisions, not demographics
Here's the mental shift that changes everything: a persona is not a type of person, it's a type of decision someone owns inside a purchase. Age, tenure, and LinkedIn headcount estimates don't tell you how to sell. What tells you how to sell is knowing what this person is responsible for, what makes them look good to their boss, and what keeps them up at night when a project goes sideways.
So I build every persona around four things, and nothing else makes the cut unless it serves these:
The outcome they're accountable for. A RevOps leader is measured on pipeline velocity and clean data. A CFO is measured on margin and predictability. Name the metric they'll get praised or fired over.
The problem in their words. Not your category language — theirs. A buyer doesn't say "I need a revenue engine." They say "my reps spend half their day doing manual data entry and I can't trust the forecast." That exact phrasing is gold. It belongs in your subject lines.
What they're afraid of. Every B2B buyer carries risk. Buying the wrong tool means a failed implementation, a wasted budget, and a conversation with their boss they'd rather not have. The best messaging de-risks the decision, so you have to know the specific fear.
What would make them an internal champion. Even someone who loves your product won't push for it unless championing it makes them look smart. Figure out the career win they get by bringing you in.
Notice none of that requires a stock photo or a first name. "Marketing Mary" tells you nothing. "The marketing leader who's accountable for pipeline but blamed when sales doesn't close it" tells you exactly what angle to lead with.
Where real persona research actually comes from
The reason most personas are fiction is that teams build them in a conference room instead of from evidence. You cannot invent what a buyer thinks. You have to go get it. Here's where I pull from, in rough order of value.
Win/loss conversations. The single richest source. Talk to people who bought and people who didn't. Ask the lost deals why they chose someone else, or chose to do nothing. The "do nothing" answers are the most useful because they reveal what your messaging failed to make urgent.
Recorded sales calls. If you run Gong, Fireflies, or any call recorder, you're sitting on a goldmine. Search for the questions buyers ask, the objections they raise, the moments they lean in. The language they use on those calls is the language you should be writing back to them.
Support tickets and onboarding notes. What people struggle with after they buy tells you what they were really trying to solve. It also surfaces the gap between what you promised and what they expected.
Intent data. This is where modern persona work pulls ahead of the old approach. Tools that track topic surges, content consumption, and buying signals tell you what a given role is researching right now. When you see that security-related research spiked at an account before they booked a demo, you learn that the security persona was a driver in that deal — not a guess, a signal. Intent data also tells you timing, which demographics never could.
Community and review mining. Read the one-star and three-star reviews of your competitors. Scroll the Slack groups and subreddits where your buyers complain. People are brutally honest in those spaces in a way they never are on a sales call.
You don't need a research team to do this. Block two days, listen to twenty calls, read fifty reviews, and interview five customers. You'll learn more than a six-week agency project built on survey data.
Map personas to the buying committee
Once you have the raw material, organize it by role in the buying group. In B2B, deals die in the gaps between committee members — the champion loves you but can't get the CFO to care, or procurement stalls a signed deal for a month. Mapping personas to the committee lets you arm each person with what they need to move the deal forward internally.
I keep it simple. Most B2B committees break into four functional roles, and I write a distinct message angle for each.
| Committee role | What they actually care about | Message angle that lands |
|---|---|---|
| Economic buyer (CFO, VP, budget owner) | Payback period, risk, predictable return | "Here's how fast this pays for itself and why it won't blow up." |
| Champion (the person with the pain) | Fixing a daily problem, looking good to leadership | "Here's how this solves your problem and makes you the hero." |
| Technical / security evaluator | Integration, security, implementation effort | "Here's how it fits your stack without breaking anything." |
| End user (reps, ops, the people who'll use it) | Daily workflow, whether it adds or removes work | "Here's how this makes your day easier, not harder." |
The champion is the one you equip hardest, because the champion sells internally when you're not in the room. Give that person the one-pager that answers the CFO's objection before it's raised. That's persona work doing real sales enablement — not a slide, but ammunition.
Turn personas into messaging that changes
This is the step everyone skips, and it's the only step that matters. A persona is worthless until it rewrites a specific sentence in a specific asset. So I run every finished persona through a simple test: what does this change?
Take the CFO persona. If you learned the CFO's biggest fear is a failed implementation that wastes six months, then your proposal needs a clear implementation timeline and a risk-reversal clause up front. Your cold email to that persona leads with predictability, not features. Your case studies feature payback math, not logos.
Take the end-user persona. If reps fear a tool that adds admin work, your demo should open by showing what it removes from their day, not the shiny dashboard the VP wants. Same product, completely different first ninety seconds.
When we build revenue engines for clients, this is where the persona work connects to the automation. The intent signals feed the sequencing, the persona defines the message for each role, and the AI agents and sales workflows deliver the right angle to the right person at the right time. Personas aren't a marketing artifact that sits in a folder. They're the instruction set for the whole system. If you want to see how that plumbing fits together, our packages lay out how research, messaging, and automation connect.
One warning. Personas go stale. Markets shift, a new competitor reframes the category, your buyers' priorities move. Revisit them at least twice a year, and whenever your win rate drops for no obvious reason. Fresh calls in, old assumptions out.
The test for whether a persona is any good
Pull up any persona your team has built. Ask one question: if I handed this to a new SDR, would they write a better cold email because of it? If the answer is yes, keep it. If the answer is "they'd know this person is 42 and enjoys hiking," throw it out. A good persona makes your next sentence sharper. That's the whole job. Everything else is theater.
Frequently asked questions
How many buyer personas does a B2B company need?
Fewer than you think. Build one per distinct role in your buying committee — usually three or four: the economic buyer, the champion, the technical evaluator, and the end user. If two "personas" would get the exact same message, they're one persona. Don't split by industry or company size; that's ICP work, not persona work.
What's the difference between a buyer persona and an ICP?
Your ICP is an account-level filter that tells you which companies to target based on firmographics like size, industry, and tech stack. A buyer persona works inside those accounts and tells you what to say to each individual decision-maker. ICP answers "who to call," personas answer "what to say when they pick up."
Can I build useful personas without a big research budget?
Yes. The best source material is already in your business: recorded sales calls, win/loss notes, support tickets, and competitor reviews. Add a handful of customer interviews and whatever intent data you can access. Two focused days of listening beats a six-week survey project, because you're pulling the buyer's actual language instead of their survey-filtered answers.
If your personas look good on a slide but your messaging still falls flat, the gap is usually in how research, messaging, and automation connect. Book a Revenue Systems Audit and we'll pressure-test your personas against your actual pipeline.