New customersGet 10% off your first payment on any Prosyo plan.Not available for INR (₹) billing. Valid on your first payment only, for new Prosyo customers.Claim 10% off
Prospecting Open source · MIT v1.0.0

Buying committee mapper Claude skill

Use this whenever a deal depends on one person. Single-threaded deals close far less often than deals with three or more engaged contacts, and they die quietly when the one contact changes jobs or goes quiet.

  • 5-step play
  • 3 guardrails
  • 1 file
  • Human approval built in

Use it when a B2B deal or target account needs more than one contact.

Then just ask your agent

“Map the buying committee for our $80k deal with Contoso. I only talk to the IT manager.”

Watch it work

One request in, expert work out

What happens when you ask your agent with this skill installed. Every step below comes straight from the skill.

Your agentApproval on
You

Map the buying committee for our $80k deal with Contoso. I only talk to the IT manager.

Loaded skill buying-committee-mapper
  1. List the roles the deal needs
  2. Name the people
  3. Score each contact
  4. Plan the threads
  5. Arm the champion
Committee map · Coverage score · Multi-threading plan

Ready for your review. Nothing is sent or changed until you approve.

  • 5Steps in the play
  • 3Guardrails
  • 1Files in the skill
  • 2 minTo read it all

What good looks like

  • At least three engaged contacts before a deal is called "commit".
  • The blocker is identified before the proposal, not after.
  • Outreach to new contacts goes through the champion when possible, so it reads as collaboration rather than going around them.

What you bring

  • Account or deal
  • Known contacts
  • Deal size and product

What you get

  • Committee map
  • Coverage score
  • Multi-threading plan
Raw
name:buying-committee-mapper description:Use this skill when a B2B deal or target account needs more than one contact: "who else should I talk to", "map the buying committee", "multi-thread this deal", or a single-threaded deal is at…

Use this whenever a deal depends on one person. Single-threaded deals close far less often than deals with three or more engaged contacts, and they die quietly when the one contact changes jobs or goes quiet.

Inputs

  • The account or deal, its size and stage.
  • Contacts already engaged and what each has said.
  • The product and the departments it touches.

The play

1. List the roles the deal needs

RoleQuestion they answerTypical titles
Economic buyerIs it worth the money?VP, C-level, budget owner
ChampionWill this make my life and my team better?Manager or director who feels the pain
Technical evaluatorWill it work with what we have?IT, engineering, operations, RevOps
UsersWill I actually use it?Individual contributors
BlockersIs it safe and compliant?Security, legal, procurement, finance
InfluencersWhat do I recommend?Peers, advisors, adjacent team leads

Deal size sets how many roles show up: under $10k often 1-2 people; $10-50k usually 3-5; above $100k usually 6-10.

2. Name the people

For each role, find the most likely person at the account. Mark each as confirmed (they told you or you met them) or inferred (from the org chart or titles).

3. Score each contact

Engagement (none, aware, engaged, active) and sentiment (supporter, neutral, sceptic, unknown). An unknown blocker is the most dangerous cell on the map.

4. Plan the threads

For each gap, decide who reaches out (rep, manager, executive sponsor, solutions engineer), through which route (champion introduction is best, then direct), and what that person needs to hear in their own language.

5. Arm the champion

Give the champion the material they need to sell internally: a one-paragraph business case, the security pack, a short answer to the most likely objection from each other role.

Output format

Deal: <account> - <size> - <stage>
Committee:
  role | name | title | confirmed/inferred | engagement | sentiment | what they need
Coverage: <roles engaged / roles needed>  Risk: <single-threaded? unknown blocker?>
Plan: <next 3 actions with owner and date>
Champion kit: <items to send>

What good looks like

  • At least three engaged contacts before a deal is called "commit".
  • The blocker is identified before the proposal, not after.
  • Outreach to new contacts goes through the champion when possible, so it reads as collaboration rather than going around them.
  • The common mistake is mapping titles without talking to anyone: a map full of inferred names gives false comfort.

Rules

  • MUST mark each person as confirmed or inferred.
  • MUST flag any deal with a single engaged contact as at risk.
  • NEVER contact a new stakeholder in a way that undermines the champion without discussing it with them first.

Example prompts

  • "Map the buying committee for our $80k deal with Contoso. I only talk to the IT manager."
  • "Who else should I bring into this deal, and how?"
  • "Build a multi-threading plan for my top 5 deals."
Try it

Ask your agent like this

Once the skill is installed, plain requests like these load it automatically. Swap in your own company, buyer and numbers.

  • “Map the buying committee for our $80k deal with Contoso. I only talk to the IT manager.”

  • “Who else should I bring into this deal, and how?”

  • “Build a multi-threading plan for my top 5 deals.”

FAQ

Buying committee mapper skill: your questions

What it does, how to install it and how it keeps you in control.

Rather have it done for you? Book a short demo and see Penny run this play on your own market.
Book a demo
Book a demo
What does the Buying committee mapper skill do?

Use this whenever a deal depends on one person. Single-threaded deals close far less often than deals with three or more engaged contacts, and they die quietly when the one contact changes jobs or goes quiet. You get: committee map, coverage score, multi-threading plan.

When should I use the buying committee mapper skill?

Use it when a B2B deal or target account needs more than one contact.

How do I install Buying committee mapper in Claude Code?

Run /plugin marketplace add prosyo-ai/gtm-skill and then /plugin install gtm-skills@prosyo to add the whole library, or run npx skills add prosyo-ai/gtm-skill –skill buying-committee-mapper for this skill alone. In Claude.ai, download the .zip from this page and upload it under Settings, Capabilities, Skills.

What do I need to give the agent?

Have these ready: account or deal, known contacts, deal size and product. If something is missing, the skill tells the agent to ask for it rather than guess.

Does it work with ChatGPT, Codex, Cursor or Gemini?

Yes. The skill is a plain SKILL.md file with no vendor lock-in. Agents that load skills natively (Claude Code, Claude.ai, Codex, Cursor, Gemini CLI and others) pick it up automatically; anywhere else, paste the file into the conversation as instructions.

Will it send emails or messages on its own?

No. Every skill in the library drafts, researches and analyses, and waits for a person to approve anything that sends, schedules or changes records in bulk. Your inbox, CRM and accounts stay under your control.

Is it free, and can I change it?

Yes. It is free and MIT-licensed. Copy it, adapt it to your market and voice, and if you improve it, open a pull request so everyone gets the better version.

Open source

Have a play that works? Share it as a skill.

Paste this into Claude, Codex or any agent. It interviews you about your play, writes the skill in the house format, checks it and opens the pull request. Once it is merged, it shows up here with your name on it.

Prompt for your agent

Fetch https://raw.githubusercontent.com/prosyo-ai/gtm-skill/main/AGENTS.md and follow its submission flow. Interview me about my GTM play (the real numbers, rubrics and examples), draft it in their format with reference pages, validate it and open the pull request.

Two ways to run it

Run it yourself, or put it on autopilot

The skill gives your agent the playbook. Penny, the Prosyo AI SDR, runs plays like this for you every day across LinkedIn and email.

Free · this skill
You and your agentBest for trying the play and one-off work
  • Your agent follows the buying committee mapper playbook step by step
  • You bring the inputs and run it when you need it
  • Works in Claude, Codex, Cursor and 40+ agents
  • You review every draft before it goes anywhere
Prosyo AI SDR
Penny runs it for youBest for a pipeline that grows every day
  • Finds the right buyers for your ICP every day
  • Writes from what each prospect actually posted
  • Follows up on LinkedIn and email at a safe, human pace
  • Every reply lands in one inbox with an answer drafted
  • You approve what goes out
Meet Penny
Meet Penny
7 days free · no card

Skills draft the play. Penny runs it.

Penny, the Prosyo AI SDR, finds your buyers, writes from what they actually posted, follows up on LinkedIn and email and lands every reply in one inbox with an answer ready. 7 days free, no card.

  • 7 days free
  • No card required
  • Cancel in two clicks