Back to guides
/Linked API

B2B Buying Committee: How to Map One on LinkedIn with an AI Agent

Deals rarely hang on one person. The question is who the others are at your target account, and how to find them before the deal goes quiet.

The short version. A B2B buying committee is the group of people at one account who shape a purchase: typically a champion who advocates for the change internally, an economic buyer who controls budget, technical and operational evaluators, the day-to-day users, a security, legal or procurement gate, and often an executive sponsor. There is no universal size – it grows with price, risk and company size. To map it, name the roles first, then find candidates for each: search the company's employees on LinkedIn by title and by how close they are to your network, read their profiles and recent posts as evidence, and mark each role as a guess with a confidence level until conversations confirm it. An AI agent or a script can run that research on your own LinkedIn account; reporting lines and budget authority are never on LinkedIn, so the map stays an informed hypothesis.

What is a B2B buying committee?

A buying committee is everyone at the customer who can move, slow or stop a purchase – the people who evaluate, approve and live with the decision. Mapping it for one target account is what sales teams call account mapping (not to be confused with partner account mapping, which compares customer lists between companies).

RoleWhat they care aboutClues on LinkedInTitle keywords to search
Champion (advocate)Getting the change through; mobilizes colleaguesPosts about the problem; a role in the affected team. A problem owner is only a potential champion until they advocateHead of, Manager + the function
Economic buyerReturn, cost, priorityBudget-owning seniority in the functionVP, Director, C-level of the function
Technical or operational evaluatorIntegration, security, implementationEngineering, IT, operations, data rolesEngineer, Architect, IT, Operations
User or workflow representativeDay-to-day fitHands-on titles in the teamSpecialist, Analyst, Representative
Security, legal or procurement gateRisk, terms, vendor processSecurity, legal, procurement departmentsSecurity, Legal, Procurement, Compliance
Executive sponsorStrategic fit, breaking deadlocks – see selling to the C-suiteExecutive titles above the functionCEO, COO, CRO, CFO

A few rules keep the map honest:

  • There is no universal size. Committees grow with price, risk and company size.
  • One person can fill several roles – at a smaller company the economic buyer may also be the champion.
  • A title match gives a candidate, not a role. LinkedIn's own sales terms define the champion as an advocate, and that shows in behavior, not in a job title.

Here is that map for one account, researched by an AI agent on your own LinkedIn account through Linked API:

Your Agent
runs on your own LinkedIn account
Map the buying committee at Example Target for our RevOps analytics product. Search the company's employees for each title keyword – "Head of Revenue Operations", "RevOps Manager", "VP Sales", "Chief Revenue Officer", "Salesforce Administrator", "Data Engineer", "Sales Operations Analyst", "Procurement", "Security" – and list the decision makers LinkedIn shows for the company. For the top 3 candidates per role, read their profile and posts from the last 90 days. Give each an inferred role, a confidence level with the evidence, and my connection degree, and list the roles with no candidate. Send nothing – stop for my review.
Agentvia MCP Server
Used Linked API: fetch_company, fetch_person
  • employees by position, one title keyword per call; the first call also returns the decision makers LinkedIn lists
  • 27 people from the title searches and 12 decision makers, 4 of them in both – 35 people; nobody for "Security"
  • current position, experience and posts from the last 90 days for the top candidates per role

35 people at Example Target; the top 13 read. Champion: 1 high, 2 low. Economic buyer: 2 medium, 1 low. Technical evaluator: 1 high, 2 medium. User: 3 medium. Security, legal or procurement: 1 low – a procurement manager; no matching security title found in these searches. Nothing has been sent. The strongest candidate per role:

PersonInferred roleConfidence and evidenceYour connection
Dana K.Champion (candidate)High – Head of Revenue Operations; a post last month on fixing forecast accuracy2nd
Marcus T.Economic buyerMedium – Chief Revenue Officer; nothing on the profile contradicts it3rd+
Priya S.Technical evaluatorHigh – Salesforce Administrator; her experience lists a CPQ rollout1st
Leo B.UserMedium – Sales Operations Analyst; nothing on the profile contradicts it2nd
Ana R.Security, legal or procurement gateLow – title keyword match only ("Procurement Manager")3rd+

nothing goes out until you have reviewed the map and chosen whom to contact first

Works withClaudeCodexChatGPTCursorOpenClaw
Example run, fictional company and people. Roles stay inferred – reporting lines and budget authority are not on LinkedIn – and a champion is confirmed only in conversation. Employee searches are bounded by what your account can see. Works in Claude, ChatGPT, Cursor or Claude Code through the MCP server or the CLI.

Why single-threaded deals stall

A deal with one contact rests on one person's calendar, priorities and job. If they go quiet, change roles or turn out not to hold the budget, the deal stalls with nobody else to call. Multithreading in sales means building relationships with several members of the committee, each on the questions they own, so the deal does not depend on any one of them.

Where the map comes from

RouteBest forWatch out for
Sales Navigator, by handReps who already have a seat and map a few accountsCreating CRM contacts – with an optional stakeholder role on an opportunity – requires Advanced Plus and CRM Sync (LinkedIn Help); the evidence-and-confidence map is still yours to maintain
Sales-engagement platforms with org-chart featuresTeams that live in that platform, its database and their CRM – Amplemarket, for example, describes an Org Chart Skill and a deal contact gap analysis built on its own data and HubSpotThe map comes from the vendor's data; LinkedIn is an outreach channel there, not the source
LinkedIn research on your own account (Linked API)Agents and scripts that query LinkedIn directly and write the map in the shape you needBounded by what your account can see; roles stay inferred

Role-first mapping is not new – it is how good account executives already work. What changes with the last route is who does the legwork: an agent or a script runs the LinkedIn research, and you review the result.

How to map a buying committee from LinkedIn

  1. Name the roles and title keywords for this deal, using the table above. A RevOps tool and a security product have different committees.
  2. Pull candidates per role.
    • Search the company's employees by position keyword, one search per keyword, optionally narrowed by location and by connection degree (1st, 2nd, 3rd+). One search returns up to 1,000 people.
    • Add the decision makers LinkedIn lists for the company – up to 20.

The reference for both is in the docs: company employees and decision makers.

  1. Read the evidence. For the strongest candidates, open the profile (current position, experience) and recent posts.
  2. Assign roles with a confidence level and the evidence behind each:
    • high – the role is stated or clearly shown: a matching title plus posts or experience that fit;
    • medium – the title fits and nothing contradicts it;
    • low – a title-keyword match only.

A champion is confirmed only by what they do in conversations, never by title.

  1. Mark warm paths. 1st-degree candidates you can message directly. For 2nd-degree candidates, look up your mutual connections – the label shows proximity, not a named introducer.
  2. Find the gaps – roles with no candidate – and decide whom to research next.
  3. Write the map to your CRM or a sheet. A person reviews it before any outreach.

Run it with an AI agent

The research runs from a plain-language instruction like the one in the run near the top of this page. Connect an assistant such as Claude to your account through the MCP server – fetch_company with employees and decision makers, fetch_person for profiles and posts – the agent-friendly CLI, or a ready-made skill. Setup is covered in giving an AI agent access to LinkedIn.

The pause before outreach is part of your instruction, not a built-in approval queue – keep it explicit.

Build it into your own tools

Developers can run the same research in their own code: one fetchCompany call per title keyword with retrieveEmployees and a position filter – add retrieveDMs for the decision makers – then fetchPerson with experience and posts for the closest candidates. The role rules can be a plain function over those fields. Each call is asynchronous: execute starts the work and returns a workflow ID, and result waits for it. A search LinkedIn refuses comes back in errors, so mark that role incomplete rather than empty – an unfinished search is not evidence that nobody holds the role. SDK setup: Node and Python SDKs; the same searches also run from the CLI.

Multithreading without noise

  • Start with your strongest relationship and ask how the decision actually gets made – that conversation corrects the map faster than any search. In an existing customer that is usually your champion – mapping expansion there is land and expand.
  • Write to each role about what it owns. The economic buyer cares about return and priority, the evaluator about integration, the user about daily work. One pitch to everyone reads as spam.
  • Never imply a colleague shared anything they did not.
  • Choose the right first touch. Check the connection degree to decide between an invitation and a message, and keep first touches reviewed – see AI for sales prospecting.
  • Watch who is already engaging. People reacting to your posts or viewing your profile may already be on the committee – see LinkedIn buying signals.

Limits

  • Reporting lines and budget authority are not on LinkedIn. Every role is inferred until the buyer confirms it.
  • Titles are self-reported and vary between companies.
  • Employee lists are bounded by what LinkedIn shows your account.
  • A 2nd-degree label is proximity, not an introduction.
  • No emails or phone numbers – Linked API works with what LinkedIn shows.
  • Pace and limits. Profile views and searches count toward per-action limits by category and period (limits API). The account runs in a dedicated cloud browser at a human pace.

Pulling a company's employee list as data, rather than mapping a committee, is covered in the company scraper guide.

Frequently Asked Questions (FAQ)

Typically a champion, an economic buyer, technical and operational evaluators, users, a security, legal or procurement gate, and often an executive sponsor. One person can hold several of these roles.

There is no universal number. It grows with the price of the purchase, the risk it carries and the size of the company.

Search the company's employees by title and seniority keywords, check the decision makers LinkedIn lists for the company, then confirm each candidate on their profile and recent posts.

Building relationships with several members of the buying committee, so a deal does not depend on one contact's availability or authority.

Yes, for the research: an agent can search employees, read profiles and posts and draft the map on your own account. The roles stay inferred, and a person reviews the map before any outreach.

Build it in, or hand it to an agent

Build the research into your own tools with the REST API, the Node and Python SDKs or the CLI. Or have an AI agent run it out of the box through the MCP server, the agent-friendly CLI or a ready-made skill. Plans start at $49 a seat a month billed annually – see pricing.

Facts verified October 12, 2026 – Sales Navigator CRM contact creation against LinkedIn Help; Amplemarket's org-chart and gap-analysis features against its live guide on that date.