B2B Personas When Six People Share One Purchase
B2B purchases are made by committees, not individuals, so personas must model the whole cast: the user who feels the pain, the champion who carries the project, the economic buyer who signs, and the gatekeepers in IT and security. Selling to the committee means giving each persona its own evidence, timeline, and definition of risk.
The committee, named
Every B2B deal has a cast, whether you map it or not. The end user lives with the problem daily and evaluates on usability. The champion, often a manager, turns that pain into a business case and spends political capital. The economic buyer signs and cares about cost, risk, and timing against other priorities. IT, security, legal, and procurement can each say no and are evaluated on the disasters they prevented.
For more on this, see this related guide and our earlier explainer on the same theme.
Most marketing personas model only the hero, the champion or the user, and then wonder why deals stall in review. A deal does not close when one person is convinced; it closes when every member of the committee can defend saying yes. Personas that stop at the champion leave the actual decision makers unaddressed.
Each persona wants different evidence
The same product needs four different proof packs. The user wants a trial and honest workflow documentation. The champion wants ROI math and a reference customer in the same role. The economic buyer wants total cost over three years, implementation risk, and what happens if the project fails. Security wants architecture diagrams, certifications, and data handling answers in their own language.
This is why generic case studies underperform: they average the evidence into something nobody finds compelling. Build collateral per persona, not per product. A one page security FAQ and a champion's ROI worksheet do more for a stalled deal than another webinar, because they answer the specific person whose objection is holding everything up.
Sequencing: who to reach and in what order
Real deals rarely start at the top. They start with a user or a low level champion, then climb. Map the typical ascent path in your segment: which personas the champion must recruit, in what order, and what each recruitment conversation needs. Content should arm the champion for the conversation with finance, not just persuade the champion.
Readers also found this companion piece from our archive useful.
Time the committee work early. Deals die when security review starts the week before signature, because the gap between the champion's promise and the gatekeepers' requirements finally becomes visible. A vendor that hands the champion a security packet in week two is not slowing the deal; they are preventing the week twelve ambush that kills it.
Marketing to a committee with limited personas
You do not need twelve personas to cover a committee; you need role based messaging tracks. Three or four archetypes, user, champion, economic buyer, gatekeeper, map well onto most deals and keep content production sane. The archetypes should describe the role's incentives and fears, because those persist even as job titles change.
Measure committee coverage in your pipeline. For stalled deals, check which personas you have engaged: deals with only the champion engaged stall predictably. That metric turns personas from a marketing artefact into a sales tool, and it tells the team exactly which conversation to start next.
Frequently asked questions
Why do B2B deals stall after the champion is convinced?
Because committees decide, not champions. Unaddressed gatekeepers in security, legal, or finance surface objections late, and the champion cannot answer evidence they were never given. Engaging the whole committee early prevents the late ambush.
How many B2B personas do we need?
Usually three or four role archetypes: the user, the champion, the economic buyer, and the gatekeeper. Role based archetypes stay useful as titles change, and they keep content production manageable compared to modeling every title.
What evidence does each persona need?
Users want trials and workflow honesty. Champions want ROI math and peer references. Economic buyers want three year cost, implementation risk, and failure scenarios. Security and legal want architecture, certifications, and data handling documentation in their own terms.
When should security review start?
As early as possible. Handing the champion a security packet in week two prevents the week twelve ambush where gatekeepers discover the gap between promised and required. Early gatekeeper engagement shortens cycles rather than lengthening them.