Account tiering
You need to decide which accounts get the most effort.
You get Tiered account list · Score breakdown · Effort rules per tier
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.
Use it when a B2B deal or target account needs more than one contact.
“Map the buying committee for our $80k deal with Contoso. I only talk to the IT manager.”
What happens when you ask your agent with this skill installed. Every step below comes straight from the skill.
Map the buying committee for our $80k deal with Contoso. I only talk to the IT manager.
buying-committee-mapperReady for your review. Nothing is sent or changed until you approve.
What good looks like
What you bring
What you get
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.
| Role | Question they answer | Typical titles |
|---|---|---|
| Economic buyer | Is it worth the money? | VP, C-level, budget owner |
| Champion | Will this make my life and my team better? | Manager or director who feels the pain |
| Technical evaluator | Will it work with what we have? | IT, engineering, operations, RevOps |
| Users | Will I actually use it? | Individual contributors |
| Blockers | Is it safe and compliant? | Security, legal, procurement, finance |
| Influencers | What 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.
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).
Engagement (none, aware, engaged, active) and sentiment (supporter, neutral, sceptic, unknown). An unknown blocker is the most dangerous cell on the map.
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.
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.
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>
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.”
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.
Use it when a B2B deal or target account needs more than one contact.
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.
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.
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.
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.
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.
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.
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.
The skill gives your agent the playbook. Penny, the Prosyo AI SDR, runs plays like this for you every day across LinkedIn and email.
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.