Sales Enablement Aside—Buyer Persona Development: How to Build B2B Personas That Actually Guide Messaging and Targeting
By Rick Elmore ·
Most of the personas I see in B2B are fiction. Someone in marketing built a slide deck two years ago with a stock photo, a made-up name like "Marketing Mary," and a bulleted list of goals that could apply to literally anyone with a pulse and a budget. It lives in a shared drive. Nobody uses it. And the reps? They're running their own mental model of who they're actually talking to, which is usually more accurate than the official document.
That gap is the whole problem. A buyer persona is only worth building if it changes what you say, who you target, and how a rep handles the third objection on a discovery call. Everything else is decoration.
So let's talk about how to do buyer persona development in a way that actually moves numbers—not the version that wins a branding award.
- Personas describe individual buyers (roles, pains, triggers, objections). Your ICP describes which accounts to go after. They're different tools and you need both.
- Build personas from real conversations and CRM data, not internal guessing. If you can't quote a customer, you're inventing.
- A persona is only "done" when it produces messaging, targeting filters, and rep talk tracks. Otherwise it's a poster.
- Most B2B deals involve 4–8 people. You need a persona for each role that can kill or advance the deal, not just the one who signs.
- Triggers and objections are the highest-leverage fields. They tell you when to reach out and what will stop the deal.
Persona vs ICP: stop conflating them
This is the mistake that breaks everything downstream, so I want to kill it early.
Your Ideal Customer Profile is a firmographic filter for accounts. Company size, industry, tech stack, revenue band, geography, growth stage. The ICP answers: "Which companies should we spend money trying to reach?" It's the guest list for the party.
A buyer persona is a portrait of a human inside those accounts. What they own, what they're measured on, what keeps them up at night, what makes them pick up the phone, and what makes them ghost you. The persona answers: "When we get in front of a specific person, what do we say?"
| Dimension | ICP (accounts) | Buyer persona (people) |
|---|---|---|
| Unit | The company | The individual buyer |
| Drives | Targeting, list building, ad spend allocation | Messaging, talk tracks, objection handling |
| Key fields | Industry, size, tech stack, funding, geo | Role, pains, triggers, objections, buying power |
| Owned by | RevOps and demand gen | Marketing and sales together |
You use the ICP to decide which 3,000 companies deserve outreach. You use personas to decide what the email to the VP of Ops says versus what the email to the CFO says. Confuse the two and you get generic account-level messaging blasted at humans who have completely different jobs.
Start with conversations, not brainstorms
The fastest way to build useless personas is to lock five internal people in a room and ask them what customers want. What you'll produce is a summary of your own assumptions, dressed up as research.
Real persona development starts with data you already have and conversations you can still go get. Here's where I actually look:
Won and lost deal recordings. Gong, Fathom, whatever you use. Go listen to 15 or 20 calls. Not the highlight reel—the messy ones. You're mining for the exact language buyers use to describe their problem, and the exact moment a deal stalled. When a prospect says "I just need something my team will actually log into," that's a persona pain, in their words, ready to drop into a subject line.
Your CRM. Filter closed-won deals from the last 12 months. Who were the champions? What titles kept showing up? Which deals closed fast and which dragged? Patterns in your own pipeline beat any external report because they describe your buyer, not the market average.
Direct interviews. Get 30 minutes with five recent customers. Ask what they were trying to fix, what almost stopped them from buying, and who else had to say yes internally. That last question is how you discover the personas you've been ignoring.
Sales team debriefs. Reps carry the sharpest persona intel in the company and it's usually trapped in their heads. Ask them: "When you get on with a Head of Sales versus a founder, how does the conversation change?" Write down the answers verbatim.
The rule I hold to: if I can't attach a real quote or a real deal to a persona attribute, it doesn't go in the document. No quote, no field. That single constraint kills most of the fiction.
The fields that actually matter
Forget the persona templates with 40 fields including favorite podcasts and morning routine. In B2B, five fields drive nearly all the value. Everything else is padding.
Role and buying power
What do they own, and what can they do in your deal? There's a big difference between a persona who can sign, one who can champion, and one who can only veto. A VP of Marketing might love your product and have zero budget authority. A CFO might not care about features at all but controls whether the deal happens. Tag each persona with their function in the buying committee: economic buyer, champion, user, blocker, technical evaluator. Your messaging changes completely based on that role.
Pains, in their words
Not "wants to improve efficiency." That's meaningless. The real pain is "I'm spending Friday afternoons manually pulling numbers from four tools to build a report nobody reads." Specific, concrete, and quotable. If your pain statement could describe any buyer in any industry, you haven't found the pain yet.
Triggers
This is the most underused field in all of persona work. A trigger is the event that turns a passive buyer into an active one. A new VP getting hired. A funding round. Missing a quarterly number. A competitor's product outage. A tool renewal coming up. When you know the triggers, your outreach stops being random and starts being timely. Timing beats messaging more often than people admit.
Objections
Every persona has predictable reasons they'll hesitate, and they cluster by role. The CFO objects on price and ROI proof. The IT lead objects on security and integration. The end user objects on "another tool to learn." If you know the top three objections per persona before the call, your reps stop getting surprised and your marketing can preempt them in the content itself.
Where they already are
Which channels, communities, and sources they actually trust. A technical buyer lives in different places than a revenue leader. This tells demand gen where to show up instead of spraying every channel equally.
Build a persona for every seat at the table
Here's a trap I watch teams fall into constantly: they build one glorious persona for the decision-maker and forget the deal actually runs through a committee. In most B2B purchases of any real size, you've got a champion pushing internally, a user who has to adopt it, a finance gatekeeper watching the spend, and sometimes an IT or security reviewer with veto power.
Each of those people needs their own persona because each of them can kill your deal for a completely different reason, and each responds to completely different messaging. You don't need one for every job title in the org. You need one for every role that can advance or block the purchase.
A practical test: map your last five won deals and your last five lost deals. Who was involved? Who advocated? Who resisted? The roles that repeat are your real personas. If a "blocker" role shows up in three of your five lost deals, that's not an edge case—that's a persona you've been failing to message to, and it's costing you.
Turn personas into messaging, targeting, and talk tracks
This is the step where 90% of persona work dies. The document gets built, everyone nods, and then it goes in a drawer. A persona that doesn't produce these three outputs is incomplete, full stop.
Messaging. Every persona's pain and top objection should map directly to a value proposition and a piece of proof. If the champion's pain is "my current tool has terrible adoption," your message to them leads with ease of use and includes a proof point about how fast teams ramp. Same product, different angle per persona. This is how you go from one generic pitch to messaging that lands because it sounds like it was written for that specific person.
Targeting. Persona attributes become filters. Title, seniority, and department turn into list-building criteria. Triggers turn into intent signals your campaigns watch for. When we build an AI-native revenue engine, this is where personas connect to automation: a trigger event fires, the system knows which persona was hit, and it deploys the right message sequence automatically. That only works if the persona was built with real, filterable attributes instead of vibes.
Talk tracks. Give reps a one-page cheat sheet per persona: the three pains to probe for, the three objections to expect with responses, and the language this persona actually uses. New reps ramp faster and experienced reps stop winging it on unfamiliar personas. This is where enablement and persona work finally connect—the persona is the enablement asset.
If you want to see how we wire personas into an end-to-end system—from targeting through automated sequencing to rep-ready talk tracks—that's the core of what we build in our revenue engine packages.
Keep them alive
Personas rot. Buyer priorities shift, new triggers emerge, objections change as the market matures. The teams that get real value treat personas as living documents, not one-time deliverables. I'd revisit them at least quarterly, and any time you notice a pattern change in your win/loss calls.
The signal that a persona needs updating is simple: reps stop trusting it. The day a rep says "that objection isn't really what I'm hearing anymore," you update the persona that same week. The document has to stay closer to reality than the rep's gut, or the rep will just ignore it—and they'll be right to.
Frequently asked questions
How many buyer personas does a B2B company actually need?
Usually three to five for a given product. One for each role that can meaningfully advance or block a deal—typically the economic buyer, the champion, the primary user, and any technical or finance gatekeeper. If you're building more than six, you're probably slicing too finely or confusing persona development with market segmentation.
What's the difference between a buyer persona and an ICP?
The ICP defines which accounts to target using firmographic filters like size, industry, and tech stack. A buyer persona defines the individual people inside those accounts—their roles, pains, triggers, and objections. The ICP drives who you spend money reaching; personas drive what you say once you reach them. You need both, and they do different jobs.
Do personas still matter if we're running account-based marketing?
More than ever. ABM picks the accounts, but every account is still a committee of humans with different motivations. Personas are what let you tailor the message to each member of the buying committee inside a target account. Without them, ABM is just expensive spray-and-pray aimed at a shorter list.
If your personas are collecting dust while your reps run on instinct and your campaigns speak to everyone and no one, that's fixable—and it usually shows up in pipeline within a quarter. Book a Revenue Systems Audit and we'll map your real buyers to your messaging, targeting, and talk tracks.