Sales Enablement Aside—Buyer Persona Development: How to Build B2B Personas That Actually Change Your Messaging
By Rick Elmore ·
Most buyer personas are useless. They're demographic trading cards — "Marketing Mary, 38, likes yoga and data-driven decisions" — that live in a slide deck nobody opens after the offsite. If your persona work doesn't change a single subject line, a single discovery question, or a single objection-handling rep, you didn't build a persona. You built decoration.
Here's the reframe I push every revenue team toward: buyer persona development is not about who your buyer is. It's about what makes them move, what makes them stall, and how those two things differ across the four or five people who have to say yes. Below is how we build personas that actually earn their keep.
1. Separate persona work from ICP work — they answer different questions
Your ICP (ideal customer profile) is an account-level filter: company size, industry, tech stack, revenue, growth stage. It tells you which doors to knock on. Personas operate inside those doors. They tell you what to say once someone opens it. Teams that blur the two end up with "personas" that are really just firmographics wearing a name tag.
Keep the division clean:
- ICP = account-level fit. Who's worth targeting?
- Persona = individual-level psychology. What does this human fear, want, and get measured on?
Your ICP might be "Series B SaaS companies with 50–200 employees." Your personas are the VP of Sales who owns the number, the RevOps lead who inherits the mess, and the CFO who signs off. Same account, three completely different conversations.
2. Map personas to buying-committee roles, not job titles
B2B deals aren't won by convincing one person. They're won by a committee, and each seat on that committee plays a distinct role regardless of what's on the business card. Build your personas around the job to be done inside the deal, not the title in the org chart.
- Economic buyer — controls budget, cares about ROI and risk.
- Champion — feels the pain daily, will sell internally for you if you arm them.
- Technical/operational evaluator — decides whether it actually works and who has to maintain it.
- Blocker — the person who benefits from the status quo or gets more work from the change.
A CFO can be an economic buyer in one deal and a blocker in another. Building personas around roles instead of titles forces you to write messaging for the function each person serves in the purchase.
3. Do the research, or you're just writing fiction
The reason most personas feel hollow is that someone made them up in a conference room. Real persona development pulls from evidence. You want direct language, not paraphrased assumptions.
Sources worth mining:
- Win/loss interviews — the highest-signal input you have. Ask why they chose you, what almost stopped them, and who pushed back internally.
- Sales call recordings — search transcripts for the exact objections and phrases buyers repeat.
- Support and onboarding notes — where the "day one" pain shows up in the customer's own words.
- Lost deals and closed-lost reasons — the objections you never overcame tell you what the persona actually cared about.
You don't need fifty interviews. Ten focused conversations per persona will surface the patterns. When three different champions use nearly the same sentence to describe their frustration, you've found messaging gold.
4. Capture pains at the individual level, not the company level
"The company wants to increase pipeline" is a business goal, not a persona pain. It's too abstract to write a compelling email around. Personas move on personal stakes: what makes this individual look good, what makes them look bad, and what wakes them up at 2 a.m.
For each persona, get specific:
- What are they personally measured on this quarter?
- What makes them look incompetent in front of their boss?
- What's the manual, annoying task they'd love to make disappear?
A VP of Sales doesn't buy your automation because "efficiency is good." She buys it because she's tired of explaining a missed number to the board and blaming reps for admin work she can't fix. That's the sentence that changes your messaging.
5. Identify the triggers that turn a persona from passive to active
Most of your market isn't buying today. The persona work that matters most is figuring out what event flips someone from "this is fine" to "I need to fix this now." Triggers are what let you time your outreach and lead with relevance instead of a generic pitch.
Common trigger categories:
- Role change — a new VP has 90 days to prove they can improve the number.
- Painful milestone — a blown quarter, a failed launch, a churn spike.
- Scaling pressure — headcount grew but the process didn't, and now everything's on fire.
- Tool failure — the current stack broke or a contract is up for renewal.
When you know the trigger, your opening line stops being "I wanted to reach out about our platform" and becomes "Congrats on the new role — most VPs in your seat spend the first quarter fighting the same reporting mess." That lands because it names the moment they're actually in.
6. Document objections per persona and build the counter into your messaging
Every persona carries a predictable set of objections, and they're different across the committee. The economic buyer's objection is "is this worth the money and how risky is it." The technical evaluator's is "who has to build and maintain this." The champion's is "will I look stupid for recommending it."
For each persona, write down the top three objections and, next to each, the exact reframe or proof that neutralizes it. Then feed those reframes into your sequences, your discovery scripts, and your landing pages. Objection handling shouldn't live only in a rep's head during a call. It should be baked into the content the persona reads before they ever talk to you.
7. Translate every persona into concrete messaging changes
This is the test that separates real persona work from theater. For every persona you build, you should be able to point to specific assets that changed because of it. If nothing changed, you learned nothing.
What should shift:
- Subject lines and openers tied to that persona's trigger.
- Value props reordered so the lead benefit matches what that role is measured on.
- Proof points swapped — the CFO wants payback math, the champion wants a peer story.
- Discovery questions written to surface each persona's specific pain.
- Objection-handling snippets ready for the reps in the flow of the deal.
We build this directly into the sequences and AI agents that run our clients' outreach, so the persona logic lives in the system rather than in a document. If you want to see how that gets operationalized end to end, it's part of how we structure our engagement packages.
8. Keep personas alive with a feedback loop
Buyers change. Markets shift. A persona built eighteen months ago describes a buyer who no longer exists. The teams that get value from persona development treat it as a living asset, not a one-time project.
Set a simple cadence: every quarter, pull the objections that actually came up on calls, the triggers that preceded your best deals, and the language from recent win/loss interviews. Compare it to your documented personas and update. When your messaging response rates dip, the persona is usually the first place the drift shows up.
9. Don't build more personas than you can act on
The instinct to map every possible stakeholder produces a binder of personas that no one uses. Start with the two or three that actually decide your deals — usually the economic buyer and the champion, plus whichever evaluator kills the most deals. You can always add more once the first ones are driving measurable messaging changes.
A tight set of well-researched personas that changes how you sell beats a comprehensive library that changes nothing. Depth over coverage, every time.
Frequently asked questions
What's the difference between a buyer persona and an ICP?
An ICP describes the ideal account — company size, industry, growth stage, tech stack — and tells you which organizations to target. A buyer persona describes an individual inside that account: their personal pains, buying triggers, and objections. You use the ICP to decide who to reach out to and personas to decide what to say once you're in the conversation. You need both, but they solve different problems.
How many buyer personas should a B2B company have?
Fewer than you think. Start with the two or three roles that actually control your deals — typically the economic buyer, the champion, and whichever evaluator most often blocks the sale. More personas only help if each one drives distinct messaging you'll actually deploy. If two personas would get the same email, they're one persona.
How do I know if my personas are actually working?
Look for concrete changes downstream. Did your subject lines, value-prop ordering, discovery questions, or objection handling shift because of the persona? Then track response and conversion rates on the messaging tied to each persona. If reply rates and meeting-booked rates improve on persona-specific sequences versus generic ones, the work is paying off. If nothing changed operationally, you built a document, not a persona.
If your personas are gathering dust while your messaging stays generic, the fix isn't more research — it's wiring persona logic into the systems that run your outreach. Book a Revenue Systems Audit and we'll show you where your messaging is leaking deals.