Skip to content
B2BenrichA ContactLevel company

Map the buying committee at every target account

Who sits on a B2B buying committee, how to find them at each account by function and seniority, and how to get their contact details.

Dag Holmen · Updated · 5 min read

View as Markdown

A buying committee is the group of people at one company who decide whether to buy: the person who signs, the person who pushes for it, the people who'll use it, the person who checks that it works and the people who can say no. In a larger B2B deal, one contact rarely decides alone.

Buying committee mapping means finding those people at every target account, by role, and getting the contact details to reach more than one of them. With an API, it's a loop over your account list. This guide covers the roles, how to find each one with B2Benrich's people search, and how to add work emails and phone numbers.

The roles on a buying committee

RoleWhat they care aboutWhere to look
Economic buyerCost, return and risk. Approves the budget.Senior level (VP or C-level) in the function that owns the problem
ChampionFixing the problem. Sells you internally.Director or manager level in the same function
UsersDaily workflow and ease of useIndividual contributors in the same function
Technical evaluatorSecurity, integration and dataIT, engineering or operations
BlockersContracts, compliance and spendProcurement, legal, security, finance

The people change with company size. At a 60-person company, the founder might be the economic buyer, champion and technical evaluator at once. At a 5,000-person company, each role can be several people across regions. Map the roles first, then see who fills them.

Step 1: Write the role map as config

Keep your committee as data, not as a list in someone's head. For a product sold to sales teams, it might look like this:

{
  "economic_buyer": { "job_function": "Sales", "job_level": "VP", "max": 1 },
  "champion": { "job_function": "Sales", "job_level": "Director", "max": 2 },
  "technical": { "job_function": "Information Technology", "job_level": "Director", "max": 1 },
  "finance": { "job_function": "Finance", "job_level": "Director", "max": 1 }
}

Every value is a placeholder. Get the real ones from /v1/search/meta/job_function and /v1/search/meta/job_level. The persona filter is worth a look too, via /v1/search/meta/persona.

Step 2: Search each role at each account

POST /v1/search/company-employees takes a company domain (or linkedin_url or id) plus the role's filters:

curl --request POST \
  --url https://api.b2benrich.com/v1/search/company-employees \
  --header 'Content-Type: application/json' \
  --header 'X-Api-Key: YOUR_API_KEY' \
  --data '{
    "domain": "acme.com",
    "job_function": "Sales",
    "job_level": "VP",
    "page": 1,
    "page_size": 5
  }'

Trimmed, with fictional values:

{
  "records": [
    {
      "id": "7781203",
      "full_name": "Maya Chen",
      "first_name": "Maya",
      "last_name": "Chen",
      "job_title": "VP of Sales",
      "linkedin_url": "https://www.linkedin.com/in/maya-chen-example",
      "company_name": "Acme",
      "company_domain": "acme.com",
      "company_id": "123456"
    }
  ]
}

That's one call per role per account, so script it. The people search API guide covers paging and the other filters.

Step 3: Fill gaps with title-company

Some roles are one specific title, like "Head of Revenue Operations", and some accounts arrive as names without domains. For those gaps, POST /v1/search/title-company takes a job_title and a company_name and returns people with that title there. When you have the domain, company-employees is safer, because names are ambiguous.

Step 4: Add work emails

For each person, POST /v1/enrich/person/name-domain-to-email takes first_name, last_name and domain and returns { status, email }. Use the record's company_domain as the domain. Treat a missing email as not found and keep the status for debugging. The email finder API guide has the details.

Step 5: Add phone numbers for the key roles

A call is worth it for the two or three people who decide. B2Benrich returns phone numbers, including mobiles and direct dials, so add them for the economic buyer and champion at your top accounts. The phone number API guide covers when to call and how to keep dialing lists compliant.

The whole loop

import os, json, requests

BASE = "https://api.b2benrich.com"
HEADERS = {"X-Api-Key": os.environ["B2BENRICH_API_KEY"], "Content-Type": "application/json"}

def post(path, body):
    r = requests.post(f"{BASE}{path}", json=body, headers=HEADERS, timeout=30)
    r.raise_for_status()
    return r.json()

def get_phone(person):
    # TODO: replace with the B2Benrich phone endpoint
    return None

ROLES = json.load(open("roles.json"))  # the role map from step 1
CALL_ROLES = {"economic_buyer", "champion"}

committee = []
for domain in ["acme.com", "globex.com"]:
    seen = set()
    for role, spec in ROLES.items():
        filters = {k: v for k, v in spec.items() if k != "max"}
        people = post("/v1/search/company-employees", {
            "domain": domain, **filters, "page": 1, "page_size": spec["max"],
        })["records"]
        for p in people:
            if p["id"] in seen:
                continue
            seen.add(p["id"])
            found = post("/v1/enrich/person/name-domain-to-email", {
                "first_name": p["first_name"],
                "last_name": p["last_name"],
                "domain": p["company_domain"],
            })
            committee.append({
                "domain": domain, "role": role, "id": p["id"],
                "name": p["full_name"], "title": p["job_title"],
                "linkedin_url": p["linkedin_url"],
                "email": found.get("email"),
                "phone": get_phone(p) if role in CALL_ROLES else None,
            })

The seen set stops one person from filling two roles at the same account.

What the map looks like

AccountRoleNameTitleEmailPhone
acme.comEconomic buyerMaya ChenVP of Salesmaya.chen@acme.com+1 512 555 0143
acme.comChampionSam OrtizDirector of Sales Developmentsam.ortiz@acme.com+1 512 555 0178
acme.comTechnicalnot found

The empty row tells the rep which role to ask about on the first call. Track coverage per account as roles filled out of roles in the map. An account with one contact is single-threaded, whatever its pipeline stage says.

Multi-threading with the map

Multi-threading means working several committee members at once, so the deal doesn't hang on one person.

  • Start with the champion. They feel the problem and can tell you who else matters.
  • Give the economic buyer a different message. Cost and risk, not features.
  • Send the technical evaluator something useful early, like security or integration docs, so they aren't the last to hear.
  • Stagger the outreach. Five people at one company getting the same email on the same morning will compare notes.

Keep the map current

Rerun the role searches for open accounts every month and compare IDs. A new VP is a new economic buyer. A champion who left is a reason to call their replacement, and to follow the champion to their next company. B2Benrich is unlimited API usage for $500 a month with no credits, so rerunning the map for every open account doesn't change your bill.

To find the accounts worth mapping in the first place, see TAM mapping with an API.

Frequently asked questions

What is a buying committee?
A buying committee is the group of people at a company who take part in a purchase decision. It usually includes an economic buyer who approves the budget, a champion who pushes for the purchase, the people who will use the product, a technical evaluator and stakeholders who can block the deal, such as procurement or legal.
How do I find the decision makers at a company?
Search the company’s employees by function and seniority. With B2Benrich, send the company domain to /v1/search/company-employees with job_function and job_level filters, using exact values from the meta endpoint, then add work emails with name-domain-to-email.
What is buying committee mapping?
Buying committee mapping is finding the people who fill each committee role at every target account and recording their contact details. It shows which roles you’ve reached and which are still missing at each account.
What is multi-threading in B2B sales?
Multi-threading means building relationships with several people on the buying committee at once, so a deal doesn’t depend on a single contact. If your one contact leaves or goes quiet, the deal still has other people behind it.
How many contacts should I have per account?
At least one per role in your committee map. Start with the champion and the economic buyer, then add the technical evaluator and anyone who can block the deal. Larger companies may need more than one person per role.

Get your API key.

Sign up, make your first call and start building your lists.

We’ll email you a link to log in. · Read the docs