Outbound resource
Map a B2B buying committee before personalizing your outreach
Turn a relevant account and verified company signal into a map of the people who may own the workflow, evaluate a change or approve it. Keep confirmed responsibilities separate from role guesses. These three worksheets help a small outbound team coordinate account-based marketing without sending every contact the same pitch.
Editorial update:
Copy the buying-committee worksheets
Original planning templates. Repeat the person record as needed; no fixed committee size is prescribed. Use permitted professional sources and keep contact eligibility in your separate approved workflow.
1. Account and buying-group scope
Account / website / business unit: [identifiers] Supported workflow and proposed change: [specific scope] ICP and verified signal references: [records] Known project status: [confirmed, or unknown] Responsibilities needed for this scope: [roles and reasons] Unidentified owners: [responsibility, next research action] Account coordination owner: [teammate] Existing conversation / next agreed action: [record, or none] Map version / review date: [date and owner]
2. Person and role evidence
Person / current company / business unit: [professional reference] Observed responsibility: [source-supported fact] Evidence source / checked date: [URL or permitted conversation record] Buying responsibility: [confirmed / hypothesis / unknown] Evidence for this project-specific role: [fact, or missing] Relationship to other participants: [confirmed connection, or unknown] Relevant workflow question: [one question] What we must not claim: [unsupported pain, authority or advocacy] Relationship owner / latest interaction: [teammate, record] Next confirmation step / review trigger: [action]
3. Coordinated outreach plan
Account map version: [reference] Recipient and supported responsibility: [record] Verified observation: [accurate statement with source] Why it may matter to this role: [hypothesis] Question or useful asset: [relevant to that responsibility] Other active conversations at this account: [check with owner] Introduction agreed: [by whom and scope, or none] Contact eligibility / suppression check: [separate workflow reference] Sender / next action / owner: [details] Pause condition: [reply, conflicting ownership, request to stop or stale evidence] Reviewer approval: [name, date]
- Copyable worksheets
- 3
- Responsibilities to check
- 5
- Use immediately
- No gate
Buying responsibilities to investigate for your specific use case
Scroll the table sideways to compare all columns.
| Responsibility | Evidence to seek | Question to confirm |
|---|---|---|
| Workflow owner / user | Current responsibility for the process affected | Who runs this process day to day? |
| Internal advocate | Explicit willingness to help evaluate and involve colleagues | Would you want to help assess this, and who should join? |
| Technical or risk evaluator | Responsibility for the relevant integration, data or security review | Who checks whether a change meets these requirements? |
| Business or budget approver | Confirmed approval responsibility for this project and scope | How would a proposal like this be approved? |
| Procurement / contracting | A stated purchasing or contracting step | Is there a supplier onboarding process we should understand? |
Start with the proposed change
Define one workflow your offer can support and the business unit it affects. A company can have different buying groups for different projects. A parent-company executive may have no role in a subsidiary's local software decision. Use your ICP to select the account and your signal record to explain why you are researching it; neither tells you who can approve a purchase.
Map responsibilities, not seniority
Record what each person is known to do before assigning a buying role. A job title can suggest a research direction, but it cannot establish budget authority, advocacy or project involvement. One person may cover several responsibilities, and some responsibilities may be irrelevant to a small purchase. Leave an unknown owner blank rather than manufacturing a complete committee.
Keep the map shared and current
Give the account one coordination owner. Before any new outreach, check the team's latest conversation, agreed next action and contact restrictions. Update the map after a role change, introduction or discovery conversation. LinkedIn's Relationship Maps documentation describes role labels, teammate ownership and stale-lead alerts; the worksheets here are an original tool-independent working method.
Worked example: a regional carrier evaluating dispatch software
Fictional scenario, not a customer result: a regional carrier announces a second depot. Your product supports dispatch planning, but the announcement does not prove a software project exists. A public role description identifies an operations manager responsible for dispatch. The finance director's title is visible, while IT ownership is unknown. Your map initially records one supported workflow responsibility and two research gaps, not three confirmed buyers.
- Operations question: How will dispatch planning be coordinated across the two depots? Do not assert that expansion has created delays.
- Technical question, after the relevant owner is identified: Which data exchange and integration requirements would an evaluation need to cover? Do not infer the deployed stack from a vacancy alone.
- Approval question in the conversation: If a change were worth evaluating, how would the business case be reviewed? Do not contact the finance director as a presumed approver just to fill the map.
- If the operations manager says the existing system covers the expansion, update the hypothesis. If they offer an introduction, record its agreed scope and coordinate the next message with the account owner.
Use AI to find missing evidence, not invent the committee
Give an approved AI tool only the source excerpts and professional information you are permitted to use. Ask it to distinguish facts from proposed roles. A human must check the original source, identity and current responsibility before the map informs outreach. Do not upload confidential conversations to an unapproved service.
- Prompt: Review these supplied account and role records. For each person, quote the supporting excerpt, identify the observed responsibility, label any proposed buying role as a hypothesis, and list what remains unknown. Do not infer budget authority or willingness to advocate from seniority. Do not invent people, sources or relationships. Propose one confirmation question per unresolved responsibility.
- Reject a polished summary that loses the source, changes the business unit or turns a tentative statement into a confirmed role.
Review coverage without turning it into a contact quota
Check whether the responsibilities relevant to this particular change have evidence or an explicit next research step. Contact count is not committee coverage. A friendly reply is not proof of an internal advocate, and several senior contacts do not establish an approval process. Hold outreach when identities conflict, another teammate is already handling the conversation or the proposed message relies on an unsupported claim.
Who this helps
- Founders researching a narrow B2B niche
- SDRs coordinating several conversations at one account
- ABM teams reviewing AI-assisted account research
Work through the process
- 01
Scope
Name the account, business unit and supported workflow.
- 02
Evidence
Record responsibility evidence and label role hypotheses.
- 03
Coordinate
Assign a relationship owner and one relevant next question.
- 04
Revise
Update after introductions, contradictions or role changes.
Questions and answers
- What is a buying-committee map?
- It is a shared record of people and responsibilities involved, or potentially involved, in a specific purchase decision. This template separates evidence, role hypotheses, missing participants and team ownership.
- How many contacts should be on the map?
- There is no universal target here. Map the responsibilities relevant to the proposed change. One person can cover several, and some remain unknown until a conversation confirms them.
- Is this the same as an ideal customer profile?
- No. The ICP defines which organizations fit your offer. The committee map investigates people and decision responsibilities within one account for a particular use case.
- Should every mapped person receive an email?
- No. The map is a coordination and research record. Decide relevance, existing relationship ownership and contact eligibility separately; use agreed introductions when available.
Sources and editorial notes
Original AI-assisted editorial templates and planning conventions prepared for LeadFlow. Examples are illustrative; they are not independently tested results, customer evidence or performance benchmarks. Check facts and adapt the material to your own workflow before use.
Keep reading
Ideal customer profile template
Copy four B2B ICP worksheets for criteria, evidence, list acceptance and reviewer disagreements. Includes examples and a practical research-quality review.
Buying-signal research checklist
Use a B2B buying-signal checklist with evidence and review templates. Verify hiring, expansion and leadership triggers without inventing purchase intent.
ICP Research & List Building
Build a focused account segment, verify niche-specific company signals and prepare role-relevant outreach with AI-assisted research and human review.
B2B discovery call agenda
Use a flexible 30-minute B2B discovery agenda, copyable notes worksheet and recap email. Explore the workflow, check constraints and agree a useful next step.