"Marketing Mary, 42, CMO at a mid-sized company, values data, hates silos." I've sat through countless workshops where a persona slide like this gets presented with total conviction. And every time I think the same thing: who actually made the decision to buy your product last time? Was it really Mary, alone? The answer is always no.
B2B personas are an inheritance from B2C marketing, where one person makes one decision in one context. That makes sense when you're optimizing a message for "Sarah, 34, busy mom, price-sensitive." It doesn't make sense in B2B, where a single purchase typically involves a buying committee of 6-10 people—each with their own mandate, their own risk, and their own answer to the question "what happens to my career if this goes wrong?"
The Problem Isn't That Personas Are Wrong. It's That They're Incomplete.
A persona typically captures one role well—often the one marketing talks to most: the user or the technical evaluator. It rarely captures the economic decision-maker who has to defend the investment internally. It almost never captures procurement or legal, who can kill a deal at the finish line for reasons that have nothing to do with the product. And it doesn't capture the dynamics between them at all—who needs to convince whom, and in what order.
The result is content that speaks persuasively to one person in the room and is invisible to the five others who actually have to say yes.
The Framework: Map the Roles, Not the People
Instead of one composite persona, I use a role-based mapping with six recurring functions in a B2B buying committee. Not all are present in every deal, but most enterprise purchases involve a variant of all six:
The economic decision-maker — owns the budget and carries the ultimate risk. Motivated by predictability and defensibility to the board. Fears having to explain a failed project a year later.
The champion/internal advocate — the person who found you, and who now has to sell the solution internally. Motivated by looking like the one who solved a real problem. Needs ammunition, not just product info—cases, ROI math, references they can cite onward.
The technical evaluator — assesses whether the solution actually works, integrates, and scales. Motivated by technical soundness and by not getting blamed if something breaks later. Skeptical of marketing language, drawn to documentation and case studies with concrete numbers.
The end user — has to live with the tool daily. Motivated by reduced friction, not added friction. Often the most honest voice in the room, but rarely the one with veto power.
Procurement/legal/compliance — can stop a deal for reasons that have nothing to do with product value: contract terms, data handling, vendor risk. Motivated by minimizing organizational risk, not functionality.
The skeptic/blocker — present in almost every committee. Often motivated by status-quo bias or a bad experience with a previous vendor. Ignore this role and you often lose the deal late in the process for reasons that were never surfaced early.
How to Use the Mapping in Practice
For each role: identify their primary fear (not desire—fear drives B2B decisions more strongly than aspiration), their preferred form of proof (case, numbers, reference, technical documentation), and what content actually reaches them in the channel they use. A CFO doesn't read your blog. A technical evaluator rarely sees LinkedIn ads. Match channel and format to the role, not the other way around.
Then build a "committee content map"—a simple spreadsheet showing what content exists for each role, and where the gaps are. Most B2B marketing teams discover that 80% of their content speaks to one or two roles, while the rest of the committee is left with nothing that addresses their specific concern directly.
Repurposing for LinkedIn
This framework also makes strong short-form content: one LinkedIn post per role, naming their specific fear and how you address it, lands far more precisely than a generic "here's how we help companies" post. It also signals to prospective customers that you understand how their organization actually makes decisions—which is itself a form of sales argument.
Personas were never wrong as a concept. They were just built for a market where one person makes the decision. In B2B, the decision is a negotiated outcome between multiple people with conflicting interests. Design your content and your sales process for that reality, and you'll see shorter sales cycles and fewer deals that die at the last minute for reasons no one saw coming.