Sales Enablement Aside—Buyer Persona Development: How to Build B2B Personas That Actually Change How Reps Sell
By Rick Elmore ·
Most buyer personas I see are worthless. Not because personas are a bad idea, but because someone in marketing built them in a workshop, gave them a name like "Marketing Mary," slapped a stock photo on a slide, and shipped a PDF that no rep has opened since. The persona described her hobbies. It did not describe why she says no.
Here's the pattern I keep running into with clients: the account-level targeting is fine. They know which companies to chase. But the moment a rep gets on a call with an actual human inside that company, the messaging falls apart. The rep pitches the same three features to a CFO that they pitched to a VP of Ops, and both deals stall for reasons nobody can name. That gap—between "we know who to sell to" and "we know how to sell to the person in front of us"—is what real buyer persona development closes.
This is not the same thing as your ICP. Your ICP is the account: industry, size, tech stack, revenue band. A buyer persona is the individual role inside that account, with their own goals, their own risk, and their own reasons to kill the deal. You need both. This post is about the second one, and specifically how to build personas from evidence you already have instead of from a whiteboard.
- Personas are about roles, not accounts. Your ICP tells you which door to knock on. Your persona tells you what to say when a specific person opens it.
- Build from evidence, not imagination. Win-loss interviews, call recordings, and CRM signals already contain your best personas. Stop inventing them in a room.
- The useful part is the buying behavior, not the demographics. What they fear, who they answer to, and what makes them say no matters far more than their job title's average tenure.
- A persona only counts if it changes a sentence. If a rep's opening line and a marketer's email subject don't change because of the persona, you built a poster, not a tool.
- Operationalize or don't bother. Personas belong in your CRM, your call scripts, and your sequences—not a slide deck.
Why most buyer personas never change how reps sell
The failure is almost always the same. Personas get built by people who never take sales calls, using data that was never collected for this purpose. You end up with a fictional character who reads industry blogs and "values efficiency." Great. Every human on earth values efficiency. That tells a rep nothing about what to do differently on Tuesday's discovery call.
The second failure is treating the persona as a marketing artifact instead of a sales instrument. Marketing wants personas to shape content themes. Fair. But reps need something sharper: what does this person actually care about, what will they push back on, and who else do they have to convince internally before they can sign. A persona that doesn't answer those three questions is decoration.
The third failure is scope. Teams build one persona for a buying committee that has five people in it. In B2B, you're almost never selling to one person. You're selling to an economic buyer who cares about ROI and risk, a technical buyer who cares about whether it actually works, and one or two end users who care about whether it makes their day harder. Same deal, three completely different conversations. If your personas don't reflect that split, your reps are speaking one language to a room that speaks three.
Where the real persona data actually lives
You don't need a survey. You're sitting on more persona data than any research firm could give you, and it's more honest because it came from real deals with real money on the line. Three sources matter most.
Win-loss data comes first. Not the CRM's "closed lost - no reason" field—actual conversations with people who bought and people who didn't. When you talk to someone who chose you, ask what nearly stopped them and who inside their org was the hardest sell. When you talk to someone who went elsewhere, ask what the other option said that landed. The patterns show up fast. You'll hear the same objection from the same role three times and realize you have a persona-level problem, not a one-off.
Call recordings are the second source, and honestly the richest. Your reps have already had hundreds of conversations with every persona you're trying to build. The language buyers use to describe their problem is right there. The moment a CFO's tone shifts, the question a technical evaluator always asks, the phrase that makes a deal go quiet—it's all recorded. Go listen to ten won deals and ten lost deals for a single role. Write down the exact words buyers use. That vocabulary becomes your messaging, because it's how they already think about the problem.
CRM signals are the third. Which titles actually respond to outreach. Which roles show up on deals that close fast versus deals that die in legal. How the sales cycle length changes when the champion is a director versus a VP. Your CRM is quietly telling you which personas convert and which ones waste your reps' time. Most teams never read it that way.
Put those three together and personas stop being guesses. A win-loss interview tells you the "why." A call recording gives you the exact words. CRM data tells you how often it's true and what it costs you. That's evidence, not a persona workshop.
How to build a persona that changes a sentence
Once you have the raw material, resist the urge to make it pretty. Skip the stock photo and the fake name. A useful persona is a short document that answers a handful of questions a rep can actually use. Here's the frame I use.
The job that got them into the room. Not their job title—the specific outcome they're accountable for that made this problem worth solving now. A VP of Sales isn't buying your platform because they like software. They're buying because their number is at risk and someone above them is asking why.
What they're actually afraid of. Every buyer has a private worry that the polished business case doesn't mention. The technical buyer is afraid this will become their problem to maintain. The economic buyer is afraid of signing something that fails and having their name on it. Name the fear and you can address it directly instead of talking past it.
Who they answer to and who they need to convince. This is the part reps consistently miss. Map the champion's internal path. If your persona is a director who has to get budget approved by a VP and sign-off from IT, your rep's job isn't just to sell the director—it's to arm the director to sell everyone else. That changes what materials you give them and when.
The exact objection that kills the deal for this role. Pull it straight from your lost calls. Write it in their words. Then write the response that has actually worked.
Here's how the same deal looks across three personas on one buying committee, which is the level of specificity that actually helps a rep.
| Persona | What they care about | What makes them say no | What the rep should lead with |
|---|---|---|---|
| Economic buyer (VP / C-level) | Impact on the number, risk of the decision, time to payback | Vague ROI, no proof it's worked for someone like them | Business outcome and a comparable customer story |
| Technical buyer (IT / Ops lead) | Whether it works, security, how much they'll have to maintain | Feeling like they'll inherit a mess or a security gap | Implementation reality and who owns what after go-live |
| End user (rep / analyst) | Whether it makes their daily work easier or harder | Extra steps, more admin, another login | How it removes work they already hate |
Notice what's missing: age, hobbies, "reads TechCrunch," favorite coffee order. None of it changes what a rep says. Everything in that table does.
How to operationalize personas so they actually get used
A persona document that lives in a shared drive is dead on arrival. The work isn't building the persona—it's wiring it into the places where selling and messaging actually happen. This is the step almost everyone skips, and it's the only one that produces a return.
Start in the CRM. Add a persona field to your contacts and make reps tag it during discovery. Now your pipeline reports break down by persona, and you can see which ones convert. That single move turns personas from a marketing opinion into a measurable sales input.
Next, rewrite the assets that touch each persona. Your outbound sequences should read differently for a CFO than for an ops manager, because the two of them do not share a problem. Your discovery call framework should include the specific fear and the specific objection for whoever's on the call. Your one-pagers should map to the committee roles, so a champion has something to forward to the person they need to convince. This is where the persona earns its keep—when the words a buyer receives actually match how that buyer thinks.
Then keep it alive. Personas drift. The objection that killed deals last year gets solved, and a new one takes its place. Revisit your win-loss and call data every quarter and update the objection and messaging fields. A persona is a living record of how a role buys, not a one-time deliverable.
This is exactly the kind of thing that breaks when it's stitched together by hand across five tools and three teams. When your lead gen, your CRM, and your sales automation run as one system, persona data flows from the conversation into the targeting and back out into the messaging without anyone re-keying it. That's the whole point of building the revenue engine as one integrated thing rather than a stack of disconnected apps. If you want to see how we package that, our pricing and packages lay out where persona work fits into the broader system.
Buyer personas vs. ICP: where the line sits
People conflate these constantly, so let me draw the line cleanly. Your ICP is the account you want—the company. It answers "which organizations should we spend our time on." Your buyer personas are the humans inside that account—they answer "how do we win the specific people who have to say yes."
You build the ICP first because it tells your team where to point. But an ICP alone leaves reps improvising the actual conversation, which is where deals are won and lost. Personas are how you turn a good target list into a closed deal, because they change what your rep says the moment a real person picks up. Get the account-level targeting right, then layer personas on top so the messaging lands. One without the other leaves money on the table.
Frequently asked questions
How many buyer personas does a B2B company actually need?
Fewer than you think. Most B2B companies need one persona per role on the buying committee for their core product—usually three to five total. If you're building more than that, you're probably describing job-title variations that buy the same way, which means you can collapse them. Build for how people buy, not for every title in the org chart.
What's the difference between a buyer persona and an ICP?
An ICP describes the ideal account—the company you want to sell to, defined by things like industry, size, and tech stack. A buyer persona describes an individual role inside that account—their goals, fears, and reasons to say no. You use the ICP to decide who to target and personas to decide how to sell once you're in the conversation.
How often should we update our buyer personas?
Review them quarterly, at least the objection and messaging fields. Buying behavior shifts as the market changes and as you solve old objections. Anchor each review to fresh win-loss and call data so you're updating from evidence, not from a hunch. A persona that hasn't changed in two years is almost certainly out of date.
If your reps are selling the same way to every person on the buying committee, your personas aren't doing their job—or you don't have real ones yet. We'll help you build them from your own win-loss and call data and wire them into the system your team actually uses. Book a Revenue Systems Audit.