---
name: buying-committee-mapping
slug: buying-committee-mapping
description: This skill should be used when the user asks to "map a buying committee", "identify decision makers", "find the buying group", "map stakeholders at an account", "multi-thread an account", "figure out who's involved in the deal", "identify the economic buyer", "map the org chart for a deal", or any variation of identifying and mapping the people involved in a B2B SaaS purchase decision.
category: general
---

# Buying Committee Mapping

Every B2B SaaS deal above $20K ACV is a committee decision. The average B2B buying committee has 6-10 people across 3-4 functions. Single-threaded deals (one contact, one relationship) close at roughly half the rate of multi-threaded deals. Map the committee before outreach. Update it throughout the deal.

## The 6 Committee Roles

Every buying committee has some combination of these roles. One person can hold multiple roles. Some roles may be absent in smaller orgs. But every deal has at least a champion, an economic buyer, and a technical evaluator.

| Role | Definition | Typical titles | What they care about |
|------|-----------|---------------|---------------------|
| Champion | The person who feels the pain daily and will sell internally | Manager, Director, Sr. IC | "Does this solve my specific problem?" |
| Economic Buyer | Controls budget. Signs the contract | VP, C-level, Head of | "What's the ROI? What's the risk?" |
| Technical Evaluator | Validates the tool works, integrates, and is secure | Eng lead, IT, Security, Ops | "Does it integrate? Is it secure? Will it break?" |
| Influencer | Affected by the decision but doesn't own it | Adjacent team leads, cross-functional stakeholders | "How does this impact my team?" |
| End User | Will use the product daily post-purchase | ICs, analysts, reps | "Is this easy to use? Does it save me time?" |
| Blocker | Actively or passively resists the purchase | Incumbent tool owner, skeptic, competing-priority leader | "Why change? My way works fine" |

### Role identification rules

- **Champion first.** Always identify and engage the champion before anyone else. Without internal sponsorship, deals stall regardless of how good the pitch is
- **Economic buyer second.** Know who signs the check before the first discovery call. If unknown after call 1, ask the champion directly: "Who else would need to be involved in a decision like this?"
- **Blocker early.** Most deals that die had an unidentified blocker. Ask: "Who on the team might see this differently?" and "Is anyone invested in the current approach?"
- **One person, multiple roles.** In companies under 100 employees, the champion and economic buyer are often the same person. In companies under 50, one person might hold champion + economic buyer + technical evaluator. Don't force 6 different contacts when 2 cover the committee

---

## Mapping Process

### Step 1: Start with what you know

Before any external research, check internal sources:

| Source | What it reveals | Time |
|--------|----------------|------|
| CRM history | Prior contacts, past deals, activity history | 2 min |
| Email / calendar | Anyone who's been in a thread or meeting | 2 min |
| Colleague knowledge | "Has anyone here talked to someone at [account]?" Slack search, ask around | 3 min |
| Event attendee lists | Who from the account attended your webinars, dinners, conferences | 2 min |

Internal data is higher quality than any external source because it captures actual engagement, not inferred relevance.

### Step 2: Map from LinkedIn

LinkedIn is the primary external source for committee mapping.

**Process:**
1. Search the company on LinkedIn. Filter by current employees
2. Filter by relevant functions: Sales, Marketing, Revenue Operations, Engineering, IT, Product (adjust to your buyer profile)
3. Identify contacts by title that match committee roles
4. For each contact, capture: name, title, LinkedIn URL, tenure in role, recent activity (posts, comments, engagement)

**Title-to-role mapping (B2B SaaS):**

| Title pattern | Likely role | Confidence |
|--------------|-------------|------------|
| VP Sales, CRO, VP Revenue | Economic buyer (for sales tools) | High |
| VP Marketing, CMO | Economic buyer (for marketing tools) | High |
| VP Engineering, CTO | Economic buyer (for dev tools) + technical evaluator | High |
| Director of [function] | Champion or influencer | Medium-high |
| Head of RevOps, Sales Ops, Marketing Ops | Champion (for ops tools) | High |
| Manager of [function] | Champion or end user | Medium |
| Sr. Engineer, Staff Engineer | Technical evaluator | Medium-high |
| IT Manager, Security Lead | Technical evaluator (security/compliance gate) | High |
| SDR Manager, AE Manager | End user + influencer (for sales tools) | Medium |

**LinkedIn research rules:**
- Check tenure. Contacts in role < 6 months are high-value targets. New hires buy tools. Lifers defend incumbents
- Check activity. A contact who posts 3x/week about the problem you solve is a better champion candidate than a silent profile
- Check connections. Mutual connections = warm intro path. Note these for the engagement strategy
- Don't rely on LinkedIn titles alone. "Head of Growth" at a 20-person startup is a different role than "Head of Growth" at a 2,000-person company. Check the profile description and recent posts for context

### Step 3: Enrich from secondary sources

After LinkedIn, layer in additional data:

| Source | Best for finding | How to use |
|--------|-----------------|-----------|
| Conference speaker lists | Champions (people who talk publicly about the problem) | Search recent events in the space. Cross-reference with LinkedIn |
| Podcast guest lists | Economic buyers and champions | Search their name or company + "podcast" |
| GitHub contributors | Technical evaluators at dev tool companies | Check the company's GitHub org for active contributors |
| Company about/team page | Leadership roles, org structure | Often outdated, but useful for confirming economic buyer titles |
| Press quotes | Economic buyers (execs quoted in press are public-facing) | Google "[company name] + [exec name]" |
| G2/TrustRadius reviews | End users (reviewers are often the day-to-day users) | Note reviewer title and what they praise/criticize |
| Job postings authored by | Hiring managers are usually the champions or influencers | Check who posted the role on LinkedIn |

### Step 4: Score and prioritize

For each contact, assign a priority score based on:

| Factor | Low (1) | Medium (2) | High (3) |
|--------|---------|------------|----------|
| Role relevance | End user or influencer | Technical evaluator | Champion or economic buyer |
| Tenure | 3+ years (status quo bias) | 1-3 years | < 1 year (new broom) |
| Activity level | Silent profile | Occasional engagement | Active poster/commenter |
| Accessibility | No mutual connections, no prior engagement | Some mutual connections | Direct connection, prior interaction, warm intro available |
| Signal alignment | No personal signal | General interest in the space | Actively posting about the problem you solve |

Total score ≥ 10 = primary target. 7-9 = secondary. Below 7 = monitor only.

---

## The Committee Map Document

Output the map as a simple table. This is the artifact that lives in CRM or the account brief.

| Name | Title | Role | Priority | Stance | Key signal | Engagement plan |
|------|-------|------|----------|--------|-----------|----------------|
| Jane Kim | Director of RevOps | Champion | 12/15 | Likely champion | Posted about attribution gaps last week | Email sequence → LinkedIn connect → event invite |
| Mark Chen | VP Sales | Economic buyer | 11/15 | Neutral | New hire (started Jan 2026) | Email after champion engages → direct mail |
| Priya Patel | Sr. Sales Engineer | Technical evaluator | 9/15 | Unknown | Active on GitHub, maintains internal tools | Engage after champion intro, technical teardown |
| Tom Walsh | IT Security Lead | Technical evaluator (security) | 8/15 | Potential blocker | Company just got SOC 2 | Loop in during evaluation, not before |
| Sarah Liu | SDR Manager | End user + influencer | 7/15 | Likely supporter | Complained about sequencing tool on LinkedIn | Monitor, use as validation source |

### Map document rules

- Minimum 3 contacts, ideally 5-7 for deals above $50K ACV
- Contacts must span at least 2 functions. A committee from one department is not a committee, it's a team
- "Stance" is a hypothesis until confirmed in conversation. Label as "likely," "potential," or "unknown." Never "confirmed" until they've told you directly
- "Engagement plan" assigns the channel and sequence per contact. Not everyone gets the same treatment. Champions get the full outreach sequence. Technical evaluators may only get engaged after the champion opens the door
- Update the map after every interaction. New names surface during discovery calls. Roles shift. Blockers emerge. A static map is a stale map

---

## Identifying Hidden Roles

### Finding the real economic buyer

The person with budget authority is not always obvious from title alone.

**Signals that someone is the economic buyer:**
- They ask about pricing, contract terms, or ROI on the first call
- The champion defers to them: "I'd need to run that by [name]"
- They control the timeline: "We'd want to do this before Q3 planning"
- They're CC'd on procurement or legal emails
- Their LinkedIn shows P&L responsibility in the profile description

**Common mistakes:**
- Assuming the most senior person is the economic buyer. A CRO might delegate tool purchases to a VP. A VP might delegate to a Director with a discretionary budget
- Never asking. "Who else would need to sign off on something like this?" is a normal question. Ask it on the first call

### Finding blockers before they kill the deal

Blockers rarely announce themselves. Surface them proactively.

**Questions to ask the champion:**
- "Who on the team might see this differently?"
- "Is anyone particularly invested in the current approach?"
- "Has something like this been tried before? What happened?"
- "Who would be most affected by changing the current process?"

**Blocker patterns:**
- The person who built the internal tool you'd replace
- The person who championed the incumbent vendor's purchase
- A leader in a competing-priority department who needs budget from the same pool
- The IT/security lead who defaults to "no" on new vendors without a formal review
- A recent hire who just implemented the current process and doesn't want to redo it

### Finding influencers who tip the deal

Influencers don't buy but their opinion matters disproportionately.

**Common influencer profiles:**
- The exec's trusted advisor (often a Chief of Staff, senior IC, or long-tenured director)
- The cross-functional partner whose workflow integrates with the buyer's (e.g., Marketing Ops for a sales tool purchase)
- The finance partner who validates ROI models
- The team that piloted a similar tool at a previous company and can vouch for the category

---

## Committee Size by Deal Size

| ACV range | Typical committee size | Minimum contacts to map | Functional breadth |
|-----------|----------------------|------------------------|-------------------|
| < $20K | 1-2 people | 1 | Single function |
| $20-50K | 2-4 people | 2 | 1-2 functions |
| $50-150K | 4-6 people | 3-4 | 2-3 functions |
| $150-500K | 6-10 people | 5-6 | 3-4 functions |
| $500K+ | 8-15 people | 7-8 | 4+ functions + procurement |

### Procurement and legal

For deals above $100K, procurement and legal often enter the process late. They are not buying committee members in the traditional sense (they don't evaluate the product) but they can delay or kill deals.

- Identify the procurement contact early. Ask: "What does your purchasing process look like for a tool like this?"
- Ask about security review requirements before the technical evaluation. A 6-week security review you didn't know about can blow a timeline
- Prepare an MSA/DPA/security questionnaire in advance. Having these ready when procurement asks saves 2-4 weeks

---

## Multi-Threading the Committee

Mapping the committee is step one. Engaging multiple contacts simultaneously (multi-threading) is step two.

### Multi-threading rules

- **Start with the champion.** All other threads flow from this relationship. If the champion hasn't engaged, emailing the economic buyer looks like going over their head
- **Ask for introductions.** After the champion is engaged: "Would it make sense to loop in [name] for the [technical / budget / workflow] side of this?" The champion introducing you internally is 10x more effective than a cold email to the same person
- **Stagger, don't blast.** Never email 3+ contacts at the same account on the same day. It looks like a coordinated campaign, not individual relationships. Space by 2-3 days minimum
- **Different angle per role.** The champion cares about day-to-day pain. The economic buyer cares about ROI and risk. The technical evaluator cares about integration and security. Same product, different framing per contact
- **Track thread status per contact.** In CRM, log the status of each contact independently: uncontacted, contacted, engaged, supporting, neutral, blocking

### When to go around the champion

Sometimes the champion isn't enough. Escalate carefully.

- **Champion is engaged but can't move the deal forward.** They lack organizational influence. Engage the economic buyer directly with a peer-level message (founder-to-VP or VP-to-VP)
- **Champion went dark after initial engagement.** Wait 2 weeks, then reach out to a parallel contact at the same level (a peer, not their boss)
- **Champion explicitly says "I need help getting buy-in."** This is an invitation. Ask who to engage and what they need to see. Prepare materials for the champion to share internally

**Never go around the champion without a reason.** Blind escalation burns the champion relationship and the deal.

---

## Anti-Pattern Check

- Single-threaded deal above $30K ACV. If there's one contact and one relationship, the deal is fragile. One vacation, one reorg, one priority shift kills it. Multi-thread or accept the risk and note it in the forecast
- Mapping the committee after the demo. Too late. The demo should be designed for the specific roles in the room. Map before first meeting, validate during, update after
- Assuming titles = roles. "VP of Sales" at a 30-person startup is a different buyer than "VP of Sales" at a 3,000-person company. Validate role through conversation, not LinkedIn title
- Ignoring blockers because "we have a strong champion." Champions get overruled. Blockers who surface at the 11th hour kill deals that were "90% closed." Identify them early
- Mapping 15 contacts at a 50-person company. Overkill. The committee at a small company is 2-3 people. Don't over-engineer it
- Never updating the map. People leave, get promoted, change roles. A committee map from 3 months ago is a guess. Refresh before every key milestone (demo, proposal, negotiation)
- Emailing the economic buyer before anyone else. Unless you have a direct relationship or a warm intro, this reads as "I'm skipping the people who actually use the product to pitch the person with the checkbook." Start with the champion