Skip to main content
DoneThat

AI Adoption GuideSalesQualify

Buying-committee mapping

NLP and graph analysis identify decision-makers, champions, and blockers across the account, using tools like People.ai.

Sales processProspectQualifyDiscoverProposeNegotiateCloseHandoffRenew

By Don, DoneThat’s AI coach · updated

The committee is your activity graph, not an org chart

The living map is economic buyer, champion, and blockers, named from your calls, emails, and Salesforce, not from a scraped org chart.

LinkedIn Sales Navigator is useful for hypotheses: reporting lines, public titles, job changes. It is not the committee. A VP on LinkedIn who has never been on a call, in a thread, or on an opportunity contact role is a person you have not met. Treating their title as decision rights is the usual way this use case goes wrong.

People.ai, Gong, LinkedIn Sales Navigator, and Salesforce belong to the same class. They are not a ranking. None of them should invent a title the person never used in your data. If Salesforce says "Manager" and the call recording says "I run the warehouse," write the deal role from the cite and leave the job title as recorded. Do not silently promote them to VP.

What belongs on the map:

  • Economic buyer. Someone who can release budget or sign. Cite a call, an email, or a contact role. If you cannot cite, leave the seat empty and flag it.
  • Champion. Someone with internal will and enough access to move the process. Enthusiasm on a discovery call is not enough. You need evidence they will spend political capital: they booked the next meeting with a peer, they sent the internal brief, they argued for you when a blocker spoke.
  • Blockers. Named people who have slowed, opposed, or rerouted the deal, with a cite. Silence is not a blocker. A missing function (procurement never invited) is a coverage hole, not a person to invent.

Empty seats are honest. A pretty org chart with guessed names is not a qualify artifact. MEDDIC auto-extraction writes champion, metrics, and decision criteria into CRM fields with a cite. This page is the people layer those fields sit on.

Extract roles from calls, email, and CRM

Pull roles from evidence you already have. Then mark what is still missing.

Work the sources in this order so titles cannot outrun activity:

  1. Salesforce contact roles and activity. Who is on the opportunity, who was last emailed, who is on the next event. This is the system of record. If the role is blank, it stays blank until a cite exists.
  2. Calls (Gong and the rest of that class). Who spoke, who was named as the signer, who was promised an intro, who objected on process, security, or price. Quote enough to defend the role in a forecast call. Do not infer a champion because the AE liked the call.
  3. Email and calendar (People.ai and the rest of that class). Who is actually on threads, who forwards internally, who dropped off. Volume is not influence. The busiest correspondent is often an operator or an EA.
  4. LinkedIn Sales Navigator last, as a check. Use it to notice a job change, a new reporting line, or a person you have never engaged. Do not copy the public org into Salesforce as the committee.

For every person on the map, store three things: the role you claim (economic buyer, champion, blocker, or unassigned), the last live touch, and the cite. No cite means unassigned.

Flag a missing economic buyer as soon as the opportunity is in qualify and no cite exists. That flag should show up on the pre-call account briefing so the next meeting has a job: get a name, get an intro, or accept that you are still single-threaded with a user.

Do not invent a champion to make the MEDDIC card look complete. If the only friendly contact cannot book a meeting with finance, they are a coach or a user, not a champion. Leave champion empty.

Do not ignore procurement until late. If your motion always hits vendor onboarding, security review, or a purchasing desk, and none of those people are on the map, that is a coverage hole. Add the function as missing. Do not wait for a packet in week ten and then treat procurement as a surprise blocker.

A missing economic buyer is a qualify gap

If you cannot name the economic buyer with a cite, the deal is not mapped. It may still be a real evaluation. It is not a complete committee.

The failure mode is promotion: the AE has a lively champion, a demo, and a date, so the opportunity moves. The map still has an empty buyer seat. Forecast treats the empty seat as "we will get there."

Put the empty seat on the qualify checklist next to MEDDIC fields. If champion is also empty, you are not multi-threaded; you have a tour guide. That pattern is a reason to run a disqualification recommender review, not a reason to keep adding meetings with the same person.

The map should make the next action obvious: ask the known contact for the signer by name, ask who owns the budget line, or accept a no-bid. It should not fill the buyer box with the most senior LinkedIn title at the account.

Keep departed people off the map

A living map drops people who no longer work there. It does not keep their role warm as a courtesy.

Job-change alerts from LinkedIn Sales Navigator, a bounced email, an out-of-office that says they left, or a call where a peer says they are gone are enough to remove them from economic buyer, champion, or blocker. Leave them on the account as history if your CRM needs the activity. Do not leave them as the champion on the opportunity.

Champion-departure monitoring is the later watch, especially after close. In qualify, the same rule applies earlier: yesterday's champion is not today's committee.

Do not auto-promote the next title in the scraped org to fill the hole. The replacement has to earn the role the same way: a cite from a call, an email, or a new contact role. Until then, champion or buyer is empty again, and the missing-seat flag comes back.

When the deal does close, the map that a sales-to-CS handoff briefing should carry is this living version: who actually bought, who blocked, who left. Not the first discovery list.

Illustrative deal: the VP who was never the buyer

A map built from LinkedIn titles will name the wrong buyer, invent a champion, and miss procurement until the paper arrives.

The following is a made-up but realistic qualify cycle, not a measured program and not reported results.

An AE is selling warehouse software into a mid-market manufacturer. Sales Navigator shows a VP of Operations with warehouse language in the about line. The AE books a call. The VP is warm, asks for a pilot price, and says they will get this done this quarter. The AE writes economic buyer and champion on the same contact, copies two other Operations directors from LinkedIn into Salesforce, and calls the committee mapped.

Call recordings show the VP never claimed budget authority. They said they would need to run this by finance, and that purchasing has a list. Email capture shows the VP's EA on every thread, and a procurement specialist CC'd once on a security questionnaire that nobody followed. Nobody from finance has been on a meeting.

Two weeks later purchasing sends a vendor packet. The VP goes quiet. The directors from LinkedIn never replied. The opportunity still shows a complete committee because the titles looked right.

What the map should have been:

  • Champion: the VP, with a cite (they booked the pilot conversation). Not economic buyer.
  • Economic buyer: empty, flagged. Next meeting job: a named intro to whoever owns the budget line.
  • Blockers / missing functions: procurement on the map as a coverage hole from the first "purchasing has a list" line, not as a surprise in week three.
  • The two directors: off the committee until they appear in a call or a thread. Public titles are not attendance.

The AE did not need a better org chart. They needed to stop treating LinkedIn as the committee, stop inventing a champion-buyer hybrid, and stop ignoring procurement until late.

People.ai, Gong, LinkedIn Sales Navigator, and Salesforce will only show the network you actually load. The quality bar is a map you can defend on a forecast call: three roles, cites, empty seats visible, departed people gone.

Is this worth automating for you?

Whether this pays back depends on how much time it takes your team today. Most teams estimate that from memory, and the estimate is usually wrong in one direction or the other.

DoneThat reconstructs where the time actually went, with no timers to forget, so you can measure the baseline before committing to a project and check the gain afterward.

Measure the baseline first