A B2B Persona Is a Committee. Build It Like One.

Consumer personas describe a person. B2B personas that describe a person miss the deal, because the user, the approver, and the blocker are three different people with three different fears.

The classic B2B persona error is a single portrait, Dana, operations manager, 38, wants efficiency. Dana exists. Dana also cannot sign. The person who signs fears budget exposure, the person who implements fears a migration weekend, the person in security fears the questionnaire, and Dana fears being blamed for choosing the tool her team routes around by Friday. A persona set that does not separate the user, the economic buyer, the implementer, and the blocker will produce messaging that answers one fear and triggers another, which is why so much B2B content reads as enthusiastic and converts as if it were vague. Build the committee, four portraits with a stated relationship, what each one can kill, and what proof each one accepts. It is more work than one portrait. It is also the first version that survives contact with an actual deal review.

Each seat gets a veto, a budget line, and a proof standard

Write the four seats plainly. User: daily pain, proof standard is a trial that respects their workflow. Economic buyer: total cost against a budget line they defend internally, proof standard is a reference customer of similar size and a contract without surprises. Implementer: integration surface and support quality, proof standard is documentation they can read before the sales call ends. Blocker: security, legal, or procurement, proof standard is the completed questionnaire and the data processing terms. A persona that cannot state its seat's proof standard is a horoscope, and content built from it will be horoscope grade, warm, agreeable, and useless in the room where the deal is decided.

Map the sequence while you are at it. The blocker rarely appears first, which tempts teams to ignore the seat until the eleventh hour, when a security review adds six weeks to a deal everyone thought was closing. The committee persona should note when each seat typically enters and what asset needs to exist before they arrive. The security one pager written during a stalled deal is always written in a worse mood than the one written in advance.

Related reading on this site: PersonaRail and How Often Should You Refresh Persona Enrichment? cover the neighbouring problems in more depth.

Where committee personas come from

Not from a workshop's imagination. From deal archaeology: the last twenty won and lost deals, who appeared in the thread, who asked which question, where the deal stalled, and the exact phrase in the lost deal email where it died. Lost deals teach more, because the committee's real vetoes only become visible when they are exercised. Interview the implementers and blockers from lost deals if they will talk; they usually will, because nobody ever asks them, and their account of why the tool died is routinely different from the champion's.

Refresh on the same evidence. A new compliance requirement, a new integration your buyers standardized on, a pricing model shift in your category, each one rewrites one seat's fears first. Update that seat's portrait and leave the others alone. Committee personas maintained seat by seat stay current. Full deck rewrites happen annually and describe last year's committee with this year's confidence.

One page per seat, one page for the room

Keep each seat to a page: role, the outcome they are graded on, their top three objections in their own vocabulary, their proof standard, and the message that has actually moved them, quoted from a real thread where privacy allows. Then one page for the room: the order seats engage, the handoffs (the user sells the buyer, the buyer tests the implementer), and the two moments deals in your category usually die. Five pages total. A team can hold five pages in their heads in a pipeline review, which is the point of the exercise.

If your current program has one persona per product and none per committee, do not rebuild everything at once. Take the product with the longest sales cycle, where committee dynamics cost you most, and build its four seats from its last twenty deals. The exercise will either prove itself in that pipeline or it will not, and either answer is cheaper than a company wide persona relaunch built on faith.

Frequently asked questions

How many personas does a B2B product need?

At minimum, one per seat in the buying committee: the user, the economic buyer, the implementer, and the likely blocker in security, legal, or procurement. A single composite persona hides the conflicting fears that actually decide deals.

What should a B2B persona include?

The role and what the person is graded on, their main objections in their own words, the proof they accept such as references, documentation, or a completed security questionnaire, and what they have the power to block.

Where should B2B persona research come from?

From recent won and lost deals: email threads, stall points, and interviews with the people involved, including implementers and blockers from lost deals. Workshop invention without deal evidence produces portraits that do not match real committees.

How often should committee personas be updated?

Seat by seat, whenever the evidence changes: a new compliance demand, a shift in the integrations buyers expect, or a pricing change in the category. Annual full rewrites tend to lag the changes that matter.