B2B-Specific Guide
B2B sales involve 5-9 stakeholders on average. Single-persona thinking fails because it ignores the influencers, blockers, and ratifiers. The buying-committee approach to B2B persona work — and how to message to each stakeholder.
According to Gartner research, the average B2B technology purchase involves between 5 and 9 stakeholders, often called a "buying committee" or "buying group." Selling to just one person — the decision-maker — ignores the people who can quietly veto the deal.
A standard B2B buying committee includes:
| Role | Concern | How to win them |
|---|---|---|
| Champion | Personal credibility from the project succeeding | Make their case for them. Provide internal-selling materials. |
| Economic buyer | ROI, budget impact, business case | Numbers, not features. Speak the language of business outcomes. |
| Technical buyer | Security, integrations, scalability, tech fit | Architecture docs, security pages, integration list. |
| End user | Daily workflow, learning curve, useful features | Demos focused on their specific use cases. |
| Procurement | Contract terms, vendor risk, savings | Standard contracts, security paperwork, references. |
| Legal/Compliance | Risk, contractual liability, regulatory fit | SOC 2, GDPR posture, MSA templates. |
| Influencer | Their domain expertise being respected | Substantive engagement, not generic pitch. |
| Ratifier | Confidence in the team's recommendation | Brand signals, case studies, peer validation. |
| Blocker | Status quo, internal politics, vendor preferences | Acknowledge concerns. Sometimes you can't win them. |
For each active deal, build a committee map. List every stakeholder identified, their role, their concerns, their current sentiment, and what you need from them. Salesforce and HubSpot both support contact roles on opportunities — use them.
The discipline of mapping forces sales to identify gaps. "We've talked to the Champion and the Economic Buyer but not the Technical Buyer" is a known risk. "We don't know if there's a Blocker" is a known unknown that needs resolution before the deal closes.
For B2B, you usually need a persona for each major committee role you sell into. A SaaS marketing tool might need:
Each persona gets the full treatment from our buyer persona guide: goals, pains, trigger events, decision criteria, information sources, internal language, objections.
Once you have personas for each role, every campaign and outbound sequence should be multi-threaded. The same opportunity gets different messaging to different stakeholders, even within the same account.
The VP of Marketing gets a message about marketing-influenced pipeline. The Marketing Ops Lead gets a message about data quality and integration. The CMO gets a message about board-meeting-ready reporting. Same product. Different jobs. Different language.
The B2B persona failure we see most often: companies build a single persona for "the buyer" and then wonder why deals stall in late stages. The deal stalled because someone on the committee — usually a Technical or Procurement stakeholder — wasn't sold. You can't sell someone you haven't messaged to.
Fix: every deal over $25K ACV should have a documented committee map with at least 3 named stakeholders. Anything less and you're flying blind.
Account-based marketing (ABM) is essentially committee-aware marketing at scale. ABM programs target accounts (the ICP) and orchestrate messaging across multiple stakeholders within each account. The mechanics: identify the committee structure for each target account, build coordinated outbound and paid campaigns that hit each role with the right message, measure pipeline impact at the account level rather than the lead level.