Start with recent won and lost deals. Identify who felt the problem, who could approve spend, who checked technical risk and who had to operate the solution. Then map the question each person needed answered. Build content from those questions rather than assuming one persona makes the whole decision.
Reconstruct a purchase that actually happened
Choose five recent deals, including wins and losses. For each, list everyone who joined a meeting, received material, raised an objection or approved a step. The person who first asked for a demo may not control budget. The budget owner may never use the product. A technical reviewer may be able to stop a purchase without being able to start one. These differences matter when you decide what a campaign should explain.
Do not begin with a generic “six-person committee” diagram. Some startups sell to one founder; others must satisfy procurement, security and operations. The no-decision guide helps when consensus never forms.
Give each participant a decision to make
For each actual person, record their job in the purchase: recognise the problem, assess the workflow, defend the economics, approve security, manage implementation or sign the contract. Then note the question they asked and the evidence that moved them forward. An economic buyer may need a business case; a daily user may need a workflow demonstration; a technical reviewer may need approved integration detail.
The same person can hold several roles in a small company. Avoid creating separate pages just because two job titles exist. Build content only where the information need is distinct and repeated. The champion one-pager can help one internal advocate carry a concise argument across functions.
Look for the absent person
Stalled deals often reveal an approval that was discovered too late. If finance appears only after pricing is agreed, the buyer may reopen the economic case. If security appears after a pilot, technical requirements may invalidate the plan. Ask sellers at what stage each stakeholder usually enters and whether the champion can invite them earlier. Marketing can prepare the right explanation for that moment.
For a hypothetical data platform, the user may value speed, the finance lead may need payback assumptions and the data owner may need governance detail. A single feature sheet will not answer all three, but three disconnected campaigns can confuse them. Keep one consistent core promise and layer proof for each decision.
Use the map to prioritise content
List the repeated unanswered questions across the sample. Rank them by how often they delay a deal and whether your company can provide credible evidence. Build the highest-leverage asset first, such as an implementation overview, business-case worksheet or relevant case study. Ask sales to use it in live deals and record what changes.
Apply this to your business
Draw five rows, one per recent deal, and columns for sponsor, user, budget owner, technical reviewer and blocker. Fill only the roles you can verify. The missing or late-entering role is your next research question, not a reason to invent another persona.
Frequently asked questions
How many people are in a B2B buying committee?
It varies by deal, company and risk. Map the actual participants in your target accounts instead of applying a universal number.
Should we create separate content for every job title?
Usually not. Start with the distinct decisions and questions. Several roles may share the same concern, while one person may play more than one role.
Strong interest from one person but no final decision?
Bring recent stalled deals and the people involved. Mohit can help identify which buyer question or internal approval your marketing is failing to support.
Talk through the problem ↗See how we could work together
