Resources / Buying Committee Mapper
Live Account Mapping Sales Navigator

Multi-thread the account. Without the templates.

For a target account + a pitch, the skill maps the 4–7 roles that matter for THIS deal, generates the Sales Nav search URL to find each one, and gives a per-role outreach angle. No generic "EB + champion + user" templates.

Download skill Install instructions
v1.0 Generates Sales Nav URLs Per-role outreach angles Deal-context aware
BC
buying-committee-mapper.zip
16.9 KB · Bundle: .skill file + SKILL.md inside · v1.0
Download skill
Want to read what it does first? View source ↓
What it does

Templates don't close deals. Specific committees do.

Single-threaded outreach into one persona is the biggest cause of stalled deals. Real B2B buying decisions involve 5–10 people. But "Economic Buyer + Champion + User" as a deliverable isn't useful, that's a framework, not a plan.

The skill asks for the deal context first: what's being sold, who feels the pain primarily, deal-size band, sales motion, account size. Those answers shift the committee meaningfully, a $5K self-serve tool has a 2-role committee; a $250K platform deal has 6–7.

For each role, you get the title patterns to search (not just "the CFO", also VP Finance, Head of Finance Ops, Director Finance at mid-market), the Sales Nav URL, and the outreach angle. EBs care about ROI; technical evaluators care about integration burden. The skill won't pitch features to a CFO.

Try saying

Any of these will work.

Who should I target at [Company]?
Map the buying committee at this account.
Find me 4-5 people to reach at [Company].
Multi-thread this account for a $80K RevOps tool.
How it works

Five steps.

01

Gather deal context

Target account, pitch, function feeling pain, deal-size band, motion, account size. Asks before assuming, generic committees don't close deals.

02

Pick the roles

Default 4–5: EB, Champion, End User, Technical Evaluator, sometimes Blocker. Sub-$10K deals collapse to 2–3; enterprise deals add Ratifier.

03

Translate to titles

For each role, generate the title patterns to search. The EB might be CFO, VP Finance, OR Head of Finance Ops depending on company size.

04

Build the URLs

Sales Nav search URLs per role, scoped to the target account. Structured filters first; keywords as last resort, max 2 terms.

05

Per-role outreach

Each role gets: what they care about, what to lead with, what to avoid, and when in the cycle to engage them.

Why it doesn't lie to you

Built to be specific to the deal.

!

Never names specific people

Without verified data, the skill produces role definitions + search URLs. Inventing "Sarah, the VP Sales" at a real company invites fabrication.

#

Deal-context-aware sizing

A $200/month tool with a 7-role committee plan is over-engineered. The skill pushes back when committee size doesn't match deal size.

@

Title patterns, not labels

"Economic Buyer" is shorthand. The user needs the actual title strings. The skill generates them precisely for the company size and category.

?

Sequencing recommendation included

Not just "here are 5 people", but the order to engage them in. Champion first, EB after warm intro, blocker last.

The output

A plan, not a template.

Per role: title patterns, the Sales Nav search URL, the outreach angle (cares about / lead with / avoid / engage when). Plus a sequencing recommendation and an explicit note on which standard roles were dropped and why.

Sample role
ROLE 2: CHAMPION Titles: Director RevOps, Head of RevOps, Sr. Mgr Revenue Ops Seniority: Director, Sr IC Function: Operations Outreach angle: Cares about: looking good internally, ammo for the internal pitch Lead with: workflow pain Engage: earliest
Committee contract
Output
Markdown plan + URLs
Committee size
2–7 roles (deal-sized)
Required tools
None (uses ICP context)
Per-role artifacts
Titles + URL + angle
Sequencing
Included
Pairs with
salesnav-search-builder
Install

Pick your Claude. Drop in the skill.

The download is a zip containing two things: the .skill file (what you upload to Claude) and a SKILL.md sidecar (the human-readable instructions). Unzip first, then follow the steps for your Claude.

⌘
Most people

Claude.ai or Desktop

  1. Download and unzip the bundle.
  2. Open or create a Project in Claude.
  3. Go to Project knowledge, click Add content.
  4. Upload the .skill file from the unzipped bundle.
  5. Start a new chat in that project. Ask it to run the skill.
Download bundle ↓ No restart needed
›_
Developers

Claude Code

  1. Download and unzip the bundle.
  2. Unzip the inner .skill file too (it's also a zip).
  3. Move the resulting folder into ~/.claude/skills/
  4. Restart Claude Code.
  5. Type a prompt that fits the trigger. The skill loads automatically.
Download bundle ↓ macOS / Linux / WSL
{ }
Builders

API or Agent SDK

  1. Download and unzip the bundle.
  2. Open the SKILL.md sidecar to read the full instructions.
  3. Load via the Skills API, or paste the instructions into your agent's system prompt.
  4. Make sure your agent has web_search and file output enabled.
  5. Ship it.
View SKILL.md ↓ v1.0
Source

Read the full instructions.

This is exactly what Claude reads when the skill triggers. No hidden prompts, no separate config. What you see here is what you get.

MD
buying-committee-mapper-SKILL.md 11.7 KB · the full skill instructions
⌄
Loading SKILL.md...

Need help implementing this on your team?

We'll install the skills, customize them to your workflow, and run the output through your team's combined LinkedIn network. Skills do the research, Linkd does the motion.

Book a demo