Sales Enablement Aside—Buyer Persona Development: How to Build B2B Personas That Actually Sharpen Your Messaging

By Rick Elmore ·

Last year I sat in on a sales call where a rep spent eleven minutes talking about ROI to a VP of Engineering who clearly didn't care about ROI. He cared about whether the thing would break his team's deploy pipeline. The rep had read the persona doc. The persona doc said "cares about ROI and efficiency." The persona doc was wrong, or more precisely, it was useless—a fictional character assembled in a conference room by people guessing at what buyers want.

That's the problem with most buyer persona development. It produces a laminated one-pager with a stock photo named "Marketing Mary" and a list of traits so generic they apply to every human with a job. Then nobody uses it, because it never told anyone anything they couldn't have guessed. Personas done right are the opposite: they're a distilled record of how real buyers actually think, decide, and say no—and they sharpen every email, call script, and landing page you ship.

Why ICP and buyer personas are not the same thing

This is the mistake I see most often, so let's kill it early. Your Ideal Customer Profile is a company-level filter: industry, headcount, revenue, tech stack, growth stage. It answers "which accounts are worth our time?" It's the gate on your prospecting list.

A buyer persona is a person-level profile. Inside one qualified account, you might be selling to four different humans who all have veto power and completely different motivations. The economic buyer wants to know it pays for itself. The technical evaluator wants to know it won't create work. The end user wants to know it won't make their day harder. The champion wants a win they can take credit for.

Target the account with your ICP. Win the account by speaking to each persona in their own language. When teams blur these together, they end up with "personas" that are really just restated firmographics—and that's why those docs gather dust. If you're still building your account-level targeting, that's a separate workflow, and our revenue system packages handle both layers so they actually connect.

Where real persona data actually comes from

You cannot build a usable persona from a brainstorm. You build it from three sources, and all three are things you already have access to.

Customer interviews are the foundation. Talk to ten to fifteen recent buyers—ideally ones who closed in the last six months, because their memory of the decision is still sharp. Don't ask them what they think of your product. Ask them about the problem that made them start looking. Ask what happened the week they decided they couldn't keep doing it the old way. Ask who else was in the room, who pushed back, and what nearly killed the deal. The goal is to reconstruct the decision, not to collect praise.

The best question I know is: "Walk me through the day you realized you had to fix this." That one question surfaces the trigger, the stakeholders, and the emotional stakes all at once.

Win-loss data tells you what interviews won't. Buyers who chose you are polite and a little biased. Buyers who didn't will tell you exactly where your messaging missed, where a competitor felt safer, and what objection you never answered. If you're not running some kind of structured loss review, start this week. The patterns in why you lose are usually more instructive than the patterns in why you win.

Intent signals show you the trigger in real time. Content a prospect consumes, searches they run, tools they're evaluating, job postings their company publishes—these tell you what's happening in an account right now. A company posting three RevOps roles is signaling a pain your champion is living through today. Intent data converts the static persona into a timing engine: you know not just who to talk to, but when they're feeling the thing you solve.

Put those three together and you get something no imagination could produce: a profile grounded in what people actually did, said, and needed.

The research-to-messaging workflow

Here's the repeatable process I run. It takes about two weeks of focused effort and it's the difference between a document and a weapon.

Step one: collect and transcribe. Record every interview with permission. Pull your last two quarters of closed-won and closed-lost notes. Export your intent and engagement data. Don't synthesize yet. You want the raw material in one place first.

Step two: tag for pains, triggers, and language. Go through the transcripts and mark three things. The pain (what hurts). The trigger (the event that made the pain urgent). And the exact phrasing they used. That last one matters more than people think. When a buyer says "we were flying blind on pipeline," that's your headline. Don't translate it into "lack of pipeline visibility." Keep their words.

Step three: cluster into roles. You'll start seeing groupings. The technical buyers cluster around one set of fears. The economic buyers cluster around another. These clusters are your personas—usually three to five for a B2B deal. Name them by role, not by a cute first name. "VP Engineering, scaling team" is more useful than "Technical Tom."

Step four: build each persona around the decision, not the demographics. For each one, write down: the core pain in their words, the trigger that starts their search, their top two objections, who they answer to, what a win looks like for them personally, and the one message that lands. Skip the hobbies and the fake age. Nobody ever closed a deal knowing the prospect likes hiking.

Step five: map messaging to each persona at each stage. This is where the work pays off. A cold email to the economic buyer and a demo talk-track for the technical evaluator should sound different because the people are different. Write the actual copy, pull from the real language you tagged in step two, and put it where your reps and sequences can use it.

What a usable persona actually contains

Here's the structure I hand to teams. Notice how little of it is demographic.

Element What goes here Why it matters
Role & mandate Their job title and what they're actually measured on Tells you what outcome they need to show their boss
Core pain (verbatim) The problem in their exact words Becomes your headline and opening line
Trigger event What makes the pain urgent enough to act Tells you when to reach out and what to reference
Top objections The two reasons they hesitate or say no Lets you pre-empt the deal-killer in your messaging
Personal win What a successful outcome does for their career Fuels the champion's internal selling for you
Message that lands The one-sentence value framing that resonates The anchor for every touchpoint with this role

Compare that to "Marketing Mary, 38, enjoys yoga and data-driven decisions." One of these tells a rep exactly what to say on a Tuesday afternoon cold call. The other tells them nothing.

How personas sharpen the whole revenue engine

The reason I care about this so much is that personas aren't a marketing deliverable. They're the input layer for everything downstream. When your personas carry real buyer language and real triggers, your cold outreach stops sounding like templated spam because it references the pain the buyer actually feels. Your AI agents and sequences can branch by persona, sending the economic buyer the ROI case and the technical evaluator the integration details, automatically. Your sales calls open on the trigger instead of a generic discovery script.

That's the whole point of building a connected revenue system rather than a pile of disconnected tools. The persona work feeds the targeting, the targeting feeds the automation, and the automation reflects back data that refines the personas. Garbage personas mean garbage at every layer. Sharp personas compound.

And personas decay. The trigger that was urgent last year might be solved by a new tool this year. A new competitor shifts the objections. A market shift changes what buyers get rewarded for internally. Pull fresh interviews and loss reviews into the process every quarter. It's a few hours of work that keeps your entire message aligned with reality.

Frequently asked questions

How many buyer personas does a B2B company actually need?

For a single product, usually three to five—one per distinct stakeholder role involved in the buying decision, not one per job title. If you find yourself with ten, you're probably splitting hairs on demographics instead of clustering by motivation. If you have one, you're almost certainly ignoring the other people who can kill your deal.

How is buyer persona development different from building an ICP?

Your ICP is a company-level filter that decides which accounts you pursue—industry, size, tech stack, growth stage. A buyer persona is a person-level profile of an individual stakeholder inside those accounts: their pain, trigger, objections, and the message that moves them. You need both. The ICP gets you into the right room; the personas help you win everyone in it.

Can I build personas without a budget for formal research?

Yes. The highest-value source costs nothing but time: call ten recent customers and ask them to walk you through their decision. Add your existing closed-won and closed-lost notes and whatever engagement data your tools already capture. You don't need an expensive research firm. You need to actually listen to the people who already bought from you and the ones who didn't.

If your personas are fiction and it's showing up in flat reply rates and stalled deals, we can fix the whole chain—research, targeting, and the automation that acts on it. Book a Revenue Systems Audit and we'll pressure-test what you've got.

Related reading

More articles · Work with us