Sales Enablement Aside—Buyer Persona Development: How to Build B2B Personas Your Reps Actually Use in Deals
By Rick Elmore ·
Most buyer personas are useless. They sit in a Notion doc nobody opens, full of lines like "Marketing Mary, age 42, enjoys yoga and reads industry blogs." A rep in a live deal has never once thought, "Let me check what Mary does on weekends." That document didn't lose a deal, but it never helped win one either.
Here's the direct answer: useful buyer persona development documents people by their role in the buying committee, not their demographics. Each persona should capture what that specific role is measured on, the pains that push them toward a solution, the triggers that make them act now, and the objections they raise before signing. When you build personas this way, reps can tailor a sentence in a call and marketers can write an email that lands. Everything else is decoration.
Why most buyer personas fail (and what reps actually need)
The failure comes from borrowing a B2C framework and stapling it onto B2B. In consumer marketing, a single person often decides and buys. Demographics and psychographics matter because you're predicting individual behavior. In B2B, that logic breaks. A $40k platform deal gets decided by five to eight people, each with a different stake, and none of them cares about your persona's hobbies.
What reps need mid-deal is fast, specific intel: when I'm talking to the VP of Sales versus the RevOps lead versus the CFO, what does each one care about, what are they afraid of, and what one line moves them? That's a working tool. A demographic profile is a trivia card.
The second failure is treating persona work as a marketing exercise that never reaches sales. Marketing builds the personas, sales never sees them, and the two teams end up describing the same buyer in incompatible language. Good persona development is shared infrastructure. Both teams pull from the same source, which is the only way messaging stays consistent from a cold email to a closing call.
Buyer persona vs ICP: the difference that changes everything
These get used interchangeably and shouldn't be. They answer different questions and operate at different levels.
| Dimension | Ideal Customer Profile (ICP) | Buyer Persona |
|---|---|---|
| Level | Account / company | Individual / role |
| Question it answers | Which companies should we sell to? | Who inside that company do we talk to, and how? |
| Typical attributes | Industry, headcount, revenue, tech stack, growth stage | Role, goals, pains, triggers, objections, influence in the deal |
| Primary user | Demand gen, SDR targeting, territory planning | AEs in live deals, content and email messaging |
| Changes when | You move upmarket or enter a new vertical | You add a new product line or the buying committee shifts |
The practical takeaway: ICP gets you into the right room. Personas tell you how to win the conversation once you're there. You need both, and they're not substitutes. A perfect ICP with no persona work means your SDRs book meetings and your AEs wing every call. Strong personas without an ICP means great conversations with companies that will never buy.
The connection between them is the buying committee. Within a single ICP account, you're not selling to one persona. You're selling to a group, each with their own version of the decision. Map that group and you've moved from theory to something your reps can run plays against.
How to map the B2B buying committee by role
Before you write a single persona, list the roles involved in a typical deal. Most B2B purchases involve a predictable cast, even if titles vary. Your job is to identify who sits in each seat for your specific sale.
- Champion. The person who feels the pain most directly and advocates for you internally. Usually the end user or their manager. They sell on your behalf when you're not in the room, so they need ammunition, not just enthusiasm.
- Economic buyer. Controls the budget and signs off. Often a VP or C-level who won't attend early calls but kills or approves the deal at the end. They care about ROI and risk, not features.
- Technical / operational evaluator. Vets whether your solution actually works with their stack and process. RevOps, IT, security. They can't say yes, but they can absolutely say no.
- End users. The people who'll live in the product daily. Their adoption determines whether the deal renews. If they hate it, your champion loses credibility.
- Blocker / skeptic. Not always present, but worth naming. Someone with a competing priority, a legacy system they built, or a bias toward a competitor. You need to know what they'll argue.
For each role, answer two questions: what does success look like in their job this quarter, and what makes them look bad to their boss? Those two answers drive almost everything else. A champion who gets promoted for hitting pipeline targets hears a completely different pitch than an evaluator whose nightmare is a failed implementation they signed off on.
You don't need a persona for every title. You need one per distinct decision role. If the VP of Sales and the VP of Marketing both act as economic buyers with the same concerns, that might be one persona. If RevOps evaluates differently depending on company size, that might be two.
The four components every working persona needs: pains, triggers, objections, and language
Strip away the fluff and a persona that reps use comes down to four blocks. Everything in the document should earn its place against these.
Pains
Not generic problems. The specific, role-level frustration that this person feels and could name out loud. A RevOps lead's pain isn't "inefficiency." It's "I spend every Monday rebuilding a forecast because the CRM data is garbage and reps don't update stages." Write pains in the buyer's own words, pulled from actual conversations. The closer it sounds to something they'd say, the faster a rep can mirror it back.
Triggers
What changed to make this person care now? Pain alone doesn't create deals; most people tolerate pain indefinitely. Triggers break the tolerance. A new VP of Sales inheriting a messy pipeline. A failed quarter. A tool being sunset. A funding round that demands faster growth. Document the three or four events that reliably precede a buying cycle for each persona. Marketing uses these for targeting and timing. Reps use them to ask the right diagnostic question: "What prompted you to start looking?"
Objections
The real reasons each role hesitates, by role. The economic buyer's objection is almost never the same as the end user's. The CFO worries about whether the ROI is real and whether you'll still be around in two years. The end user worries about learning yet another tool. Catalog the objections you hear in deals, assign them to the persona who raises them, and write the response that actually works. This is the section reps reach for most.
Language and messaging angle
The words that resonate and the words that repel for each role. A technical evaluator wants precision and proof; marketing superlatives make them trust you less. An economic buyer wants outcomes tied to numbers they're measured on. Give reps and writers the vocabulary that fits each persona, including the phrases to avoid. This is what keeps your cold email, your deck, and your closing call speaking the same language.
How to research personas without guessing
The fastest way to build a fake persona is to assemble the team in a conference room and brainstorm what you think buyers want. You'll produce a document full of confident assumptions and zero evidence. Real persona research comes from three sources, in order of value.
Win/loss and deal conversations. Your best data already exists in call recordings and CRM notes. Pull the last 20 to 30 closed deals, won and lost. Listen for the moment the champion said why they cared, the question the CFO asked that stalled things, the objection that killed a lost deal. Pattern these by role. This is the highest-signal research available, and most teams never do it.
Direct customer interviews. Talk to recent buyers, ideally within 90 days of their decision while it's fresh. Ask what problem they were solving, what else they considered, who else was involved, and what nearly stopped them from buying. You're not fishing for compliments. You want the messy reality of how the decision actually got made internally.
Rep debriefs. Your AEs carry an enormous amount of unwritten persona knowledge. The problem is it lives in their heads and leaves when they do. Structured debriefs, where you ask reps to describe the typical champion or the usual objection from procurement, surface that knowledge. Treat it as a hypothesis to confirm against call data, not as gospel, because reps remember vivid deals more than typical ones.
One rule throughout: separate what buyers say from what they do. People rationalize. A buyer might say they chose you for features when the real driver was that your champion trusted the rep. Weight behavior and outcomes over stated reasons.
How to document personas so reps actually use them in deals
A persona nobody opens in a live deal has failed, no matter how accurate. Documentation format determines usage. Keep each persona to a single page or screen. If a rep can't scan it in 30 seconds between calls, it won't get used.
Structure every persona identically: role and committee position at the top, then the four blocks (pains, triggers, objections with responses, language). Add one line on how this persona typically interacts with the others, since deals are won by managing the committee, not any single person. Skip the stock photo and the invented name if it tempts people to treat the document as fiction. Some teams find a name helps reps reference personas quickly in conversation ("that's a classic Economic Ed objection"), so use your judgment.
Then connect the personas to the places reps and marketers actually work. Link the relevant persona to deal stages in your CRM so the right objection-handling notes surface at the right moment. Pull trigger language into your SDR sequences. Feed the pain statements into your messaging frameworks. When persona work lives inside the revenue system instead of beside it, it gets used by default. This is a core part of how we build integrated revenue engines for clients: the research doesn't sit in a doc, it drives the automation, the sequences, and the AI agents that run on top of it.
Review personas quarterly against fresh deal data. Markets shift, committees change, new objections appear when a competitor launches something. A persona is a living document that tracks how your buyers actually behave, not a one-time project you file away.
Where this fits
Buyer persona development isn't a standalone marketing deliverable. It's the connective layer between your ICP (which accounts to chase) and your execution (what to say to each person in those accounts). Done right, it aligns your SDR sequences, your content, your sales conversations, and increasingly your AI agents around the same understanding of who's buying and why. Done wrong, it's a document that makes everyone feel organized while the deals keep getting decided on instinct. The difference is whether your personas are built from real deal evidence, mapped to the buying committee, and wired into the systems your team uses every day.
If your personas are collecting dust while your reps freestyle every call, we can help you rebuild them into something the whole revenue team actually runs on. Book a Revenue Systems Audit.