Sales Enablement Aside—Buyer Persona Development: How to Build B2B Personas Your Reps Actually Sell To
By Rick Elmore ·
I've sat through more buyer persona presentations than I can count. The pattern is always the same: a marketer unveils "Marketing Mary" or "IT Director Dave," complete with a stock photo, a fake age, and a bullet point about how he "values work-life balance." Everyone nods. The deck gets saved to a shared drive. And not a single rep ever opens it again.
Here's the problem. Those personas describe a person. Sales doesn't sell to a person. They sell to a buying committee under pressure, each member with a different reason to care or stall. A persona that tells you Dave is 44 and likes golf does nothing when Dave is on a call trying to decide whether your tool is worth the political risk of championing it internally.
If you want personas your reps actually use, you have to build them around the real mechanics of the deal: who's in the room, what's forcing them to act, and what they'll get blamed for if it goes wrong. Let me walk through how we do it.
- A useful b2b buyer persona is tied to a buying-committee role and a job-to-be-done, not demographics.
- Build personas from real conversations and data signals—won deals, lost deals, call recordings—not internal guesses.
- Every persona needs a trigger: the event that moves someone from "this is a known problem" to "we're buying something this quarter."
- AI makes personas living documents by pulling patterns from calls, CRM notes, and intent data continuously.
- If a rep can't quote the persona's pain back to a prospect in their own words, the persona has failed.
Why most B2B personas never make it onto a sales call
The core failure is that marketing builds personas for messaging and sales needs them for selling. Those are different jobs. Messaging personas care about tone, channel, and content topics. Selling personas care about the specific sentence that makes a VP of Finance lean in.
The second failure is that they're built from the inside out. Someone on the team imagines what a buyer probably thinks, writes it down, and treats it as fact. Real buyers rarely describe their problems the way you'd expect. They don't say "I need better pipeline visibility." They say "I walk into the forecast meeting and I genuinely don't know which deals are real." That second sentence is sellable. The first one is a feature description.
The third failure is static. Markets move, buying committees reshuffle, new triggers emerge. A persona written eighteen months ago is describing a company that may not exist anymore. Most personas are a snapshot when they need to be a live feed.
Start with the buying committee, not the individual
In B2B, almost nothing of consequence gets bought by one person. There's usually a champion who wants it, an economic buyer who signs, a user who has to live with it, and at least one skeptic whose whole job seems to be killing new initiatives. Your personas should map to these roles, because each one needs a completely different argument.
Take a mid-market company evaluating a revenue system. The RevOps lead is the champion—she feels the daily pain of broken handoffs and manual reporting. The VP of Sales is the economic buyer—he cares about quota attainment and whether this makes his number more predictable. The CFO is the skeptic—she's seen three tools promise ROI and deliver spreadsheets. The SDR team are the users—they'll quietly sabotage anything that adds clicks to their day.
Sell the same way to all four and you lose. The champion needs ammunition to sell internally. The economic buyer needs a business case. The skeptic needs proof and a way to look smart for approving it. The user needs to believe their day gets easier. One product, four narratives.
So the first move in building a b2b buyer persona set is to list the actual roles in your best deals and build a persona for each seat at the table—not one generic "decision maker."
Build personas from evidence, not imagination
Here's where the real work is. Open your last 20 to 30 closed-won deals and your last batch of closed-lost. Then do something most teams skip: go listen. Call recordings, discovery notes, the actual words in email threads. You're mining for three things.
Pains in the buyer's own language. Write down the exact phrases they use. Not your category terms—theirs. These become the hooks in your outreach, because when a prospect reads their own problem described back to them, they assume you understand it.
The trigger event. Why now? Something changed. A new VP came in and the board wants a plan. A tool got deprecated. They missed a quarter. They raised a round and have to scale GTM fast. Problems alone don't create deals—problems plus a forcing event do. If you can't name the trigger, you'll spend your pipeline on people who have the pain but no urgency to fix it.
The internal cost of inaction and the fear. What is this person worried will happen if they do nothing—or if they back you and it flops? The CFO's fear of a wasted investment is as real as the champion's desire to fix the problem. Good personas capture both the pull toward action and the drag against it.
Patterns will show up fast. You'll notice that your best-fit champions almost always say the same two or three things. You'll notice that deals stall at the same objection. That repetition is the signal. Write it down verbatim.
What actually goes in the persona
Strip out everything that doesn't help a rep sell. Keep it tight enough that someone can read it in two minutes before a call. Here's the structure I use.
| Field | What it answers | Example (RevOps champion) |
|---|---|---|
| Committee role | Why are they in the deal? | Champion—feels the daily pain, sells internally for us |
| Job to be done | What outcome are they hired to produce? | Make revenue predictable and the team efficient without more headcount |
| Pain (their words) | What hurts, phrased how they'd say it? | "We're stitching together five tools and still flying blind on forecast" |
| Trigger | What makes now the time? | New VP of Sales demanding a clean forecast in 60 days |
| Fear / objection | What makes them hesitate? | "We've bought tools before that nobody adopted" |
| What good looks like | How do they measure success? | One source of truth, forecast they can defend to leadership |
| Message that lands | The one line that earns the meeting | "We make the forecast something you can actually stand behind, without adding to your team's workload" |
Notice there's no age, no stock photo, no "enjoys hiking." None of that changes how a rep opens a call. Every field here does.
How AI turns personas into living documents
The reason personas go stale is that updating them manually is tedious, so nobody does it. This is where AI genuinely earns its place—not as a gimmick, but as the thing that keeps personas honest.
Point an AI layer at your call recordings and CRM notes and have it surface recurring language, objections, and triggers across hundreds of conversations. A human reading 30 calls catches the obvious patterns. A model reading 300 catches the shift happening right now—a new objection that's showing up in the last month, a trigger that's becoming more common since a competitor changed pricing. That's the difference between a persona that describes last year and one that describes this quarter.
We also use intent and firmographic signals to flag when an account looks like a given persona is active. If a company just hired a VP of Sales and started researching forecasting tools, that maps cleanly to the champion-plus-trigger profile. The persona stops being a static reference and becomes a filter the whole system runs against—outreach gets personalized to the live situation, not a generic archetype.
The practical setup: AI drafts and refreshes persona summaries from real data, a human on the revenue team reviews and sharpens them monthly, and the sharpened version feeds directly into sequences, call prep, and lead scoring. That loop is what we build into the systems on our packages—personas wired into the engine instead of sitting in a drive.
Make reps actually use them
A persona only matters if it shows up in the moment of selling. The deck-on-a-drive model guarantees failure. Instead, put the persona where the work happens.
Drop the "message that lands" and top objection straight into your outreach templates, segmented by persona. Surface the relevant persona summary in the CRM when a rep opens a contact, so call prep takes 30 seconds. Build the trigger criteria into lead scoring so reps spend time on accounts where the "why now" is real. And run a simple test in call reviews: can the rep describe the prospect's pain in the prospect's own words? If they can, the persona is working. If they're reciting features, it isn't.
One more operator habit: treat objections as persona updates. Every time a deal dies at a new objection, that objection belongs in the persona. Personas should get sharper every quarter because your team keeps feeding them what they learn in the field.
The test for whether your personas are any good
Forget whether the slide looks polished. Ask one thing: would a prospect, reading an email built from this persona, feel like you were describing their specific situation? If yes, you've done the work. If it reads like it could apply to any company in the industry, you've built demographic fluff with a new coat of paint.
Good personas are uncomfortable in how specific they are. They name the exact fear. They quote the exact phrase. They pinpoint the exact event that makes someone pick up the phone. That specificity is the entire point, because it's what makes a cold prospect feel understood—and feeling understood is what gets you the meeting.
Frequently asked questions
How many buyer personas does a B2B company actually need?
Fewer than you think. Build one per committee role in your best-fit deals—usually a champion, an economic buyer, and one or two others. If you've got a dozen personas, you've probably confused persona with segment. Keep the set small enough that every rep knows them cold.
What's the difference between a buyer persona and an ideal customer profile?
Your ICP describes the company you want to sell to—industry, size, tech stack, the firmographic fit. The buyer persona describes the individual humans inside that company who influence the purchase. ICP tells you which accounts to target. Personas tell you how to talk to the people once you're in.
How often should buyer personas be updated?
Review them monthly if you have an AI layer pulling from live calls and CRM data, quarterly at minimum if you're doing it by hand. The trigger for an off-cycle update is a new recurring objection or a shift in who's showing up in deals. Personas should move as fast as your market does.
If your personas are collecting dust while your reps wing every call, the fix isn't a better slide—it's wiring research-backed personas into the system that runs your outreach, scoring, and call prep. Book a Revenue Systems Audit and we'll show you where yours are leaking deals.