B2B Buying Committee Mapping: Six Decision Roles, a Worked Enterprise Example and a Role-Not-Title Worksheet

Buying committee mapping is the work of naming, for one account and one purchase, the people who hold six decision roles: the economic buyer who can say yes alone, the champion who carries the case, the operator who will live with the result, the technical evaluator who recommends, the security, legal and procurement gates who can each say no, and the blocker who wants a different outcome. Titles are clues to those seats, not the seats themselves. This guide gives a test for assigning people to seats, a worked enterprise example and a worksheet you can copy.

Why a Title List Is Not a Map

A list of titles answers "who works there". A map answers "who decides what, and what each of them needs before they will let the purchase through". The two diverge for a plain reason: the same title holds a different seat in different companies and in different purchases at the same company. A chief information officer is the economic buyer for an infrastructure contract, a technical evaluator for a sales-data subscription and a gate for a marketing tool that touches customer records. A map built from titles alone assigns that person one seat, and is wrong for two of the three purchases.

The size of the group makes the error expensive. Forrester's Buyers' Journey Survey, 2025, as summarised on the firm's blog in February 2026, found that "73% of purchases involve three or more departments, with an average of 13 people inside the buyer's organization and nine from outside involved in making a purchase decision." The same post notes that "GenAI is now a first-stop research tool for many buyers" and that external experts, peers and communities shape buyer thinking "often before a provider is even on the radar". Thirteen people across three or more departments is not a contact; it is a structure, and the seller who has not drawn it is negotiating with a room they cannot see.

Forrester's own role vocabulary for the group, from an earlier post on the 2024 survey, is "decision-maker, champion, influencer, ratifier, and user". The six seats below are a seller's working version of the same idea, arranged by what each person can do to the deal rather than by what they are called.

The Yes-No-Live Test

Three questions assign any person to a seat, and they are asked about the person's power over this purchase, not about their rank.

Can this person say yes alone? If the purchase proceeds on their signature, or on their instruction to someone who signs for them, they are the economic buyer. There is one per purchase. A person who "would need to take it to" someone else is not it, however senior.

Can this person say no alone? If their refusal stops the purchase without anyone overruling them, they hold a gate. Security, legal and procurement are the recurring gates, and each has its own standard of proof. A blocker also answers yes to this question, with a difference: a gate wants a condition met, a blocker wants a different outcome.

Will this person live with the result? If the product changes their working week, they are an operator. An operator's veto does not arrive in a meeting; it arrives after signature, as non-adoption, which is why a map that skips them produces a signed contract and a failed renewal.

Two seats answer no to all three questions and still decide the deal. The champion cannot say yes, cannot say no and will not run the product, but carries your case into rooms you are not in, and the deal moves at the champion's pace. The technical evaluator cannot sign or veto in form but produces the recommendation that the economic buyer and the gates rely on; a negative evaluation is a veto in practice.

Run the test on every name you have. Anyone who gets three noes and carries no case is not on the committee, whatever the org chart says.

The Six-Seat Decision Map

Reading the map as text: two seats, the economic buyer and the operator, are defined by what happens to them if the purchase goes ahead, and they are found by asking about budget and about daily work. Three seats, the evaluator and the gates, are defined by a standard the product must meet, and they are found by asking what review exists. The champion and the blocker are defined by what they want, which no record states outright, so both are inferred from prior attempts and from incumbent relationships and then confirmed in conversation.

Seat by Seat: What Each Role Decides and What Convinces It

The economic buyer. This seat owns a budget line and a number that the purchase is supposed to move. The holder is identified by the yes-alone question and verified by asking two different people the same budget question; when the answers agree, the seat is named. What convinces this seat is a case written in its own measures, with the cost of inaction stated as plainly as the cost of the product. What loses it is a feature tour and a return-on-investment figure the seller cannot show the working for. At executive level the holder appears in public records: an annual report lists the executive officers, and a Form 8-K Item 5.02 marks a change in them, which is why a new executive in the buying function is a reason to re-map rather than to resend the old deck; the new executive hire guide covers that window.

The champion. A champion is made during the deal, not found in a database, but the raw material is visible beforehand: a person who has spoken or written about the problem, who sponsored a previous attempt, or whose role was created to own the outcome. The seat decides whether the case is argued in your absence, and the test of a real champion is behaviour, not warmth: they introduce you to other seats, they tell you what was said in the meeting you missed, and they ask for material they can forward. How to find and enable a champion covers the enablement side; for mapping purposes the rule is that a champion who has not yet opened a second seat for you is a candidate, not a champion.

The operator. The operator will run the product after signature: the administrator, the team lead whose queue it changes, the analyst who will own the data flows. The seat is easy to skip because it carries no signature, and it is the seat that decides whether a signed deal renews. The holder is found through postings that name the tools a team runs and through the discovery question "whose week does this change?", and is convinced by a product that demonstrates itself in their own workflow and by a migration plan that does not land on them unaided.

The technical evaluator. The evaluator writes or applies the requirements and tests the integration. The seat decides whether the product passes, and it buys defensibility: an evaluator who approves a product that later fails carries the blame, so the standard of proof is documentation, a sandbox and straight answers about limits. Architecture and platform titles point to the seat; so do engineering posts about the stack. A failed evaluation stands until it is re-run, which is why the seat is worked early and in writing.

The three gates. Security, legal and procurement are grouped because they share a property: each can say no alone, and each wants a condition met rather than a different outcome. They differ in what counts as evidence. Security wants proof of controls, in the form of a questionnaire answered against the account's own standard, an audit report, and a data-flow description. Legal wants the terms and the data handling: the contract, the data processing agreement, the sub-processor list and the lawful basis for any personal data in the product. Procurement wants the process followed: supplier registration, a price benchmark, references and a clean record. The processes are public even when the people are not. Trust pages, published DPA templates and supplier-registration portals describe what each gate will ask, which is the raw material of the worksheet below. The people are a different matter. The annual-report count later on this page shows that legal and security leaders are named in thousands of filings and procurement leaders in a handful, which is why the procurement gate is found through postings, supplier portals and the discovery question rather than through the executive list. When procurement is the buyer rather than the gate, as it is for sourcing and supplier-risk tools, the seat changes; the buyer-or-gate map for procurement leaders sorts those cases.

The blocker. The blocker wants a different outcome: the incumbent kept, a rival project funded, the status quo preserved, or the decision made in a different forum. The seat is found by asking who owns the thing you replace and who sponsored the last attempt, and it is confirmed by behaviour: meetings that lose attendees, requirements that change after you meet them, a competing evaluation that appears late. Blockers are not handled by persuasion aimed at them. They are handled by the map: by making sure the economic buyer has heard the blocker's alternative from you before hearing it from them, by giving the blocker a role in the outcome when one exists, and by not leaving the deal single-threaded through a seat the blocker can reach. Where that thread is thin, the fix is multithreading.

When the Committee Is a Formal Body

In private companies the committee is a de facto group that no one calls a committee. In public procurement it is written down, and the written version is a useful check on the seats above. The Federal Acquisition Regulation states that "Agency heads are responsible for source selection. The contracting officer is designated as the source selection authority, unless the agency head appoints another individual for a particular acquisition or group of acquisitions." The source selection authority shall "Establish an evaluation team, tailored for the particular acquisition, that includes appropriate contracting, legal, logistics, technical, and other expertise to ensure a comprehensive evaluation of offers", and shall "Select the source or sources whose proposal is the best value to the Government". The evaluation itself is documented: "The relative strengths, deficiencies, significant weaknesses, and risks supporting proposal evaluation shall be documented in the contract file", with cost or price, past performance and technical evaluation treated as separate records.

Read against the six seats, the regulation names one economic buyer (the source selection authority), a technical evaluator (the technical evaluation), a legal gate and a procurement gate (contracting and legal expertise on the team), and a documented commercial standard ("best value"). It has no champion and no blocker because it is designed not to. That is the difference between a formal committee and the one you are mapping: in a company, the two seats the regulation excludes are the ones that decide the pace. For public buyers, the RFP buying signals guide covers what the published process reveals before, during and after an open bid.

A Worked Enterprise Example

Mardale Freight Systems is an invented company; the people, titles and events below are made up to show the method and describe no real organisation.

Mardale is a 9,000-employee logistics group with a 300-seat sales organisation across four regions. The purchase is a revenue-data platform that would replace a contact-data subscription and feed verified accounts and contacts into the CRM. The seller's first map, built from public records before any conversation, looked like this.

Two discovery conversations changed four rows. The RevOps director confirmed that the budget line sits with the chief revenue officer but that spend of this size is approved by the chief financial officer, which split the economic buyer seat into an owner (CRO) and a ratifier (CFO) and added a second case to write. The vice president of sales development turned out to have sponsored the incumbent subscription two years earlier; she was not a champion but a candidate blocker, protective of the earlier decision, and the real champion was a regional sales director who had built a spreadsheet process to work around the incumbent's data. The procurement gate acquired a name when the RevOps director described the vendor-onboarding sequence and the category manager who runs it. The security and legal gates stayed as processes with no named person, which is a normal state before the evaluation starts and an abnormal one after it.

The map after two calls had six seats, eight people, two of them guessed, and one explicit risk: the sales development leader could reach the CRO without the seller in the room. The response was not a pitch to her but a path around the dependency: the regional director opened a conversation with the CRO, the CFO's case was written in the cost-per-working-lead terms finance would check, and the incumbent's renewal date, visible in the case study's publication timing, set the clock. None of that was available from the title list.

The Role-Not-Title Mapping Worksheet

Buying committee mapping needs a record, not a memory. Copy the columns below into a sheet or a CRM object, one row per seat, and add rows when a seat splits (an owner and a ratifier for the economic buyer; three rows for the three gates).

A map is complete enough to forecast on when the economic buyer and the operator are Named or Verified, the evaluator is Named, each gate has at least a named process, the blocker seat has been asked about even if the answer was "no one", and no row is a guess older than a quarter. A map that fails any of those is a research list, and the deal built on it is a hope. The discovery question that fills more rows than any other is still "who else will want a say in this?", asked of every seat; the discovery call questions guide places it among the four territories a call has to cover, and the decision-maker finding guide covers where the economic buyer sits as company size and purchase size change.

Where the Gate Holders Are Named: An Original Count

The table records exact-phrase counts from the SEC's EDGAR full-text search for annual reports on Form 10-K filed between October 1, 2025 and October 1, 2026, retrieved October 2, 2026. The unit is documents, and a phrase in a filing proves only that the words appear, not that the role sits on any committee.

Read down the column: the legal and security gates have named leaders in the public record, with the general counsel and the chief information security officer appearing in thousands of annual reports, and the processes those gates run appear as "third-party risk management" and "vendor risk management". The procurement gate is nearly invisible at that level, with twenty filings naming a chief procurement officer and two a head of procurement, which matches the worked example: the procurement holder is found through the supplier portal, the postings and the discovery question, not the filing. The economic buyer for a sales purchase is also thinly recorded, with "chief revenue officer" in 199 documents, so the yes-alone question has to be asked rather than looked up at accounts where the revenue leader is not an executive officer.

Keeping the Map Current

Seat data decays faster than contact data because it changes without anyone updating a profile. A reorganisation moves the budget line; a new executive in the function re-opens every seat under them; a policy change at the account hands a gate to a different team; a champion promoted out of the function leaves a seat that looks filled and is not. Three habits keep the map honest. Re-run the Yes-No-Live Test on the economic buyer at every stage change, with the budget question asked of a second person. Re-date every row at each two-way contact and let the quarter rule demote untouched rows to Guessed. And re-read the map when a public record changes: an 8-K Item 5.02, a new posting for a role on the map, an incumbent's case study appearing or disappearing. Forrester's reminder that "the buying network doesn't end at purchase" applies here: the renewal has a committee too, and it is not the same one that signed.

Where Lead Seeker Fits

Lead Seeker is built for the first column of the worksheet and for keeping it dated. It watches hiring, funding and financial events, tech stack changes, public statements, product and GTM moves and operational stress at the accounts you describe (here is how to read Trigger Signals), returns the people in the seats re-verified the moment you run the search, and assembles a record in which every claim links to its public source where available, with the freshness date stamped on it (here is how the prospect dossier works). You can see how Lead Seeker works end-to-end, or claim 5 free verified leads for one account whose committee you are mapping now; the prospect dossier template shows where the seat assignments and their sources are recorded, and the lead intelligence library holds the method guides this page links to. Teams that want the account research and signal programme run for them can speak to Percepture's B2B intent data service, and teams that want to know how their company appears when the thirteen people inside the account research it through AI answers can measure that with Prime AI Visibility. Neither replaces the map; both depend on it.

Frequently Asked Questions

What is buying committee mapping?

Buying committee mapping is the practice of identifying, for one account and one purchase, who holds each decision role and what each of them needs before the purchase can proceed: the economic buyer who can say yes alone, the champion who carries the case, the operator who will live with the result, the technical evaluator who recommends, the security, legal and procurement gates who can each say no, and any blocker who wants a different outcome. The output is a dated table with a status for every seat, not a list of titles.

How many people are on a B2B buying committee?

Forrester's Buyers' Journey Survey, 2025, as reported on the firm's blog, found "73% of purchases involve three or more departments, with an average of 13 people inside the buyer's organization and nine from outside involved in making a purchase decision." The count for any one purchase depends on its size, its contract length and how many teams the product touches, so treat the average as a reason to expect several seats to split rather than as a target for your map.

What is the difference between an economic buyer and a champion?

The economic buyer can approve the spend alone; the champion cannot approve or veto anything but argues the case when the seller is absent. A champion who is also the budget owner holds both seats, and the map should say so, because a deal that depends on one person for both the argument and the signature is single-threaded through that person. In the worked example above the apparent champion turned out to be a candidate blocker and the real champion sat two levels down.

How do you identify the economic buyer at an account?

Ask the yes-alone question of two different people: whose budget does this come from, and who approves spend at this size? When the answers agree, the seat is Verified. Public records help at executive level, where an annual report lists the officers and a Form 8-K Item 5.02 marks a change, but the EDGAR count on this page found "chief revenue officer" in 199 annual reports over twelve months, so for a sales purchase the question has to be asked rather than looked up. A new executive in the function re-opens the seat.

What is a blocker in a buying committee and how do you handle one?

A blocker is a committee member who wants a different outcome: the incumbent kept, a rival project funded or the decision made elsewhere. A gate wants a condition met; a blocker wants you to lose. Find the seat by asking who owns what you replace and who sponsored the last attempt, confirm it by behaviour such as late requirements changes or a competing evaluation, and handle it through the map rather than through persuasion: make sure the economic buyer hears the alternative from you first, offer the blocker a role in the outcome where one exists, and remove any single thread the blocker can reach.

Is a buying committee a formal body?

In private companies it is a de facto group with no charter. In public procurement it is formal: the Federal Acquisition Regulation makes the contracting officer the source selection authority by default and requires an evaluation team "that includes appropriate contracting, legal, logistics, technical, and other expertise", with the evaluation documented in the contract file. The formal version names an economic buyer, an evaluator and the legal and procurement gates, and by design has no champion and no blocker, which is why mapping a company committee is harder than reading a solicitation.

Sources

• Forrester, Three Realities About B2B Buying Networks (Katie Fabiszak, February 23, 2026; Buyers' Journey Survey, 2025: "73% of purchases involve three or more departments, with an average of 13 people inside the buyer's organization and nine from outside"): https://www.forrester.com/blogs/three-realities-about-b2b-buying-networks/ (read October 2, 2026)
• Forrester, The Verdict Is In: It's Buying Groups For The Win (Buyers' Journey Survey, 2024: "on average, 13 people are involved in making a purchasing decision"; role vocabulary "decision-maker, champion, influencer, ratifier, and user"): https://www.forrester.com/blogs/the-verdict-is-in-its-buying-groups-for-the-win/ (read October 2, 2026)
• eCFR, 48 CFR 15.303, Responsibilities (source selection authority; evaluation team with contracting, legal, logistics, technical and other expertise; "best value"): https://www.ecfr.gov/current/title-48/chapter-1/subchapter-C/part-15/subpart-15.3/section-15.303 (read October 2, 2026)
• eCFR, 48 CFR 15.305, Proposal evaluation (strengths, deficiencies, significant weaknesses and risks documented in the contract file; cost or price, past performance and technical evaluation): https://www.ecfr.gov/current/title-48/chapter-1/subchapter-C/part-15/subpart-15.3/section-15.305 (read October 2, 2026)
• U.S. Securities and Exchange Commission, EDGAR Full-Text Search (exact-phrase document counts, Form 10-K, October 1, 2025 to October 1, 2026, retrieved October 2, 2026): https://www.sec.gov/edgar/search/
• Percepture, B2B Intent Data service: https://percepture.com/services/b2b-intent-data/ (read October 2, 2026)
• Prime AI Visibility: https://primeaivisibility.com/ (read October 2, 2026)

About the Author

Bob Generale is President of Percepture. He works across SEO, AI search, digital PR, sales intelligence and AI-powered revenue systems, with a focus on connecting visibility, buyer intent and sales action.

Next Steps

Start buying committee mapping on the three accounts you expect to forecast this quarter: draw the Six-Seat Decision Map from public records alone and mark every row Guessed. Then run the Yes-No-Live Test on the next call with each account and watch how many rows change. When a map has its economic buyer and operator Named, claim 5 free verified leads to see what a dated, source-linked record for the people in those seats looks like before the evaluation starts.