Sales Enablement Aside—Buyer Persona Development: How to Build B2B Personas That Actually Shape Messaging and Targeting
By Rick Elmore ·
Last quarter I sat in on a messaging workshop where a marketing team proudly walked through their buyer persona. "Marketing Mary," they called her. She liked coffee, worked long hours, and "valued efficiency." There was a stock photo. There was a fake quote. What there wasn't: a single reason anyone in that room would write a different email, pick a different channel, or change who they called first.
That's the problem with most buyer persona development. It produces an artifact nobody uses. A persona only earns its keep if it changes a decision — what you say, where you say it, and who you say it to. Everything else is a poster for the wall.
- Personas operate at the person level; ICP operates at the account level. You need both, and they do different jobs.
- Demographics don't drive buying. Problems, triggers, and internal politics do. Build personas around jobs-to-be-done and the pressure each role is under.
- B2B is a committee sport. Map the champion, the economic buyer, the blocker, and the end user separately — they want different things.
- If a persona doesn't change your messaging, channel, or targeting, it's decoration. Every field should earn its place by informing an action.
- Mine real data, not imagination. Call notes, lost-deal reviews, and sales objections beat any template.
Buyer persona vs ICP: stop conflating them
These two terms get used interchangeably and it causes real damage. Your ideal customer profile (ICP) describes the account: industry, headcount, revenue, tech stack, growth stage, the business conditions that make a company a good fit. A buyer persona describes a person inside that account: their role, what they're measured on, what keeps them up at night, how they buy.
Here's why mixing them up hurts. ICP decides which companies land on your target list. Persona decides what you say to the five people inside that company who touch the deal. If you only have an ICP, you'll pick the right accounts and send them generic messaging that bounces off everyone. If you only have personas, you'll write compelling emails to companies that were never going to buy.
| Ideal Customer Profile (ICP) | Buyer Persona | |
|---|---|---|
| Level | Account / company | Individual / role |
| Answers | Which companies should we target? | What do we say to the people inside them? |
| Built from | Firmographics, tech stack, trigger events | Role, goals, pains, buying behavior, objections |
| Drives | List building, routing, territory, scoring | Messaging, channel, sequence copy, offers |
In the revenue engines we build at FullStackCloser, ICP and persona feed different parts of the machine. ICP powers the targeting layer — who gets added to campaigns. Personas power the messaging layer — what each contact actually reads. When both are tight, outbound stops feeling like spam and starts feeling like you read someone's mind.
Why most personas never change a single decision
The failure mode is predictable. A team downloads a template with twenty fields, fills them in with plausible guesses, and ships it. The fields that would actually change behavior — the real trigger that makes someone start looking, the exact objection that kills deals, the phrase a buyer uses to describe their own problem — get skipped because they're hard. The easy fields (age range, favorite tools, "hobbies") get filled because they're easy.
Then nobody opens the document again.
The fix is to flip the exercise. Don't start with "what do we want to know about this person." Start with "what decisions do we make every week that this persona should inform." You make messaging decisions, channel decisions, and sequencing decisions. So build the persona backward from those three outputs. Every field you include has to justify itself by changing one of them. If knowing a VP of Sales "enjoys weekend hiking" doesn't change your email, cut it.
The buying committee is the real unit of analysis
Single-persona thinking is where B2B teams quietly lose. One deal rarely has one buyer. It has a committee — usually four to seven people in anything above SMB — and each one is pulling in a different direction.
I split them into roles, not job titles, because titles vary wildly across companies:
The champion feels the pain daily and wants it solved. They'll carry your case internally if you make them look smart. Your job is to arm them with proof and ROI language they can forward up the chain.
The economic buyer signs off on spend. They don't care about features. They care about business outcomes, risk, and whether this makes or saves money fast enough to matter. Messaging that wins the champion often bores the economic buyer, and vice versa.
The blocker is usually IT, security, finance, or procurement. They can't say yes, but they can absolutely say no. They care about implementation risk, compliance, and whether this creates work for them. Ignore them and your "closed" deal stalls in legal for two months.
The end user lives with the tool after the deal closes. If they hate it, you churn. Their adoption concerns rarely surface in the sales cycle, which is exactly why they should show up in your persona work.
When you build personas for each of these, your messaging gets layered instead of flat. The champion gets the pain-and-vision story. The economic buyer gets the one-page business case. The blocker gets the security and rollout reassurance before they ask. That's not more work for the sake of it — that's how you keep deals from dying in the committee.
How to build data-backed personas
Forget the stock photos. Here's the process I run.
Start with the people who already bought. Pull your last ten or fifteen closed-won deals. For each, write down who the actual champion was, what role signed, what internal resistance showed up, and — this is the gold — what the buyer said in their own words about why they were looking. Call recordings are a goldmine here. The exact phrasing a VP used to describe their problem is often better copy than anything your marketing team will write.
Then study the losses. Lost deals tell you about objections and blockers more clearly than wins do. Where did deals stall? Which role killed them? What objection kept coming up? A persona that includes the real reasons people say no is ten times more useful than one that only imagines why they'd say yes.
Talk to your reps. The people on the phone every day know the personas intuitively even if they've never written them down. Ask them: when a deal is going well, what did the first good conversation sound like? What does this person always push back on? What makes them go quiet? Twenty minutes with two good AEs beats a week of guessing.
Interview a few actual buyers if you can. Even three or four conversations with recent customers surface patterns you'll never get from internal sources. Ask what they were doing the day they decided to look for a solution. That "trigger moment" is the single most valuable thing a persona can capture, because it tells you both what to say and when to catch them.
Pull it together and each persona should cover a handful of fields that earn their keep: the role and what they're measured on, the core pain in their own language, the trigger event that starts a search, their top two or three objections, where they actually spend attention, and what proof moves them. That's it. Six fields that change decisions beat twenty that don't.
Turning personas into messaging, channel, and targeting
This is where the work pays off. A finished persona should make three things obvious.
Messaging. The core pain in the buyer's own words becomes your opening line. The trigger event becomes your relevance hook. The top objection becomes the thing you preempt before they raise it. When a CFO persona tells you the real fear is "another tool my team won't use," your email leads with adoption and time-to-value, not features. Same product, completely different message depending on who's reading.
Channel. Where a persona spends attention decides where you show up. A VP of Engineering isn't living in their LinkedIn inbox — they might respond to a thoughtful technical point in a community or a referral from a peer. A VP of Sales checks LinkedIn and email constantly and responds to directness. Build your channel mix around where each persona actually is, not where it's easiest to send volume.
Targeting. Personas sharpen who you prioritize inside a target account. If your champion is almost always a director-level operator rather than a C-suite exec, your outbound targeting should reflect that and route the C-suite as a secondary thread, not the entry point. This is exactly the kind of logic we wire into the systems we build — persona rules feeding sequence selection and contact prioritization automatically, so reps aren't guessing per lead.
The test for whether your personas are real: hand them to a new SDR. If they can write a relevant first-touch email to the right person without asking you a single question, the persona works. If they can't, it's still a poster.
Keep them alive
Personas aren't a one-time project. Markets shift, buyers change what they care about, new objections appear. Review them every couple of quarters against fresh call data. The second you notice reps saying "nobody actually says that anymore," the persona has drifted and your messaging is drifting with it. Treat persona development as a running input to your revenue engine, not a deliverable you file away.
Frequently asked questions
How many buyer personas does a B2B company actually need?
Fewer than you think. Most B2B companies need three to five personas that map to the key roles in the buying committee — typically a champion, an economic buyer, and a technical or procurement blocker, plus the end user if adoption drives renewals. If you're building ten personas, you're probably slicing by demographic details that don't change your messaging. Build by role and decision-making influence, not by title variations.
What's the difference between a buyer persona and an ICP?
An ICP describes the ideal company — industry, size, revenue, tech stack, growth stage — and decides which accounts you target. A buyer persona describes an individual person inside that company — their role, goals, pains, and buying behavior — and decides what you say to them. You need both: ICP for list building and targeting, personas for messaging and sequencing. Using one without the other leaves half your go-to-market blind.
How do I build personas if I don't have much customer data yet?
Start with what you have. Even five closed deals and a few hours of call recordings reveal patterns. Interview your two best reps about who they talk to and what they hear. If you're truly early, interview three or four prospects in your target market directly — ask what triggered their search and what would make them hesitate. Build a draft, use it, and tighten it as real deal data comes in. An imperfect persona built from ten real conversations beats a polished one built from assumptions.
If your personas are collecting dust while your outbound stays generic, let's fix the whole chain — from ICP and targeting to persona-driven messaging and the automation that connects them. Book a Revenue Systems Audit and we'll pressure-test how your personas are actually shaping messaging and pipeline.