Sales Enablement Aside—Buyer Persona Development: How to Build B2B Personas That Actually Sharpen Your Messaging
By Rick Elmore ·
Most B2B personas are useless. They're a slide deck nobody opens, a fictional "Marketing Mary" with a stock photo and a list of hobbies that have nothing to do with why she signs a contract. Teams build them once, feel productive, and then write the same generic outreach they would have written anyway.
That's a waste. A good b2b buyer persona isn't a demographic sketch. It's a decision model: what a specific role on the buying committee is trying to accomplish, what they fear, what language they use, and what evidence moves them. Done right, personas change the words you put in front of people. That's the only test that matters.
The short answer: Build one persona per role in the buying committee—not one per company. Ground each in real research (call recordings, win-loss interviews, intent data), capture the role's goals, objections, and vocabulary, then wire those outputs directly into your sequences, landing pages, and discovery questions. If a persona doesn't change what sales and marketing actually say, it's decoration.
ICP vs persona: what each one actually answers
These two get blended together constantly, and the confusion costs you. They answer different questions.
Your ICP (ideal customer profile) describes the company you should sell to: industry, headcount, revenue, tech stack, growth stage, triggers. It's a targeting filter. It tells you which accounts to pour resources into and which to disqualify fast.
Your buyer persona describes the people inside that company who evaluate, champion, block, and approve the purchase. It's a messaging input. It tells you what to say once you're in the room.
| Dimension | Ideal Customer Profile (ICP) | Buyer Persona |
|---|---|---|
| Unit of analysis | The account/company | The individual and their role |
| Core question | Who should we target? | What do we say to them? |
| Example attributes | Industry, size, revenue, tech stack, trigger events | Goals, objections, success metrics, vocabulary, information sources |
| Primary owner | RevOps and demand gen | Sales and product marketing |
| Changes what? | List building and account scoring | Copy, discovery questions, objection handling |
You need both. The ICP gets you to the right door. The persona gets you through the conversation once it opens. Skip the persona work and you'll run technically well-targeted campaigns that still sound like everyone else.
Why one persona per company fails
The biggest mistake I see is building a single persona for a target account. B2B purchases aren't made by one person. A serious deal involves a committee, and each role weighs the decision through a different lens.
Picture a mid-market company evaluating a new revenue platform:
- The VP of Sales cares about quota attainment, ramp time, and pipeline coverage. She wants to hit the number.
- The RevOps lead cares about data cleanliness, integration with the existing stack, and whether this creates more admin work.
- The CFO cares about payback period, total cost, and what gets cut to fund it.
- The CEO cares about whether this moves the strategic needle without becoming a distraction.
Send all four the same email and you'll resonate with maybe one of them by accident. The VP wants to hear about faster ramp. The CFO couldn't care less about ramp—she wants to know the payback math. Same product, different buying questions.
So the rule is simple: build a persona for each distinct role that influences the purchase. At minimum, cover the economic buyer (controls budget), the champion (feels the pain and pushes internally), the technical/operational evaluator (has to live with it), and the blocker (has reasons to say no). You don't need twenty personas. You need the three to five that actually show up in your deals.
Where real persona data comes from
Personas built in a conference room from guesswork are fiction. The useful ones come from sources where buyers reveal what they actually think. Here's where to dig, in rough order of value.
- Call recordings. This is the richest vein you have and most teams ignore it. Pull 15–20 recorded discovery and demo calls per role. Listen for the exact phrases buyers use to describe their problem, the questions they repeat, the moment they lean in, and the moment they go quiet. Note their words, not your paraphrase. If three RevOps leads independently say "I'm drowning in manual data entry," that phrase belongs in your copy verbatim.
- Win-loss interviews. Talk to people who bought and people who didn't. The losses are more valuable—they tell you what your messaging failed to answer. Ask: what nearly stopped you? Who else was in the decision? What did a competitor say that we didn't? Patterns here expose the objections your personas must preempt.
- Intent and behavioral data. What content does each role consume before they engage? What search terms, what topics, what pages? Intent signals show you the questions a persona is asking before they ever talk to you, which tells you what the top of your outreach should address.
- Sales team debriefs. Your reps carry an informal persona model in their heads. Structured conversations—"What's the first objection a CFO always raises?"—surface what they know but haven't written down.
- Direct customer conversations. Short, no-pitch interviews with current customers. Ask about their day, their goals, how they measure success, and how they found you. Keep it about them.
Notice what's not on this list: assumptions, LinkedIn skimming, and inventing a backstory. Hobbies and commute length don't help you close. The persona's success metrics, their objections, and their vocabulary do.
What goes into a persona that sharpens messaging
Strip out the decorative stuff. A persona that actually changes your copy needs a tight set of fields, each tied to a decision the buyer makes. For every committee role, capture:
Role and mandate
What are they accountable for? What does a good quarter look like for this person specifically? This anchors everything—you're selling to their mandate, not their job title.
Goals and success metrics
The outcomes they're measured on. A VP of Sales is measured on attainment and forecast accuracy. Frame your value in terms of the number they report upward. If your message doesn't connect to a metric they own, it's noise to them.
Pains and triggers
The friction that makes them look for a solution, and the events that turn a low-grade annoyance into an active priority. A new funding round, a missed quarter, a competitor's move, a tooling migration. Triggers tell you when to reach out and what to lead with.
Objections and risks
What makes this role hesitate or push back. The CFO's "what's the real payback." The RevOps lead's "this'll break our integrations." Write these down so your sequences and your reps answer them before they're even voiced.
Vocabulary
The actual words this persona uses, lifted from call recordings. Do they say "pipeline coverage" or "enough deals in play"? "Attribution" or "where leads come from"? Matching their language is the fastest way to sound like you understand their world. Mismatched jargon signals you don't.
Information sources and watering holes
Where they learn, who they trust, what they read. This drives channel strategy and the proof points that carry weight—a peer case study versus an analyst report versus a hands-on trial.
That's it. Six fields, each sourced from evidence, each pointed at a decision. A persona document you can act on fits on one page.
How to operationalize personas across sales and marketing
Here's where most persona projects die. The deck gets built, applauded, and filed. Nothing changes. Operationalizing means the persona shows up in the real artifacts your team uses every day.
In outreach sequences. Build a distinct sequence per persona, not per campaign. The champion gets a pain-led message about their daily friction. The economic buyer gets a results-led message about payback and risk. Same account, different threads, coordinated timing. Your sales automation should route and personalize based on role, pulling the right opening line and proof point for each persona automatically.
In discovery. Give reps a persona-specific question set. When they're talking to the RevOps lead, the discovery leans into integration and data workflow. With the CFO, it leans into budget cycle and payback expectations. This turns "good rep instinct" into a repeatable process.
In content and landing pages. Map every asset to the persona and buying stage it serves. A champion needs an internal business case they can forward. An economic buyer needs an ROI summary. A technical evaluator needs a security and integration page. If an asset doesn't map to a persona's actual question, reconsider why it exists.
In lead scoring and routing. Persona identity should feed your scoring. A director at a target account behaves differently from an intern, and your RevOps model should weight the economic buyer's engagement higher than a tangential role's. When personas, ICP, and intent data all live in one system, scoring gets sharp instead of mushy.
Keep them alive. Personas aren't a one-time project. Re-pull call recordings quarterly. New objections surface, vocabulary shifts, triggers change with the market. Assign an owner—usually product marketing with RevOps—to refresh them on a cadence. A persona built two years ago and never updated is close to useless now.
The thread running through all of this: personas are only valuable when they're wired into the system that sales and marketing actually run on. A persona in a slide deck is an opinion. A persona driving your sequences, scoring, and discovery scripts is an operating asset.
Where this fits
Persona work sits between your targeting and your messaging. The ICP decides which accounts you chase; the personas decide what you say to the humans inside them. Get both right and your outreach stops sounding interchangeable with every other vendor in the inbox. The hard part isn't writing the personas—it's connecting them to the tools your team uses so the research actually changes behavior. That's a RevOps and systems problem as much as a marketing one, which is exactly where the lead gen, sales automation, and AI-agent layers of an integrated revenue engine earn their keep. If you want to see how persona-driven messaging gets built into sequences and scoring end to end, our packages lay out the options.
If your personas are collecting dust while your outreach still sounds generic, let's fix the whole chain. Book a Revenue Systems Audit and we'll show you where your messaging is leaking and how to wire personas into a system that compounds.