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 are fiction. Someone built a slide with a stock photo of "Marketing Mary," gave her a job title, a coffee habit, and a vague goal like "wants to grow the business." Then it went into a Google Drive folder and never influenced a single email, call script, or landing page. That's not persona work. That's a craft project.
Here's what I've learned running outbound and RevOps systems: a persona is only worth building if it changes what you say and who you say it to. If your messaging reads the same before and after the persona exercise, you wasted a week. So this is a playbook for buyer persona development that actually sharpens your outreach—built around the real humans on a B2B buying committee, not a company-shaped abstraction.
- Personas are about people on the buying committee; your ICP is about the account. You need both, and they do different jobs.
- The useful parts of a persona are pains, triggers, objections, and decision criteria—not demographics or fake personality quirks.
- Research comes from real conversations: won deals, lost deals, and sales call recordings. Not a brainstorm in a conference room.
- A persona that doesn't produce specific message angles and objection responses isn't finished.
- In most B2B deals you're selling to three to five roles at once. Build a persona for each one that touches the decision.
Why ICP and buyer personas are not the same thing
People use these interchangeably and it causes real damage. Your Ideal Customer Profile describes the company you want to land: industry, headcount, revenue, tech stack, growth stage, the trigger events that make them a fit. The ICP tells your SDRs which doors to knock on and keeps you from wasting time on accounts that will never close or will churn in ninety days.
A buyer persona describes a person inside that company. Same account can contain five of them, and they want different things. The VP of Sales cares about pipeline and quota attainment. The RevOps lead cares about clean data and whether your tool will create three new manual processes. The CFO cares about payback period. The individual rep who'll actually use the thing cares about whether it makes their day harder. Sell the CFO's message to the end user and you lose. Sell the end user's message to the CFO and you lose.
Put simply: the ICP gets you into the building. Personas tell you what to say to each person once you're inside. You need the account-level targeting to be efficient, and you need the human-level personas to be persuasive. Skip either one and your outreach either hits the wrong companies or says the wrong things to the right ones.
Start with the buying committee, not a single hero buyer
The biggest mistake in buyer persona development is building one persona and treating the deal like a single-threaded sale. Real B2B purchases get decided by a committee, and the committee is where deals die. One champion loves you, forwards your proposal internally, and it quietly dies because the person who controls the budget never heard a reason to care, or the technical evaluator flagged an integration risk nobody addressed.
So before I write a word of persona content, I map the committee. For a given deal, who are the roles that touch it? I usually sort them into four buckets:
- Economic buyer — signs off on spend, measures ROI. Often absent from early calls and shows up late to kill or approve the deal.
- Champion — feels the pain most acutely and wants this solved. Your inside seller. But they rarely have final authority.
- Technical/operational evaluator — the person who has to make it work, integrate it, or live with it. Can veto on risk alone.
- End user — whoever uses the product daily. Their buy-in determines whether you churn after you win.
Build a persona for each role that genuinely influences the decision. If you sell a $2k/month tool, maybe that's two personas. If you sell a $150k platform, it might be five. The point is to stop pretending the deal rests on one person's opinion.
How to research buyer personas without making it up
Real persona research is unglamorous. It's not a workshop with sticky notes. It's going to the source and listening to how buyers actually talk. Here's where the signal lives.
Won-deal interviews. Call ten recent customers. Ask them what was going on in their world when they started looking. What finally pushed them to act? What almost stopped them from buying? Who else was involved in the decision, and what did those people worry about? The language they use is gold—copy it down verbatim, because that's the phrasing that will make your outreach feel like it was written by someone who gets it.
Lost-deal interviews. Harder to get, more valuable. The people who said no will tell you exactly which objection you failed to handle and which competing priority beat you. Lost deals reveal the objections you've been avoiding.
Sales call recordings. If you record calls, you're sitting on the best persona research available. Search transcripts for the moments buyers push back, go quiet, or get excited. Note the exact phrases. Patterns show up fast—the same three objections, the same two triggers, over and over.
Your own team. Your best AE knows the personas cold even if they've never written one down. Debrief them. What makes a VP of Sales lean in versus tune out? What does the RevOps person always ask about?
What I deliberately ignore: made-up hobbies, favorite brands, a fabricated daily routine. None of it changes a sentence in your email. If a data point won't alter your messaging or targeting, leave it out.
What goes into a persona that's actually useful
I keep persona docs tight. One page per persona, four sections that do real work:
| Section | What it captures | How it changes your messaging |
|---|---|---|
| Pains | The specific problems this role loses sleep over, in their words | Your opening line and value prop lead with the pain they recognize instantly |
| Triggers | Events that move them from "someday" to "now"—new hire, missed quarter, funding, tool failure | Timing and targeting: you reach out when the trigger is fresh, and reference it |
| Objections | The real reasons they stall or say no, including the unspoken ones | You pre-empt objections in sequences and arm your reps with responses |
| Decision criteria | What they actually judge the purchase on—ROI, risk, ease, status, time saved | Your proof points and case studies get matched to what each role weighs |
Notice what's not on there. No age range, no stock photo, no "enjoys hiking." Those details feel like progress and deliver nothing. The four columns above are the engine. Everything else is decoration.
One more thing I add to each persona: a short section on how this role talks. A CFO and an SDR describe the same problem in completely different vocabularies. Capturing the actual language—"blown quarter," "data hygiene," "ramp time," "burn"—is what makes your copy sound native instead of like a vendor reading from a script.
Plugging personas into messaging and outreach
This is the part everyone skips, and it's the only part that matters. A persona doc that sits in a folder is worthless. The whole point is to drive it directly into your sequences, scripts, and pages.
Start with your outbound sequences. For each persona, write the email that leads with their pain and references their trigger. The RevOps lead gets a message about messy pipeline data and manual handoffs. The VP of Sales gets one about rep ramp time and missed forecast. Same product, two completely different first lines. When you multi-thread an account, each contact should get the version built for their role—not a blast of the same generic pitch.
Then take your objections and build them into the sequence itself. If the technical evaluator always worries about integration, your third touch should address integration before they even raise it. Pre-handling objections in the sequence shortens cycles because it removes the stall points before they stall.
Match your proof to decision criteria. If the economic buyer judges on payback period, your case studies for that persona lead with payback period, not feature lists. If the end user cares about ease, show the interface and the time saved. Same case study, framed around what each role weighs.
This is where the work compounds. When you run AI-assisted outreach and sales automation, personas become the instruction set that makes personalization scale. The system knows which role it's writing to and pulls the right pain, trigger, and proof point automatically. That's the difference between automation that sounds robotic and automation that sounds like a human who did their homework. We build this persona-to-sequence connection into every engine we deploy—you can see how it fits into the broader system on our pricing and packages page.
Keep personas alive or they rot
Buyers change. The triggers that worked last year fade, new objections appear when a competitor shifts positioning, and new roles enter the buying committee as a category matures. A persona built once and never revisited slowly drifts from reality until it's lying to you.
I treat personas as living documents tied to a review rhythm. Every quarter, pull the latest won and lost deals and check: are the pains still the same? Did a new objection show up? Is a new role now part of the decision? The maintenance is light if you do it regularly and painful if you let it lapse for two years. Tie the review to your pipeline reviews so it doesn't get forgotten.
The signal that your personas are working is simple. Reply rates on persona-specific sequences beat your generic ones. Reps stop getting ambushed by objections. Deals move through the committee instead of stalling with a single champion. When those things start happening, you'll know the persona work was real and not a craft project.
Frequently asked questions
How many buyer personas does a B2B company actually need?
One per role that genuinely influences a purchase decision, not one per job title. For most B2B deals that's three to five: economic buyer, champion, technical evaluator, and end user. If a role never touches your deals, don't build a persona for it. Resist the urge to split hairs—two slightly different VP titles with identical pains and objections are one persona.
What's the difference between a buyer persona and an ideal customer profile?
An ICP describes the company you want to sell to—industry, size, tech stack, trigger events. A buyer persona describes an individual human on that company's buying committee—their pains, triggers, objections, and decision criteria. The ICP controls targeting at the account level; personas control messaging at the human level. You need both, and they answer different questions.
How do I build buyer personas if I don't have many customers yet?
Interview prospects and your own sales conversations instead of customers. Even a dozen discovery calls reveal the recurring pains, triggers, and objections. You can also mine your competitors' reviews and the communities your buyers hang out in for the language they use. Start with a rough draft built from first-principles reasoning and tighten it every time you talk to a real buyer. A directional persona beats no persona.
If your personas are stock photos in a folder and your outreach says the same thing to everyone, the fix is a system that connects research to sequences. Book a Revenue Systems Audit and we'll show you where your messaging is missing the people who actually decide.