Map a B2B buying committee from evidence

Begin after you have qualified the account and the relevance of the people already known. A committee map needs a defined initiative: the change being considered, its current stage and the decision the account is working toward. An account can have several unrelated purchases underway. Someone responsible for one purchase may have no responsibility for another.

Write the initiative in language the account has confirmed. If all you have is a public expansion announcement, record that as context; it does not establish an active evaluation of your service. Until a person confirms the initiative, use a provisional research note and a modest discovery question. Do not present an imagined purchase process as account intelligence.

The working example throughout this guide is fictional. Merebrook Field Services has confirmed that it is considering a shared technician onboarding checklist for two depots. Its immediate decision is whether to run a limited pilot. A later company-wide purchase would need a fresh review of responsibilities. Keeping that boundary visible prevents a pilot contact from acquiring assumed authority over a larger commitment.

List the work that this purchase may require: defining the operational need, testing the proposed approach, checking technical or security requirements, arranging purchasing steps, authorizing spend and signing an agreement. These are prompts for discovery, not a required committee structure. One person may perform several jobs, a group may share one job, and some jobs may not apply to the current decision.

A job title is useful for finding a plausible starting point, but it does not establish budget ownership, veto power or signing authority. Record an action you need to understand, such as who confirms the pilot’s success criteria. This produces an answer that can guide the next conversation more reliably than a broad label such as influencer.

Salesforce’s opportunity contact role fields separate a Primary contact marker from a configurable Role field. Treat those as record fields whose meaning your team must define for the initiative. A primary contact designation alone does not document approval authority.

Use three evidence states consistently. Observed means a specific statement or action supports the responsibility. Inferred means you have a reason to investigate it. Unknown means you have no adequate basis to assign it. Observed evidence can still become outdated or apply only to a narrow task.

For Merebrook’s pilot, the following fictional notes are current at 6 November 2026. The evidence is invented for teaching. Each row identifies a responsibility rather than ranking a person’s power. The map contains three named participants and three unassigned responsibilities; that is a feature of this example, not a recommended committee size.

Keep evidence and interpretation in separate fields. Store the relevant email or meeting-note reference so another owner can check the original context. For example, Jon’s request supports his involvement in a review. It does not prove that he can approve the vendor, that the review has started, or that approval will follow.

When a responsibility has no name, preserve the empty assignment and write a question beside it. Filling every cell with the most senior available employee makes the map look complete while weakening its usefulness.

Ask which unknown actually blocks the current decision. Merebrook can discuss pilot success criteria before it identifies a signatory. It should clarify the purchasing route before someone treats a proposed paid pilot as authorized. The next question depends on the next commitment, not on a desire to finish the organization chart.

Use the existing conversation to locate the responsibility where appropriate. Ask Leah whether this pilot needs a purchasing review and how she prefers that question to be handled. She may answer it herself, offer an introduction, provide a team address or say the purchase is not ready. Record that answer without converting a referral into an endorsement.

If the current contact cannot identify the owner, keep the responsibility unknown. Agree on a later checkpoint or pause the affected step. Separately researched outreach may sometimes be relevant, but it needs its own evidence and purpose. A missing name is not permission to start parallel sequences to a department.

Add a contact plan beside the role map. Each proposed message needs a relevant purpose, an internal owner and an expected output. Teammates can then see when another person owns the conversation and whether a follow-up would duplicate a live exchange.

In this fictional plan, the account owner coordinates the initiative while specialists handle specific questions. Transfer the current request, its context and the agreed next step when ownership changes. Check active conversations before releasing another message.

Existing reply handling should stop or adjust the original sequence when a conversation changes. The committee map supplies account context for that handoff. It should not become a second, conflicting system for preferences, opt-outs or follow-up dates.

A useful introduction request names the responsibility you need to understand and gives the recipient room to choose the route. Avoid saying that a colleague recommended your solution when they only identified a contact. If you have no relationship or referral, explain the public or direct context honestly.

These fictional messages illustrate two different evidence states. Adapt the wording to what happened, including whether the person invited direct contact. Do not use an example as permission to imply a conversation that never occurred.

Review the map after a meaningful conversation, a change of scope or a handoff. Preserve the previous evidence date and record why the assignment changed. If a pilot becomes a wider rollout, revisit approval, review and signing responsibilities instead of carrying the old map forward automatically.

Conflicting statements need a clarifying question, not a confidence score that hides the disagreement. Suppose Leah expects content review to finish this week while Samir says depot supervisors must first test the checklist. Record both statements, their dates and the unresolved dependency. Ask who will consolidate the test feedback and what that means for the pilot decision.

Keep contact plans responsive to those updates. A person who has completed a review may need no further outreach until a new question arises. A newly identified participant may need a concise handoff of relevant context, not the entire campaign history. Respect the account’s stated coordination preferences.

The review outcome should be an action with an owner: request clarification, revise the pilot scope, transfer the conversation, wait until an agreed date or close the initiative. More mapped names are not, by themselves, evidence of progress.

Use one worksheet per initiative and keep it alongside the account record. Begin with the people and evidence already available. Unassigned responsibilities are acceptable; each should have either a relevant discovery question or a reason that no action is needed yet.

Before sending, read the proposed contact row aloud: this person is receiving this message because of this evidence, and this owner is responsible for the result. If the explanation depends only on seniority or another employee’s silence, revise the plan. Review the worksheet when new evidence changes the next decision.