
decision-maker-identification
When the user wants to build or improve a sales bot's ability to identify decision-makers vs gatekeepers. Also use when the user mentions "decision maker," "buyer identification," "gatekeeper detection," "authority detection," or "economic buyer."
- Installs
- 416
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/louisblythe/sales-skills --skill decision-maker-identification- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads decision-maker-identification automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Decision-Maker Identification
You are an expert in building sales bots that identify whether they're talking to decision-makers or gatekeepers. Your goal is to help developers create systems that detect authority level and adjust conversation strategy accordingly.
Why Identification Matters
The Gatekeeper Trap
Problem scenario:
You pitch features for 20 minutes to someone
who then says: "Sounds great, I'll pass this
along to my boss who makes these decisions."
Result:
- Wasted detailed pitch
- Information filtered/lost
- No direct relationship with buyer
- Competitor might pitch directly
The Right Approach
Identify early, adjust accordingly:
Talking to gatekeeper:
→ Gather information
→ Understand their influence
→ Ask for introduction to decision-maker
→ Position them as ally
Talking to decision-maker:
→ Qualify thoroughly
→ Pitch with authority
→ Drive toward decision
→ Handle objections directly
Detection Signals
Title-Based Signals
Typically decision-makers:
- C-suite (CEO, CFO, CTO, CMO)
- VP-level
- Director-level (depends on company size)
- "Head of..." roles
- Owners/Founders
Often gatekeepers/influencers:
- Coordinator
- Specialist
- Analyst
- Associate
- Junior/Entry-level titles
- "Assistant to..."
But title isn't everything:
- Small company manager = decision-maker
- Large company VP = might need board approval
Language Signals
Decision-maker language:
- "I'm looking for..."
- "We need..."
- "I want to see..."
- "My budget is..."
- "I can approve..."
- "Let me decide if..."
- Uses "I" for decisions
Gatekeeper language:
- "My boss wants me to..."
- "I'm researching for..."
- "I'll need to run this by..."
- "They asked me to find..."
- "I can recommend..."
- Uses "they" for decisions
Question Patterns
Decision-makers ask:
- ROI and business impact questions
- Timeline and implementation questions
- Contract and pricing questions
- "What happens if we need to scale?"
- Strategic fit questions
Gatekeepers ask:
- Feature/function checklist questions
- "Can you do X?" lists
- Comparison/research questions
- "What should I know before presenting?"
- Process-oriented questions
Authority Indicators
def detect_authority_signals(message, context):
signals = {
"high_authority": [
r"I (can|will) (decide|approve|sign)",
r"my (team|budget|department)",
r"I('m| am) (the|responsible for)",
r"final (decision|say|call)",
r"I (need|want) to (see|understand)"
],
"low_authority": [
r"(need to|have to) (check with|ask|run by)",
r"(my|the) (boss|manager|VP|director) (wants|asked)",
r"I('ll| will) (recommend|present|share)",
r"gathering (info|options|quotes)",
r"evaluating (for|on behalf)"
]
}
authority_score = 0
for pattern in signals["high_authority"]:
if re.search(pattern, message, re.IGNORECASE):
authority_score += 1
for pattern in signals["low_authority"]:
if re.search(pattern, message, re.IGNORECASE):
authority_score -= 1
return authority_score
Direct Discovery Questions
Soft Discovery
Questions that reveal authority without being awkward:
"Who else would be involved in evaluating this?"
→ Reveals if there are others above them
"What does your decision process typically look like?"
→ Reveals their role in that process
"When decisions like this get made, who usually
has the final say?"
→ Direct but professional
"Are you the one who'd be using this day-to-day,
or more evaluating for the team?"
→ User vs buyer distinction
Direct Authority Questions
More direct approaches (use carefully):
"Are you the right person to discuss
budget and timeline with?"
"Do you have the authority to move forward
if this is a good fit?"
"Would this decision need approval from
anyone else, or is it your call?"
Be matter-of-fact, not challenging.
BANT Authority Questions
Budget: "Is there budget allocated for this?"
→ If they don't know, probably not decision-maker
Authority: "Would you be signing off on this?"
→ Direct authority check
Need: "Is this something you're personally trying to solve?"
→ Their skin in the game
Timeline: "When are you looking to have this implemented?"
→ Decision-makers have urgency
Adjusting Strategy
Talking to Decision-Makers
Strategy:
- Qualify thoroughly
- Focus on business outcomes, not features
- Discuss ROI and strategic value
- Be direct about pricing and process
- Ask for decision timeline
- Handle objections immediately
Tone:
- Peer-to-peer
- Consultative
- Value their time
- Direct and efficient
Talking to Gatekeepers
Strategy:
- Gather information about decision-maker
- Understand their influence on decision
- Make them look good to their boss
- Equip them with compelling materials
- Ask for introduction/inclusion
Questions:
"What matters most to [boss name] when
evaluating solutions like this?"
"What would you need to see to recommend
this to your team?"
"Would it be helpful if we set up a call
that includes [decision-maker]?"
Talking to Influencers
Influencers ≠ gatekeepers. They can't decide
but they can torpedo or champion.
Strategy:
- Respect their expertise
- Address their specific concerns
- Make them a champion
- But don't over-invest in convincing them
- Always aim for decision-maker access
"I can tell you know this space well.
What would make you comfortable recommending
this to [decision-maker]?"
Multi-Stakeholder Situations
Mapping the Buying Committee
Track stakeholders as they emerge:
{
"deal_id": "12345",
"stakeholders": [
{
"name": "Sarah Chen",
"title": "VP Marketing",
"role": "economic_buyer",
"authority": "high",
"sentiment": "positive"
},
{
"name": "Mike Johnson",
"title": "Marketing Manager",
"role": "champion",
"authority": "medium",
"sentiment": "very_positive"
},
{
"name": "Lisa Wong",
"title": "IT Director",
"role": "technical_evaluator",
"authority": "veto_power",
"sentiment": "neutral"
}
]
}
Role Types (MEDDIC)
Champion:
- Internally sells for you
- Has access to power
- Personally invested in success
Economic Buyer:
- Controls budget
- Final authority on spend
- Often C-level or VP
Technical Evaluator:
- Assesses technical fit
- Can say no, rarely says yes alone
- Often IT or operations
User Buyer:
- Will use the product daily
- Cares about usability
- Influences but doesn't decide
Coach:
- Internal guide
- Shares information
- May not have authority but has knowledge
Navigating to Power
When stuck at wrong level:
From user to manager:
"You'd be using this daily—your input is key.
But for budget and timeline, would it make sense
to include [their manager] in our next call?"
From manager to VP:
"I want to make sure we address any strategic
concerns early. Would [VP] want to be involved
at this stage, or prefer to weigh in later?"
From gatekeeper to decision-maker:
"You've done great research. To move things
forward, I'd love to connect with [decision-maker]
directly. Would you be able to introduce us?"
Bot Conversation Adjustments
Dynamic Depth Based on Authority
Low authority detected:
- Keep pitch high-level
- Focus on helping them evaluate
- Provide shareable materials
- Ask about decision-maker preferences
High authority detected:
- Go deeper on value and ROI
- Discuss implementation details
- Be ready for pricing discussion
- Drive toward next steps
Authority-Based Routing
def route_conversation(prospect, authority_score):
if authority_score >= 2: # Likely decision-maker
return {
"track": "executive",
"messaging": "strategic_roi",
"cta": "schedule_demo",
"escalation": "enterprise_ae"
}
elif authority_score == 1: # Potential influencer
return {
"track": "influencer",
"messaging": "feature_benefit",
"cta": "include_decision_maker",
"escalation": "standard_ae"
}
else: # Likely gatekeeper
return {
"track": "researcher",
"messaging": "educational",
"cta": "send_materials",
"escalation": "sdr_handoff"
}
Escalation Triggers
Escalate to human when:
- High authority + high intent detected
→ Valuable conversation, don't lose it
- Decision-maker asks pricing
→ Negotiation opportunity
- Multiple stakeholders mentioned
→ Complex deal, needs human navigation
- Authority unclear after 3 exchanges
→ Human can probe more naturally
Edge Cases
Small Company Dynamics
In small companies:
- Titles mean less
- Founder/CEO often involved early
- Fewer stakeholders
- Faster decisions
Adjust: Assume higher authority earlier
Enterprise Complexity
In large enterprises:
- Multiple decision-makers
- Procurement involved
- Long evaluation cycles
- Committee decisions
Adjust: Expect lower individual authority,
map full buying committee
Authority Shifts
Authority can change mid-conversation:
"Actually, let me loop in my VP for this."
→ Adjust expectations, prepare for new audience
"I just got promoted—this is now my call."
→ Increase engagement depth
"Budget decisions moved up to executive team."
→ Re-map stakeholders
Metrics
Identification Accuracy
Track:
- Predicted authority vs actual decision-maker
- Time to identify decision-maker
- Deals lost due to wrong-level engagement
Improve:
- Refine detection signals
- Earlier direct questions
- Better title/context mapping
Conversion by Authority Level
Track funnel by identified authority:
Decision-makers:
- Meeting rate: X%
- Close rate: Y%
- Deal size: $Z
Influencers:
- Meeting rate: X%
- Close rate: Y%
- Deal size: $Z
Gatekeepers:
- Meeting rate: X%
- Close rate: Y%
- Deal size: $Z
Invest energy proportionally.
FAQ
What does the decision-maker-identification skill do?
When the user wants to build or improve a sales bot's ability to identify decision-makers vs gatekeepers. Also use when the user mentions "decision maker," "buyer identification," "gatekeeper detection," "authority detection," or "economic buyer."
How do I install decision-maker-identification?
Run npx skills add https://github.com/louisblythe/sales-skills --skill decision-maker-identification in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/decision-maker-identification/ (personal) or .claude/skills/decision-maker-identification/ (project).
Which AI agents can use decision-maker-identification?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is decision-maker-identification safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains decision-maker-identification?
It is published by louisblythe in louisblythe/sales-skills. It has 416 recorded installs.
More from louisblythe/sales-skills
appointment-booking
louisblythe/sales-skills
When the user wants to build or improve a sales bot's ability to integrate with calendars and schedule meetings autonomously. Also use when the user mentions "booking meetings," "calendar integration," "scheduling calls," "appointment setting," or "automated booking."
objection-handling
louisblythe/sales-skills
When the user wants to improve their ability to address prospect concerns, overcome resistance, or respond to pushback without being defensive. Also use when the user mentions "handling objections," "overcoming resistance," "common objections," "prospect pushback," "they said no," or "dealing with concerns."
sales-presentations
louisblythe/sales-skills
When the user wants to create, optimize, or improve sales presentations, pitch decks, demos, or proposal presentations. Also use when the user mentions "sales deck," "pitch deck," "demo presentation," "proposal deck," "investor pitch," "executive presentation," "sales slides," "presentation optimization," or "how to present." This skill covers structuring, designing, and delivering compelling sales presentations.
outbound-prospecting
louisblythe/sales-skills
When the user wants help with outbound sales prospecting, lead sourcing, or pipeline building. Also use when the user mentions 'prospecting,' 'lead sourcing,' 'finding leads,' 'building pipeline,' 'cold outreach,' 'target account list,' 'ICP,' 'buyer persona,' 'lead list,' or 'account-based.' This skill covers prospecting strategy, lead research, multi-channel outreach, and pipeline generation.
closing
louisblythe/sales-skills
When the user wants to improve their ability to recognize buying signals, ask for the sale, and confidently move deals to commitment. Also use when the user mentions "closing deals," "asking for the sale," "getting commitment," "buying signals," "sealing the deal," or "converting prospects."
sales-psychology
louisblythe/sales-skills
When the user wants to apply psychological principles to sales conversations, understand buyer behavior, or use persuasion techniques ethically. Also use when the user mentions 'buyer psychology,' 'why people buy,' 'persuasion,' 'influence,' 'decision-making,' 'cognitive bias,' or 'negotiation psychology.' This skill provides 70+ mental models organized for sales application.
Popular business & finance skills
sales-enablement
coreyhaines31/marketingskills
When the user wants to create sales collateral, pitch decks, one-pagers, objection handling docs, or demo scripts. Also use when the user mentions 'sales deck,' 'pitch deck,' 'one-pager,' 'leave-behind,' 'objection handling,' 'deal-specific ROI analysis,' 'demo script,' 'talk track,' 'sales playbook,' 'proposal template,' 'buyer persona card,' 'battle card,' 'battlecard,' 'competitive one-pager,' 'win-loss analysis,' 'why are we losing deals,' 'loss reasons,' 'how do I respond to this objection,' 'prospect just said,' 'help my sales team,' 'sales materials,' or 'what should I give my sales reps,' 'cold call script,' or 'voicemail script.' Use this for any document or asset that helps a sales team close deals. For public competitor comparison pages, see competitors. For running buyer interviews or churn research, see customer-research. For marketing website copy, see copywriting. For cold outreach emails, see cold-email. For the offer being sold (bonuses, guarantees, pricing structure),
revops
coreyhaines31/marketingskills
When the user wants help with revenue operations, lead lifecycle management, or marketing-to-sales handoff processes. Also use when the user mentions 'RevOps,' 'revenue operations,' 'lead scoring,' 'outbound pipeline stages,' 'lead routing,' 'MQL,' 'SQL,' 'pipeline stages,' 'deal desk,' 'CRM automation,' 'marketing-to-sales handoff,' 'data hygiene,' 'leads aren't getting to sales,' 'pipeline management,' 'lead qualification,' or 'when should marketing hand off to sales.' Use this for anything involving the systems and processes that connect marketing to revenue. For cold outreach emails, see cold-email. For email drip campaigns, see emails. For pricing decisions, see pricing.
sales-funnel-blueprint
autonnel/autonnel-skills
Turn an offer into a concrete multi-step sales funnel spec - page-by-page structure, price ladder, copy outline and the metrics each step must hit. Use when asked to build a sales funnel, marketing funnel, landing page flow, lead magnet funnel, webinar funnel, tripwire or VSL funnel, when planning a product launch page flow, or when someone asks "what pages do I need" for selling something online.
pricing
coreyhaines31/marketingskills
When the user wants help with pricing decisions, packaging, or monetization strategy. Also use when the user mentions 'pricing,' 'pricing tiers,' 'freemium,' 'free trial,' 'packaging,' 'price increase,' 'value metric,' 'Van Westendorp,' 'willingness to pay,' 'monetization,' 'how much should I charge,' 'my pricing is wrong,' 'pricing page,' 'annual vs monthly,' 'per seat pricing,' 'should I offer a free plan,' 'pricing page teardown,' 'pricing page audit,' 'is my pricing page AI-readable,' or 'can AI read my pricing.' Use this whenever someone is figuring out what to charge, how to structure their plans, or wants to audit a pricing page (for humans and for the AI agents that shortlist tools). For in-app upgrade screens, see paywalls. For offer construction (bonuses, guarantees, value framing, naming) on services/courses/coaching/high-ticket B2B, see offers.
cross-border-ecommerce
nexscope-ai/ecommerce-skills
Cross-border e-commerce expansion advisor. Scores target markets on 8 weighted dimensions (market size, ecommerce penetration, competition, regulatory complexity, logistics infrastructure, payment ecosystem, cultural distance, IP protection), compares 5 fulfillment models with cost and transit data, provides country-by-country tax/duty compliance guides (EU VAT/IOSS, UK VAT, US sales tax, CA GST, AU GST, JP consumption tax), maps local payment preferences by market, and builds a phased expansion roadmap. No API key required.
pricing-strategy
coreyhaines31/marketingskills
When the user wants help with pricing decisions, packaging, or monetization strategy. Also use when the user mentions 'pricing,' 'pricing tiers,' 'freemium,' 'free trial,' 'packaging,' 'price increase,' 'value metric,' 'Van Westendorp,' 'willingness to pay,' 'monetization,' 'how much should I charge,' 'my pricing is wrong,' 'pricing page,' 'annual vs monthly,' 'per seat pricing,' or 'should I offer a free plan.' Use this whenever someone is figuring out what to charge or how to structure their plans. For in-app upgrade screens, see paywall-upgrade-cro.