Sales Enablement Aside—Buyer Persona Development: How to Build B2B Personas That Actually Sharpen Your Messaging
By Rick Elmore ·
Most of the buyer personas I see in B2B could have been written without talking to a single customer. "Marketing Mary, 38, likes coffee and hates manual reporting." That's not a persona. That's a stock photo with a job title. And the teams carrying these documents around wonder why their messaging never lands.
Here's what actually happens: someone on the marketing team builds personas during an offsite, the sales team never reads them, and six months later nobody can find the file. The exercise produces a deliverable, not a decision-making tool. That's the gap I want to close in this post. Done right, buyer persona development isn't a creative writing assignment. It's research that changes what you say, to whom, and when.
- Personas are not your ICP. Your ICP describes which companies to sell to. Personas describe the individual humans on the buying committee who say yes, no, or "not now."
- Build from evidence, not imagination. Real personas come from win/loss interviews, call recordings, and intent signals — not a whiteboard brainstorm.
- Map to the committee. B2B deals are decided by three to seven people. You need a persona for each role that can kill the deal, not just the one who signs.
- The output is messaging, not a document. A persona earns its keep when it changes an email subject line, a call opener, or a landing page headline.
- Track triggers. The moment a buyer starts caring is more useful than their demographics. Capture what event pushes them from passive to active.
Why demographic personas keep failing B2B teams
The persona template most teams inherit came from B2C marketing, where age, income, and lifestyle genuinely predict buying behavior. In B2B, that data tells you almost nothing. Knowing your buyer is a 42-year-old VP who commutes 30 minutes doesn't help you write a better cold email. Knowing that she just absorbed two teams in a reorg and now owns a tool stack she didn't choose? That changes everything.
The failure point is almost always the same: personas built on assumptions about who the buyer is, instead of evidence about what the buyer is trying to accomplish and what stands in their way. When you skip the research, you fill the gaps with your own biases. You describe the buyer you wish you had, then write messaging for a person who doesn't exist.
There's a second failure too. Teams build one persona — usually the economic buyer — and ignore the rest of the committee. But in most B2B deals, the person who signs the contract is not the person who first felt the pain, not the person who'll use the product daily, and not the person in finance who can veto the whole thing. Message to one and the deal stalls when the others aren't convinced.
Persona vs. ICP: what's actually the difference?
People use these terms interchangeably and it muddies everything. Here's how I keep them straight.
| Dimension | Ideal Customer Profile (ICP) | Buyer Persona |
|---|---|---|
| Describes | The company you want to sell to | The individual humans who decide |
| Attributes | Industry, size, revenue, tech stack, growth stage | Role, goals, pains, objections, triggers, language |
| Drives | Targeting and list building | Messaging, positioning, objection handling |
| Answers | "Who should we prospect?" | "What do we say to win them over?" |
You need both, and they work in sequence. The ICP gets you to the right account. The personas get you through the account's buying committee. If you've already locked your ICP and you're wondering why conversion is still soft, the problem is usually persona-level: your messaging treats a complex committee like a single buyer.
Map the buying committee before you write a word
Before building any persona, I sketch the committee for a typical deal. Who gets looped in? For most B2B purchases over a few thousand dollars a month, you're looking at some version of five roles:
There's the champion — the person who feels the pain most acutely and will push internally for a solution. There's the economic buyer who controls the budget and cares about ROI and risk. There's the end user who will live inside your product and cares whether it makes their day better or worse. There's the technical or security evaluator who can block on integration or compliance grounds. And there's the skeptic — often finance or ops — whose default answer is no and who needs a reason to stay neutral.
Each of these people reads the same deal through a different lens. Your champion wants ammunition to sell internally. Your economic buyer wants to know this won't blow up in their face. Your end user wants to know it won't add work. When you build a persona for each, you stop writing one-size-fits-nobody messaging and start arming yourself for every conversation in the deal.
You don't need a persona for every title on the org chart. You need one for every role that can advance or kill the deal. That's usually three to five, not fifteen.
Where real persona data actually comes from
This is the part teams skip, and it's the only part that matters. Good personas are sourced, not invented. Here are the three wells I draw from, in order of value.
Win/loss and customer interviews. Nothing beats a 30-minute conversation with someone who recently bought from you — or chose not to. Ask them what was happening in their world when they started looking. Ask what they typed into Google. Ask what almost made them walk away, and what finally tipped them. The exact phrases people use become your messaging. When three customers independently describe their problem as "we were flying blind on pipeline," that sentence belongs on your homepage. You didn't write it. They did.
Sales call recordings. If you run Gong, Fathom, or any call capture, you're sitting on the richest persona data you'll ever have. Pull 15 to 20 recordings and listen for patterns in objections, the questions each role asks, and the language buyers use to describe their pain. A technical evaluator asks completely different questions than a champion. The recordings show you exactly what each persona worries about, in their own words, at the moment it matters.
Intent data and behavioral signals. Interviews tell you the "what" and "why." Intent data tells you the "when." When an account starts researching a specific category, consuming competitor content, or hitting your pricing page repeatedly, that's a trigger event in motion. Tying triggers to personas — knowing that a champion typically starts looking right after a failed quarter, or after inheriting a broken process in a reorg — lets you time your outreach to the moment someone actually cares.
You don't need all three to start. Begin with five customer interviews and a stack of call recordings. That alone will put you ahead of most of your competitors, who are still working from the offsite whiteboard.
What goes into a persona that drives messaging
Strip out everything that doesn't change what you say. For each persona on the committee, I capture six things:
The job they're accountable for — what does their boss grade them on? The pain in their words — the actual phrases from interviews and calls, not your paraphrase. The trigger — the event that moves them from passive to active. The objections — what makes them hesitate or push back. The success metric — how they'll know the purchase paid off. And the information diet — where they go to learn, who they trust, what format they'll actually consume.
Notice what's missing: age, hobbies, favorite software, a fake name and headshot. None of that survives contact with a real sales conversation. If a field doesn't change a subject line, a call opener, or a piece of content, it doesn't go in the persona.
Turning personas into messaging decisions
A persona you file away is worthless. Here's how I force each one to earn its place. Take the champion persona. Their pain is "I'm getting blamed for missed targets and I can't see where deals are stalling." That single sentence rewrites your outbound. Instead of "We help companies automate their sales process," you open with "If you're getting heat for missed pipeline but can't point to where deals die, that's usually a visibility problem, not an effort problem." One line, pulled straight from the research, and it lands because it's their language.
Do this for each persona and each channel. The economic buyer's landing page leads with risk and ROI. The end user's demo opens with "here's the annoying thing this removes from your day." The security evaluator gets a one-pager that answers their questions before they ask. Same product, five entry points, each built from evidence about a specific human.
This is where persona work connects to the rest of your revenue engine. When we build sales automation and AI agent sequences for clients, the personas decide the branching logic — which message a lead gets depends on which role they hold and which trigger fired. Without research-backed personas, that automation is just spray and pray at scale. You can see how we package this across lead gen, RevOps, and automation in our pricing and packages.
Keep personas alive with your call data
Buyers change. The pain that drove deals last year gets solved by a new tool, a reorg shifts who holds budget, a new regulation creates a fresh trigger. Static personas rot. The teams who get lasting value treat persona development as a loop, not a project: every quarter, pull the latest call recordings and win/loss notes, and check whether the language, objections, and triggers still hold. When you hear a new objection surfacing across three calls, update the persona and update the messaging that same week.
This is the quiet advantage of building personas from call data in the first place. The source refreshes itself. Every conversation your reps have is new research, if you're set up to capture and review it. Most teams aren't, which is exactly why their personas go stale and their messaging drifts back to generic.
Frequently asked questions
How many buyer personas do I actually need?
One for each role that can advance or kill a deal — typically three to five in B2B. Start with your champion, economic buyer, and the most common blocker. Resist building a persona for every job title; you want enough to cover the committee, not a filing cabinet nobody reads.
Can I build personas without customer interviews?
You can start with call recordings and intent data if you have deal volume, and that's better than nothing. But interviews surface the "why" behind decisions that calls and data only hint at. Even five conversations with recent buyers and churned prospects will sharpen your personas more than any amount of internal guessing.
How often should I update buyer personas?
Review them quarterly against fresh call data and win/loss notes. Do a deeper refresh whenever something structural shifts — a new competitor, a pricing change, a market event that creates new triggers. If your win rate or reply rate drops without an obvious cause, outdated personas are a likely culprit.
If your messaging isn't landing and you suspect the problem is persona-deep, we'll pull apart your call data, interviews, and intent signals to rebuild personas that actually drive conversion. Book a Revenue Systems Audit and we'll show you where your committee is slipping through.