Glossary · Targeting and signals

What is a buying committee?

The short answer

A buying committee is the group of people at one company who take part in a B2B purchase: the decision maker who signs, the champions who push for it, the people who will use it, and the gatekeepers in finance, security, legal and procurement who can slow it down or stop it.

Updated
Read
4 min
Written by
Antoine Blitz
On this page8 sections
  1. Real data
  2. Who is on a B2B buying committee?
  3. How do you map a buying committee from job titles?
  4. Decision maker, champion and gatekeeper: what is the difference?
  5. Why does a B2B deal need more than one contact?
  6. How do you find the people on a buying committee?
  7. Related terms
  8. Questions people ask

Real data

One buying committee, mapped by job title

Calendly, and a hypothetical purchase: a tool for its sales team. One call searched the current employees of the company in seven tiers, one role of the committee per tier. Titles and counts only, no names.

Returned by the BlitzAPI API on

POST/v2/enrichment/company

The company

Company
Calendly
Industry
Software Development
Size band
501–1,000 employees
Employees on LinkedIn
796
Headquarters
Atlanta, Georgia, United States
POST/v2/search/waterfall-icp-keyword

The committee for a sales tool, one tier per role

Tier 1 · Likely signer: sales leadership
1 profile in sales leadership
Tier 2 · Likely champion: RevOps, sales development
1 profile in revenue operations
Tier 3 · Approves the spend: finance
1 profile in finance leadership
Tier 4 · Reviews the vendor: security
4 profiles in security and compliance
Tier 5 · Reviews the contract: legal
1 profile in legal
Tier 6 · Negotiates the terms: procurement
1 profile in procurement
Tier 7 · Uses the tool: sellers
8 profiles with account executive titles

17 profiles in one call. Each profile is counted once, in the first tier whose titles it matched. The counts are profiles whose current title matched on that day, not the size of each team.

Who is on a B2B buying committee?

A B2B buying committee forms because any purchase with a real budget or a real risk involves more than one person. The roles repeat from deal to deal, even when the titles do not:

Role What they do in the purchase Typical titles when a company buys a sales tool
Decision maker Owns the budget and signs CRO, VP of Sales, Head of Sales
Champion Wants the change, pushes for it inside, often runs the evaluation RevOps manager, sales development lead
Users Work with the product every day; their adoption decides the renewal Account executives, SDRs
Influencers Shape the choice without owning it Sales enablement, IT, a peer who used the tool before
Gatekeepers Control the spend, the risk and the contract, and can stop the deal Finance, security, legal, procurement

The decision-makers guide shows how to find the person who signs. The rest of the committee decides whether that person ever says yes. A small purchase paid by card may involve two of these roles; a platform rolled out across the company can involve all five, with several people in each.

How do you map a buying committee from job titles?

To map a buying committee from job titles, write one search tier per role, in the order you want to reach them, and run it on one account. The example above does it at Calendly for a hypothetical purchase, a tool for the sales team, and finds 17 profiles across seven tiers. Three lessons from that run:

  • Titles vary more than roles. A first pass with exact titles, such as “VP of Sales”, found no one at the signer tier. Keyword phrases found a sales leader under a title the exact list did not contain. List the variants, and exclude the words you do not want, such as “Operations” or “Regional”.
  • The control side is bigger than it looks. At Calendly, security returned four profiles, more than finance, legal and procurement together. In a software purchase, security usually reviews the vendor before the contract is signed.
  • A title is a hypothesis. It tells you who could play a role, not who plays it in this deal. The champion is whoever pushes for the purchase, and only conversations reveal that.

Keep the committee tied to its account: the same titles mean different roles in a company of 40 people and in a company of 4,000, which is why the ideal customer profile comes first.

Decision maker, champion and gatekeeper: what is the difference?

The decision maker can say yes alone. The champion cannot, but wants that yes and works for it: they forward your material, book the next meeting and argue your case in rooms you never enter. Gatekeepers rarely start a purchase. They protect the company from a bad one, so they check cost, risk and terms, and they can say no.

Which is which?

Six people involved in the same software purchase. Which role does each one play?

  1. The Chief Revenue Officer, who owns the budget for the tool and signs the order form

  2. An SDR manager who ran the trial and keeps asking when it will be bought

  3. The security team, which sends the vendor a questionnaire before any contract

  4. A RevOps lead who builds the business case and presents it to the CRO

  5. Procurement, which negotiates the price and the payment terms

  6. The founder of a 30-person startup, who approves every new tool herself

Show the answers
  1. The Chief Revenue Officer, who owns the budget for the tool and signs the order formDecision makerBudget and final approval sit with one person: that is the decision maker, whatever the title.
  2. An SDR manager who ran the trial and keeps asking when it will be boughtChampionPushing for the purchase from inside, without the power to sign, is what a champion does.
  3. The security team, which sends the vendor a questionnaire before any contractGatekeeperSecurity checks the risk of a vendor: it can block the deal, but it does not start it.
  4. A RevOps lead who builds the business case and presents it to the CROChampionMaking the case to the person who signs is the work of a champion.
  5. Procurement, which negotiates the price and the payment termsGatekeeperProcurement controls the terms of the purchase, usually late in the deal, and can stall it.
  6. The founder of a 30-person startup, who approves every new tool herselfDecision makerIn a small company the founder often holds the budget: the role matters, not the title.

Why does a B2B deal need more than one contact?

A B2B deal needs more than one contact because one contact is a single point of failure. If your only contact changes jobs, goes on leave or loses the argument inside, the deal stops and nobody else at the company knows your name. People do change jobs: the data decay page counts how many VPs of Sales in three US cities started their current job since January 2025.

Each role also asks its own questions. Finance asks what it costs and when it pays back, security asks where the data goes, users ask what changes in their day. Reaching several roles early, which sales teams call multi-threading, lets each question reach the person who can answer it instead of landing on your champion.

How do you find the people on a buying committee?

You find the people on a buying committee account by account, with one title search per role. Waterfall ICP runs the tiers above in a single BlitzAPI call: it takes a company page and up to 10 ranked tiers of titles, and returns each person with the tier that found them. The find decision makers use case chains it with email enrichment, so the committee you mapped becomes a list you can contact.

Sources and method

Written by
Antoine Blitz, Founder, BlitzAPI
Published
API calls run on

The calls ran on October 28, 2026 through the BlitzAPI MCP server, which calls the same endpoints; they are shown here as the equivalent REST requests.

The purchase is hypothetical. The tiers show which current titles at this company could play each role in a sales tool purchase, not a deal in progress.

No name and no individual title is shown: each tier is counted by function, because at a named company a unique title points to one person. A title says which role a person could play, not the role they play in a given deal.

Questions people ask

Who are economic buyers?

The economic buyer is the person who controls the budget for a purchase and can approve it alone. In a sales tool purchase, that is usually whoever runs sales or revenue. Other members of the buying committee can recommend, delay or block; the economic buyer is the one who decides.

What is a buying group?

Another name for a buying committee. Some analysts and vendors prefer "buying group", others "buying committee", but both mean the people at one company who take part in a purchase, from the person who signs to the teams that review the vendor and the contract.

What is the definition of a procurement committee?

A group that reviews and approves purchases above a set amount, usually with members from finance, legal and the department that is buying. In a B2B sale, procurement is one of the gatekeepers of the buying committee: it negotiates the terms and checks the vendor, most often late in the deal.

What software helps identify champion and decision-maker insights?

Three kinds of tools, used together. A people search finds the likely decision maker and other roles by title inside a target account. Your CRM and email tools show who replies, attends meetings and forwards your material. Call notes show who argues for the purchase. Titles find candidates; only behavior reveals the champion.

With BlitzAPI

Put it to work

For builders

The calls behind the real data on this page, as REST requests. Send them with your API key, from any language or workflow tool.

The company record

curl -X POST https://api.blitz-api.ai/v2/enrichment/company \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"company_linkedin_url":"https://www.linkedin.com/company/calendly"}'

API reference

The committee, one tier per role

curl -X POST https://api.blitz-api.ai/v2/search/waterfall-icp-keyword \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "company_linkedin_url": "https://www.linkedin.com/company/calendly",
    "cascade": [
      {"include_title": ["Chief Revenue Officer", "Chief Sales Officer", "VP Sales", "SVP Sales", "Vice President Sales", "Head of Sales"],
       "exclude_title": ["Operations", "Enablement", "Engineering", "Regional", "Area", "Assistant"]},
      {"include_title": ["Head of Sales Development", "Director Sales Development", "Sales Development Manager", "Revenue Operations"]},
      {"include_title": ["[Chief Financial Officer]", "VP Finance", "Vice President Finance", "Head of Finance", "Director Finance", "Controller"]},
      {"include_title": ["[Chief Information Security Officer]", "[CISO]", "Head of Security", "Director Security", "Security Compliance", "GRC"]},
      {"include_title": ["[General Counsel]", "Legal Counsel", "Commercial Counsel"]},
      {"include_title": ["Procurement", "Purchasing", "Vendor Management"]},
      {"include_title": ["Account Executive", "Sales Development Representative", "Sales Development Rep", "SDR", "Business Development Representative", "BDR"]}
    ],
    "max_results": 30
  }'

API reference

Data shouldn't be
the problem

Grab. Connect. Build.