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

By Rick Elmore · 2026-10-15

I've watched a lot of sales teams spend a quarter building a beautiful "ideal customer profile" deck, then run cold sequences that open with "Hope you're doing well." The ICP work was real. The messaging was generic. That gap is almost always a persona problem, not a targeting problem.

Here's the distinction that matters: your ICP tells you which companies to go after. Your buyer personas tell you how to talk to the actual humans inside those companies who will approve, block, or champion your deal. Most B2B teams blur the two together and end up with messaging that's technically "on-target" but says nothing specific to the person reading it.

• An ICP is account-level. A b2b buyer persona is role-level. You need both, and they do different jobs.
• Modern B2B deals are decided by a committee, not a single buyer. Build a persona for each seat at the table, not just the champion.
• The useful parts of a persona are pain points, trigger events, and objections tied to a role—not demographics or made-up personality quirks.
• Personas that live in a slide deck are decoration. Personas wired into sequences, call scripts, and enablement actually move pipeline.
• Build personas from conversations and deal data, not from guessing. Ten honest customer calls beat a hundred survey responses.

Why ICP and buyer persona are not the same thing

I'll make this concrete. Your ICP might be: "Series B to C SaaS companies, 200 to 800 employees, US-based, selling into mid-market, with a founder-led sales motion they're trying to professionalize." That's a filter. It tells your SDRs which logos belong in the list.

But when your rep actually opens a conversation at one of those accounts, they're not talking to "a Series B SaaS company." They're talking to a VP of Sales who's six months into the job and worried about hitting number, or a RevOps lead who's drowning in a broken tech stack, or a CFO who sees your category as a cost line to defend against. Same account. Three completely different conversations.

The ICP qualifies the account. The persona wins the person. When teams skip persona work, every message defaults to the lowest common denominator—vague value props that could apply to any company in any industry. That's the "Hope you're doing well, I wanted to reach out about our solution" email that gets deleted in half a second.

Build personas around the buying committee, not the buyer

The single biggest mistake I see is building one persona—usually the economic buyer or the most obvious user—and calling it done. In B2B, that's a fiction. Deals of any real size get decided by a group, and that group has at least three functional roles you need to speak to differently.

I think about the committee in terms of jobs, not titles, because titles vary wildly across companies:

• The champion. The person who feels the pain most directly and wants this solved. They'll sell internally for you, but only if you arm them well.
• The economic buyer. The person who controls budget and has to justify the spend. Often cares less about features and more about risk, ROI, and what happens if this fails.
• The technical or operational evaluator. The person who has to make it work. Security, integrations, implementation load, "who's going to own this?"
• The blocker. Not always a formal role, but someone whose world changes if you win. The incumbent vendor's internal advocate, the person who built the current manual process, the skeptic.

Each of these people has a different reason to say yes and a different reason to kill the deal. A persona document that only captures the champion gives your team a false sense of confidence. The deal stalls in "legal review" or "we decided to revisit next quarter," and nobody understands that the real blocker was a security evaluator who never got a single message aimed at their concerns.

What actually belongs in a B2B buyer persona

Strip out everything that doesn't change what your rep says or writes. I don't care that the persona's name is "Marketing Mary" or that she enjoys yoga. That's theater. Here's what earns its place:

Role-based pain points

What is this person measured on, and where are they currently failing or at risk? A VP of Sales is measured on pipeline coverage and attainment. A RevOps lead is measured on forecast accuracy and system reliability. A CFO is measured on efficient growth. The pain has to be written from their scoreboard, not yours. "Our tool improves efficiency" is not a pain point. "Your reps spend half their day on manual data entry instead of selling" is.

Trigger events

Triggers are the reasons someone starts looking now instead of living with the problem forever. New leadership hire. A funding round that comes with growth expectations. A bad quarter. A tool that got acquired and is sunsetting. A new compliance requirement. When you know the triggers per role, your SDRs can time outreach and your messaging can reference the actual moment the buyer is in. This is what separates relevant outreach from spray-and-pray.

Objections and decision criteria

For every persona, write down the three to five objections you reliably hear from that role, and the criteria they use to judge options. The economic buyer's objection isn't the evaluator's objection. Document them separately. This becomes your rebuttal library and, honestly, your best source of content ideas—every real objection is a landing page or a case study waiting to be written.

Language they actually use

Capture the exact words buyers use to describe their problem. Not your category jargon—theirs. If RevOps leads say "our data is a mess" and you keep saying "data governance infrastructure," you sound like an outsider. Mirroring real language is the cheapest way to make messaging feel like it was written for one person.

Here's a simple way to see the difference across a committee:

How to build personas from real research, not guesses

You cannot build a useful persona in a conference room with a whiteboard and opinions. You'll just document your assumptions in a nicer font. The input has to be real.

Start with won-deal interviews. Call ten customers who recently bought and ask them to walk you through the whole decision: what pushed them to start looking, who else was involved, what almost stopped them, what nearly made them pick someone else. Ten of these conversations will teach you more than any report. Then do the same with a few lost deals and stalled deals—those tell you where your current messaging is failing by role.

Layer in the data you already have. Pull your sales call recordings and read the objection patterns. Mine your CRM for which titles actually appear in closed-won opportunities versus which ones you assumed would be the buyer. Read the questions prospects ask in demos. Check what pages people actually visit before they book a call. The evidence is sitting in your systems; most teams just never assemble it.

Then write each persona tight. One page, maximum. Role and the jobs they're accountable for, their top pains in their words, the triggers that make them buy, their objections, and the one outcome they most want. If it doesn't fit on a page, you've added theater back in.

Wiring personas into messaging, sequences, and enablement

This is where most persona projects die. The deck gets built, everyone nods, and three weeks later the reps are writing emails the old way. A persona only earns its keep when it changes the words that go out the door.

Start with outbound sequences. Instead of one sequence for an account, build persona-specific tracks. The email that lands with a RevOps lead opens with the data mess, not the revenue upside the CFO cares about. The CFO track leads with payback and risk. Same account, parallel conversations, each one relevant. When we build multi-threaded sequences inside a revenue engine, this is the backbone—every seat on the committee gets messaging aimed at their actual scoreboard, and the system tracks who's engaging so reps know where the deal really stands.

Next, feed them into your call framework. Your discovery questions should change based on who's on the call. Your reps should know the three objections that role tends to raise before they raise them. That's not scripting people into robots; it's giving them the context to sound like they've solved this exact problem for this exact kind of person before. Because they have.

Then enablement content. Each persona's objections become a content map. One-pagers for the evaluator, an ROI model for the economic buyer, a quick-win story for the champion to forward internally. The champion almost never closes the deal alone—they need ammunition to sell your solution to the committee when you're not in the room. Build that ammunition per persona.

Finally, keep them alive. Personas aren't a one-time project. Every quarter, your reps surface new objections and new triggers from live deals. That feedback has to flow back into the documents, the sequences, and the content. When the loop is closed, your messaging gets sharper every quarter instead of going stale. If you want to see how this gets built as one connected system rather than a pile of disconnected docs, that's exactly what our packages are designed to stand up.

Frequently asked questions

How many buyer personas does a B2B company actually need?

Fewer than you think, but more than one. For most B2B motions, three to five personas covering the core committee roles is right—typically a champion, an economic buyer, and a technical or operational evaluator. If you find yourself building ten, you're probably confusing minor title variations with genuinely different buying motivations. Build personas around distinct pains and decision criteria, not around every job title in your CRM.

What's the difference between an ICP and a buyer persona?

An ICP describes the account you want—firmographics like industry, size, growth stage, and tech stack. It tells you which companies to pursue. A buyer persona describes an individual role inside that account—their pains, triggers, and objections. It tells you how to talk to that person. You use the ICP to build the list and the persona to win the conversation. Neither works well without the other.

How often should buyer personas be updated?

Treat them as living documents. Do a light review every quarter using objections and triggers your reps heard in live deals, and a deeper refresh once a year or whenever your market shifts—new competitors, a pricing change, a new category of buyer entering the committee. Personas that never get updated quietly drift away from reality, and your messaging drifts with them.

If your personas are sitting in a slide deck instead of driving your sequences and scripts, that's fixable—and it's usually the fastest lever for sharpening pipeline. Book a Revenue Systems Audit and we'll map your buying committee to your messaging, end to end.

Related reading

• AI Content Repurposing: Turn One Asset Into a Month of Content
• GEO & AEO: How to Get Your B2B Brand Cited by AI Search