sales-account-map

Name: sales-account-map
Author: sales-skills

83installs9forks

How to install sales-account-map?

sales-skills/sales/sales-account-map

$npx -y skills add sales-skills/sales --skill sales-account-map

Installs into the current project.

Summary

Maps the buying committee at a target account — identify decision-makers, influencers, champions, and blockers, then recommend a multi-threading strategy. Use when stuck single-threaded in a deal, don't know who the real decision-maker is, can't figure out the right entry point a

Files · 1

View on GitHub

SKILL.md

1	# Map the Buying Committee
2
3	Help the user map the full buying committee at a target account — identify who's involved in the purchase decision, what role each person plays, and how to multi-thread the account effectively. This skill is platform-agnostic but references Apollo.io as the primary data source for finding and enriching contacts. The same approach works with ZoomInfo, Cognism, LinkedIn Sales Navigator, or any contact database.
4
5	## Step 1 — Gather context
6
7
8	If `references/learnings.md` exists, read it first for accumulated knowledge.
9
10	Ask the user:
11
12	1. Which account are you targeting? (Company name, size, industry)
13
14	2. What are you selling?
15	- Product/service category
16	- Approximate deal size (affects committee size and complexity)
17	- Which department does it primarily affect?
18
19	3. Where are you in the process?
20	- A) Prospecting — haven't engaged anyone yet
21	- B) Single-threaded — talking to one person, need to expand
22	- C) Active deal — have some contacts, need to map the full committee
23	- D) Stuck deal — need to find the missing stakeholder(s)
24
25	4. What do you know already?
26	- Any existing contacts at the account?
27	- Any org chart intel (reporting structure, team size)?
28	- Any intel on their buying process?
29
30	5. Company size? (This determines committee complexity)
31	- A) SMB (1-200 employees) — expect 1-3 decision-makers
32	- B) Mid-market (200-2,000 employees) — expect 3-6 stakeholders
33	- C) Enterprise (2,000+ employees) — expect 5-12+ stakeholders
34
35	If the user's request already provides most of this context, skip directly to the relevant step. Lead with your best-effort answer using reasonable assumptions (stated explicitly), then ask only the most critical 1-2 clarifying questions at the end — don't gate your response behind gathering complete context.
36
37	## Step 2 — Identify the committee roles
38
39	Map expected roles using this framework:
40
41	### Buying committee roles
42
43	\| Role \| What they do \| How to identify \| Typical titles \|
44	\|---\|---\|---\|---\|
45	\| Economic Buyer \| Has budget authority, signs the check \| Highest-ranking person in the buying org; often VP+ or C-suite \| VP/SVP/CRO/CFO/CTO depending on what you sell \|
46	\| Champion \| Wants your product to win, advocates internally \| Has the problem you solve, engaged in conversations, asks for resources to share internally \| Director/Senior Manager who owns the problem \|
47	\| Technical Evaluator \| Vets the product technically \| Asks detailed technical questions, runs POCs, owns integration \| Architect, Staff Engineer, IT Manager, Solutions team \|
48	\| User Buyer \| Will use the product daily \| Cares about workflow, UX, and day-to-day impact \| Individual contributors, team leads, end users \|
49	\| Coach \| Gives you intel on internal politics and process \| Usually someone you have a relationship with; may not have buying authority \| Any level — could be a former customer, mutual connection, or friendly contact \|
50	\| Gatekeeper/Blocker \| Can slow or kill the deal \| Owns competing budget, prefers a competitor, or has political reasons to oppose \| Procurement, Legal, IT Security, or a peer of the Champion who prefers the status quo \|
51
52	### Scaling the committee by company size
53
54	\| Company size \| Roles to map \| Contacts to find \|
55	\|---\|---\|---\|
56	\| SMB (1-200) \| Economic Buyer + Champion (often the same person), maybe 1 Technical Evaluator \| 2-3 contacts \|
57	\| Mid-market (200-2,000) \| Economic Buyer, Champion, Technical Evaluator, 1-2 User Buyers \| 4-6 contacts \|
58	\| Enterprise (2,000+) \| All 6 roles, potentially multiple people per role (committee of 8-12+) \| 6-12 contacts \|
59
60	## Step 3 — Find the people
61
62	For tool-specific search filters (Apollo People Search, ZoomInfo Org Charts), read `references/platforms.md`
63	and pull the section for the data tool the user has.
64
65	### Interpreting org structure from data
66
67	Apollo (and most data providers) don't show reporting lines directly. Reconstruct the org chart by:
68
69	1. Seniority mapping: Group contacts by seniority level (C-suite → VP → Director → Manager → IC)
70	2. Department clustering: Group by department to see team structure
71	3. **Title

People who liked this also viewed

6 picks

Type

sales-account-map

83installs9forks

View on GitHub

How to install sales-account-map?

sales-skills/sales/sales-account-map

$npx -y skills add sales-skills/sales --skill sales-account-map

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Map the Buying Committee
2
3	Help the user map the full buying committee at a target account — identify who's involved in the purchase decision, what role each person plays, and how to multi-thread the account effectively. This skill is platform-agnostic but references Apollo.io as the primary data source for finding and enriching contacts. The same approach works with ZoomInfo, Cognism, LinkedIn Sales Navigator, or any contact database.
4
5	## Step 1 — Gather context
6
7
8	If `references/learnings.md` exists, read it first for accumulated knowledge.
9
10	Ask the user:
11
12	1. Which account are you targeting? (Company name, size, industry)
13
14	2. What are you selling?
15	- Product/service category
16	- Approximate deal size (affects committee size and complexity)
17	- Which department does it primarily affect?
18
19	3. Where are you in the process?
20	- A) Prospecting — haven't engaged anyone yet
21	- B) Single-threaded — talking to one person, need to expand
22	- C) Active deal — have some contacts, need to map the full committee
23	- D) Stuck deal — need to find the missing stakeholder(s)
24
25	4. What do you know already?
26	- Any existing contacts at the account?
27	- Any org chart intel (reporting structure, team size)?
28	- Any intel on their buying process?
29
30	5. Company size? (This determines committee complexity)
31	- A) SMB (1-200 employees) — expect 1-3 decision-makers
32	- B) Mid-market (200-2,000 employees) — expect 3-6 stakeholders
33	- C) Enterprise (2,000+ employees) — expect 5-12+ stakeholders
34
35	If the user's request already provides most of this context, skip directly to the relevant step. Lead with your best-effort answer using reasonable assumptions (stated explicitly), then ask only the most critical 1-2 clarifying questions at the end — don't gate your response behind gathering complete context.
36
37	## Step 2 — Identify the committee roles
38
39	Map expected roles using this framework:
40
41	### Buying committee roles
42
43	\| Role \| What they do \| How to identify \| Typical titles \|
44	\|---\|---\|---\|---\|
45	\| Economic Buyer \| Has budget authority, signs the check \| Highest-ranking person in the buying org; often VP+ or C-suite \| VP/SVP/CRO/CFO/CTO depending on what you sell \|
46	\| Champion \| Wants your product to win, advocates internally \| Has the problem you solve, engaged in conversations, asks for resources to share internally \| Director/Senior Manager who owns the problem \|
47	\| Technical Evaluator \| Vets the product technically \| Asks detailed technical questions, runs POCs, owns integration \| Architect, Staff Engineer, IT Manager, Solutions team \|
48	\| User Buyer \| Will use the product daily \| Cares about workflow, UX, and day-to-day impact \| Individual contributors, team leads, end users \|
49	\| Coach \| Gives you intel on internal politics and process \| Usually someone you have a relationship with; may not have buying authority \| Any level — could be a former customer, mutual connection, or friendly contact \|
50	\| Gatekeeper/Blocker \| Can slow or kill the deal \| Owns competing budget, prefers a competitor, or has political reasons to oppose \| Procurement, Legal, IT Security, or a peer of the Champion who prefers the status quo \|
51
52	### Scaling the committee by company size
53
54	\| Company size \| Roles to map \| Contacts to find \|
55	\|---\|---\|---\|
56	\| SMB (1-200) \| Economic Buyer + Champion (often the same person), maybe 1 Technical Evaluator \| 2-3 contacts \|
57	\| Mid-market (200-2,000) \| Economic Buyer, Champion, Technical Evaluator, 1-2 User Buyers \| 4-6 contacts \|
58	\| Enterprise (2,000+) \| All 6 roles, potentially multiple people per role (committee of 8-12+) \| 6-12 contacts \|
59
60	## Step 3 — Find the people
61
62	For tool-specific search filters (Apollo People Search, ZoomInfo Org Charts), read `references/platforms.md`
63	and pull the section for the data tool the user has.
64
65	### Interpreting org structure from data
66
67	Apollo (and most data providers) don't show reporting lines directly. Reconstruct the org chart by:
68
69	1. Seniority mapping: Group contacts by seniority level (C-suite → VP → Director → Manager → IC)
70	2. Department clustering: Group by department to see team structure
71	3. **Title

People who liked this also viewed

6 picks

Type