What you'll get
- 1 copy-ready blocks
- 1 table
- 5 min read
How to use it
- Step 1: Print the table and the title map, or keep both open while you research an account.
- Step 2: For one live deal, write a name against each role. Gaps are your to-do list.
- Step 3: Match your next touch to the role's column, not to your pitch.
- Step 4: Rebuild the map when anything changes hands; committees move.
Buying committee roles repeat from deal to deal. Whether the purchase is software, services or machinery, the same six jobs appear around the table: someone signs, someone wants it, someone tests it, someone will use it, someone guards the money and someone would rather it never happened. This sheet names each role, what it cares about, what to send it and what ignoring it costs.
The six roles
| Role | The job | Cares about | Send them | Ignored, it costs you |
|---|---|---|---|---|
| Decision maker | Signs, owns the budget line | The business case and the risk of acting or not | A one-page case their team wrote with you | A deal everyone likes that never gets signed |
| Champion | Owns the problem, wants it fixed | Looking right for backing you | Ammunition: proof, answers, a forwardable note | Nothing moves when they go quiet |
| Evaluator | Tests the claim, technical or commercial | Whether it works, integrates and is true | Specifics: documentation, references, a sandbox | A quiet no late in the deal |
| User | Lives with it daily | Whether it makes the week easier | A short demo of their task, not your tour | Resistance after signature, churn later |
| Finance and procurement | Guards money, terms and risk | Price against the alternative, contract, compliance | Clean paperwork early, answers without chasing | Weeks lost at the end, discounts you did not plan |
| Blocker | Prefers the status quo or a rival | The cost and risk of changing | Respect and specifics; meet them early | They speak once, late, in the room you are not in |
One person can hold two roles, and a role can be held by a group. The point of the sheet is not the labels; it is that each role needs its own reason to say yes, and a deck written for one of them persuades none of the others.
How do you spot the roles from job titles?
Titles mislead, but they are where research starts.
Head of the function with the problem usually the champion, sometimes the decision maker
VP or director the function reports to often the real decision maker
Architect, lead engineer, senior analyst evaluators
Manager of the team that would use it speaks for the users
Finance partner, procurement, legal, infosec finance and procurement, and where blockers sit
The person who chose the current tool the likeliest blocker, and worth meeting firstThe fuller mapping is in Sort 500 Job Titles into Buying-Committee Roles.
How many of them do you need?
Enough that the deal survives one person going quiet. On the accounts we work, coverage means at least three roles named before outreach starts, and an account is only moving when two or more people are in conversation. The Buying Committee Mapper builds the map from a role list; the Buying Committee Map is the printable version. The term itself is in the glossary.
Worked example (illustrative, not a real company)
Quaywise sells warehouse software and maps Northfield Logistics. Dana Whitfield, operations director, owns the dock scheduling problem: champion. Her VP holds the budget line: decision maker. Marcus Lee in IT will test the integration: evaluator. Two depot supervisors speak for the users. Procurement joins at contract. The incumbent vendor's internal sponsor is the blocker, so Quaywise asks for twenty minutes with them in week two rather than week ten. All names and details are invented.
Five mistakes to avoid
- Reading the org chart as the committee. The committee is who influences this purchase, not who reports to whom.
- Selling only to the champion. They already agree. Spend the next touch on someone who does not.
- Meeting the blocker last. Late objections are expensive; early ones are research.
- Sending everyone the same deck. Six roles, six different questions. One deck answers at most one of them.
- Stopping at the first yes. One enthusiastic contact is a thread, not a committee. Keep mapping.
Why this works on named accounts
Common questions
What are the roles in a B2B buying committee?
Six repeat across deals: the decision maker who signs, the champion who owns the problem, the evaluators who test the claim, the users who live with it, finance and procurement who guard money and terms, and the blocker who prefers the status quo. One person can hold more than one.
How many people are in a typical buying committee?
It grows with deal size and risk. A small tool might be two people; an enterprise platform pulls in the full six roles, some held by groups. Rather than trust an average, map the account in front of you and count.
Who in the buying committee matters most?
The one you have not met. Deals stall less because the champion was weak and more because an evaluator, a finance partner or a blocker was never spoken to until they spoke up.
More from the Academy
Buying Committee Map
For sellers working a large account through a single contact.
You leave with nine roles to look for, a map you can paste into a spreadsheet, a brief for each person and a coverage check that shows where the account is exposed.
Sort 500 Job Titles into Buying Committee Roles
For sales heads and account owners with a contact export full of job titles.
You leave with a role-sorting prompt, a six-role key and a gap list by account.
Multithreading Email Templates for a Second Stakeholder
For sellers with one contact in a large account and nobody else.
You leave with a who-next card, 6 email templates, a thread log and 2 emails written out.
Buying Committee Mapper
Map the people behind a decision by role, stance and influence, and see who to approach next. Runs in your browser.
Want this in your inbox?
Optional. We use your email only to send you this, nothing else.