Claude Skills for SaaS: The Complete Revenue Playbook

Every Claude skill in this playbook maps to one revenue problem SaaS teams actually have.

Install commands, full SKILL.md files, and copy-paste prompts throughout.

Works with Claude Code, Cursor, Codex CLI, Gemini CLI, and any harness that reads SKILL.md files.

How to install any skill

# Method 1: Plugin marketplace (automatic loading)
/plugin install [plugin-name]

# Method 2: Copy to skills directory
cp -r skills/[skill-folder]/* ~/.claude/skills/

# Method 3: Reference inline in any prompt
"Using the [skill-name] skill, help me [task]"

Skills index

Category	Skills
ICP and Positioning	startup-icp-definer, icp-enrichment, value-proposition, competitive-intel
Prospecting	sales-prospect, lead-qualification, account-tiering, sales-research
Outbound and Email	cold-email-sequence-generator, cold-outreach-generator, outbound-sequences, outbound-plays, outbound-optimizer, gtm-outbound
Discovery and Sales	sales-discovery, founder-sales, enterprise-sales, sales-qualification, product-led-sales
Pipeline and Revenue	sales-pipeline, sales-close, sales-objection, sales-follow-up, sales-compensation
Customer Success	onboarding-playbook, csm-qbr, churn-risk, expansion-playbook
Content and Enablement	email-sequence, email-template-generator, sales-deck, battle-card, case-study-generator
RevOps	crm-hygiene, forecasting, territory-planning, sales-reporting
Team and Hiring	building-sales-team, sdr-coaching, sales-onboarding, interview-scorecard

Before you build sequences, write copy, or hire reps, you need a precise ICP and a positioning that earns attention in the first line.

These skills wire your ICP and value prop into every downstream skill automatically.

startup-icp-definer

Interviews you to define your ICP. Outputs a structured ICP document that feeds into every outbound skill.

"Define my ICP. Ask me one question at a time about:
1. Company size range (employees or revenue)
2. Industry and company type (SaaS / agency / B2B services)
3. Tech stack signals (what tools do my best customers use before buying me?)
4. Buying triggers (what events precede a purchase: funding, hiring, product launch?)
5. Pain points by role (what does the decision maker complain about?)
6. Disqualifiers (who looks right but never converts?)

Output a structured ICP document with:
- Firmographics (size, industry, geography, stage)
- Psychographics (what they care about, what they fear)
- Pain points mapped to role
- Buying triggers ranked by conversion rate
- Decision-maker map (buyer, influencer, blocker)

Save to CLAUDE.md when done."

value-proposition

Builds a value proposition that holds up in the first line of a cold email and the first 30 seconds of a call.

"Build my value proposition for [ICP ROLE] at [COMPANY TYPE].

My product: [DESCRIBE]
Best customer outcome: [SPECIFIC RESULT WITH NUMBER]
Why us over the alternative: [SPECIFIC DIFFERENTIATOR]

Output:
1. One-sentence value prop (under 15 words, outcome-first)
2. Three-sentence version for email body
3. 30-second spoken version for calls
4. Versions for each seniority tier: C-suite / Director / Manager / IC

Rules: no em dashes, no jargon, no adjectives without numbers behind them."

competitive-intel

Builds a competitive intelligence brief and battle card for any competitor.

"Build a competitive brief for [COMPETITOR NAME].

My product: [DESCRIBE]
Audience: my sales team preparing for deals where [COMPETITOR] comes up

Cover:
1. What [COMPETITOR] does well (be honest)
2. Where they fall short (with evidence: G2 reviews, customer complaints, job postings)
3. The two scenarios where we win and why
4. The two scenarios where they win and what to do about it
5. The questions to ask a prospect that reveal which scenario we are in
6. The one-liner to use when their name comes up on a call

Sources to check: G2, Capterra, Reddit, their job postings, their changelog."

Find the right companies, the right people, and the right signal before writing a single word of outreach.

Bad lists waste good copy. These skills build lists worth running.

sales-prospect (full SKILL.md)

# SKILL: sales-prospect

### When to use
- Building a target account list from scratch
- Refining an existing list against a defined ICP
- Identifying the right contact within a target account

### Input required
- ICP definition (from CLAUDE.md or described inline)
- Target volume
- Tools available (Apollo, Clay, Sales Navigator, LinkedIn)
- Geography

### What it does
1. Translates the ICP into specific filters for your available tool
2. Identifies the right title and seniority tier to target
3. Returns the specific searches to run in Apollo or Sales Navigator
4. Identifies the one signal that most reliably indicates buying intent for this ICP
5. Flags accounts to prioritise based on signal strength

### Output format
- Tool-ready filter strings for Apollo / Sales Nav
- Buying signal definition: what to look for and where
- Sample list of 10 accounts with prioritisation score
- The one outreach trigger to watch for each account

Copy-paste prompt:

/sales-prospect

Build a prospect list for outbound.

ICP:
- Title: [TARGET TITLES]
- Function: [owns or influences what?]
- Company type: [SaaS / agency / B2B services]
- Company size: [employee range]
- Geography: [regions]

Volume: [N] contacts
Tools available: [Apollo / Clay / Sales Navigator]

Return:
- ICP definition in filter-ready format
- Sourcing strategy with specific searches to run
- The one signal that most reliably indicates buying intent
- Top 10 accounts to start with ranked by signal strength

lead-qualification (full SKILL.md)

# SKILL: lead-qualification

### When to use
- Qualifying inbound leads before booking a call
- Scoring an outbound list before running a sequence
- Training SDRs on qualification criteria

### The one qualification question
Is this person responsible for generating revenue or building GTM systems at their company?
If yes: proceed. If no: skip.

### Who to qualify
- Role: Director, Founder, Owner, Manager, or C-suite
- Company type: SaaS, B2B, or agency
- Function: owns or influences outbound, lead gen, or GTM
- Status: actively employed or running a company (not open to work)

### Who to skip
- Job seekers (open to work badge)
- Pure IC contributors with no GTM responsibility
- Students or hobbyists
- Roles with no revenue influence

### Qualification tiers
Tier 1 (contact immediately):
- Title matches exactly (VP Sales, Head of Marketing, Founder, RevOps Director)
- Company in ICP range
- Active signal in last 30 days

Tier 2 (contact within 3 days):
- Adjacent title (Sales Manager, Marketing Manager, Growth Lead)
- Company type matches, size unclear
- No recent signal but profile clearly in ICP

Tier 3 (contact if capacity allows):
- Partial ICP match
- GTM influence is unclear
- Include a qualifying question in outreach

### Discovery questions that qualify while building rapport
1. Who owns outbound at your company right now?
2. What does your current lead gen motion look like?
3. How many people are on the sales or marketing team?
4. Who decides on new tools in the GTM stack?

sales-research (full SKILL.md)

# SKILL: sales-research

### When to use
- Preparing for any outbound touch
- Pre-call research for discovery or demo
- Account expansion research for CS

### What it does
1. Pulls what the company does and who they sell to
2. Finds signals from the last 90 days (funding, hiring, leadership changes, product launches)
3. Identifies the pain most relevant to your offer
4. Names the right entry point: who to contact and why
5. Returns three opening angles ranked by likely reply rate

Copy-paste prompt:

/sales-research

Build a full account research brief for [COMPANY NAME].

Include:
- What they do and who they sell to (one paragraph)
- Signals from last 90 days: funding, hiring, leadership changes, product launches
- The one pain most relevant to my offer: [describe offer in one sentence]
- Right entry point: who to contact and why
- Three opening angles ranked by likely reply rate

Sources: Firecrawl for the website, Exa for recent news, LinkedIn for org structure.
Under 400 words. I am reading this before making contact.

account-tiering

"Build an account tiering model for my ABM list.

Accounts: [PASTE LIST or describe the universe]
My ICP from CLAUDE.md: [reference]
My offer: [one sentence]

Tier accounts into:
- Tier 1 (top 20%): highest ICP fit + active signal + accessible contact
- Full personalisation. Named account plan. CEO-level outreach if needed.
- Tier 2 (next 30%): strong ICP fit, no signal yet
- Semi-personalised. Use their industry and company size as context.
- Tier 3 (remaining 50%): partial ICP match or unclear
- Template-based outreach. Qualify through the sequence.

For each tier: outreach approach, touchpoint volume, and the one thing to learn before contacting."

Every outbound skill below is copy-paste ready. They read CLAUDE.md for your ICP and voice.

Rules applied across all: no em dashes, no banned words, peer-level tone, one CTA per touch.

cold-email-sequence-generator

"Write a [3 / 5 / 7]-touch cold email sequence.

Prospect: [TITLE] at [COMPANY TYPE]
Pain point: [THE ONE PAIN THIS ICP HAS]
Signal: [BUYING SIGNAL if any: funding / hiring / competitor / tech change]
Offer: [what you sell in one sentence]

For each touch:
- Subject line (2-4 words, no question marks, looks internal)
- Email body
- Send day (Day 1, 4, 9, 16, 25, 35)
- Different angle per touch (no repetition)

Rules:
- Touch 1: signal-led opener, under 150 words, one question as CTA
- Touches 2-4: different pain angle each time
- Touch 5+: breakup email with referral ask
- No em dashes, no jargon (leverage/synergy/streamline/unlock)
- Sound like a peer, not a vendor
- Load directly into Instantly, Smartlead, or Salesforge"

cold-outreach-generator (signal-led variants)

# Job change signal
"Write 3 cold email variants for a prospect who just started as [TITLE] at [COMPANY].
Signal: new role, likely in evaluation mode for [CATEGORY OF TOOLS].
Offer: [one sentence].
Rules: reference the new role in opener without naming their LinkedIn profile. Under 100 words. One question CTA."

# Funding signal
"Write 3 cold email variants for [TITLE] at [COMPANY] who just announced a [ROUND] round.
Angle: what the round means for their [SALES/MARKETING/GROWTH] function specifically.
Offer: [one sentence]. Under 100 words. Opener does not say congratulations."

# Hiring signal
"[COMPANY] just posted [ROLE]. Write 3 cold emails for [TITLE] at [COMPANY].
Angle: what hiring [ROLE] implies about their current gap.
Offer: [one sentence]. Under 100 words. Reference the hiring without naming the job posting directly."

# Competitor signal
"[PROSPECT] is using [COMPETITOR]. Write 3 cold emails.
Angle: what [COMPETITOR] does not do well for [ICP TYPE] (reference G2 or known limitations).
Do not name the competitor in the subject line. Under 100 words."

outbound-optimizer

"Audit this sequence and tell me why it is underperforming.

[PASTE FULL SEQUENCE COPY]

Metrics:
- Open rate: [N%]
- Reply rate: [N%]
- Positive reply rate: [N%]

Diagnose:
1. Is the open rate problem the subject line or deliverability?
2. Is the reply rate problem the hook, the offer, or the CTA?
3. Which touch has the highest drop-off?
4. What is the one change most likely to move positive reply rate above 2%?

Return rewritten versions of the two weakest touches. Test these before rebuilding the full sequence."

outbound-plays (scenario playbooks)

# Event attendee play
"Build an outbound play for attendees of [EVENT NAME].
List size: [N]. My presence at the event: [attending / speaking / exhibiting / not there].
Output: pre-event outreach (invite to meet), day-of message, post-event follow-up sequence.
Personalisation anchor: the session they attended or the theme of the event."

# Competitor displacement play
"Build a competitor displacement play targeting [COMPETITOR] customers.
List source: G2 reviewers, LinkedIn followers of [COMPETITOR], or job postings mentioning [COMPETITOR].
Angle: what [COMPETITOR] users consistently complain about.
Sequence: 4 touches, different angle per touch. First touch: no pitch, just insight."

# Product-led expansion play
"Build a PLS expansion play for free or trial users who hit [USAGE TRIGGER].
Trigger: [DESCRIBE THE PRODUCT EVENT: e.g. 5+ sessions in 7 days, invited a teammate, exported data].
Sequence: 3-touch email + in-app message + CS call if no reply.
Goal: convert to paid within [N] days."

gtm-outbound

"Build a full outbound GTM strategy for [PRODUCT].

ICP: [FROM CLAUDE.md or describe here]
Team size: [N reps]
Pipeline target: [$N per month]
Current conversion rates: [describe if known, or skip]

Output:
- Channel allocation (email / LinkedIn / phone / other) with rationale
- Weekly send volume targets per channel
- ICP priority tiers and which tier gets which level of personalisation
- Full sequencing logic: number of touches, cadence, channel per touch
- The 3 signals to prioritise and what to do when each fires

Use this as the brief for building individual sequences in cold-email-sequence-generator."

Full SKILL.md files for discovery, qualification, and the founder-to-founder sales motion.

These skills make every call better, not just the first one.

discovery-calls (full SKILL.md)

# SKILL: discovery-calls

### Call structure (30 minutes)

Minutes 0-5: Set the agenda
- Restate the goal of the call from their perspective, not yours
- Confirm the time and agenda
- Ask if anything has changed since scheduling

Minutes 5-20: Discovery
- Use the question framework below
- Follow their answers, do not stick to a script
- Goal: get them to describe their problem in their own words

Minutes 20-25: Confirm the pain
- Restate what they said using their exact words
- Ask: "Is that right? Am I missing anything?"
- Do not skip this step. If you do, the follow-up will be generic.

Minutes 25-30: Define the next step
- A next step is a specific action with a specific date, agreed by both parties
- "I'll send you some info" is not a next step
- "I'll send the case study by Thursday and we'll talk again on the 15th" is a next step

### Question framework

Situation questions:
- What does your current [relevant process] look like?
- Who owns [the problem area] today?
- How long have you been doing it this way?

Problem questions:
- What is the biggest frustration with how things work today?
- What would you change if you could change one thing?
- What has the cost of this problem been for the business?

Implication questions:
- What happens if this does not get solved in the next 6 months?
- How is this affecting other parts of the team?
- Has this come up in conversation with leadership?

Need-payoff questions:
- If you solved this, what would that mean for you personally?
- What would a good outcome look like from your perspective?
- How would you measure whether a solution actually worked?

### After the call: capture immediately
- Their pain in their exact words
- Decision process (who else, what does approval look like)
- Timeline (is there a forcing function?)
- What they said they need to see next
- The agreed next step with a specific date

Copy-paste prompt:

"Prep me for a discovery call with [NAME], [TITLE] at [COMPANY].

Context: [how we met / what they responded to]
What I know about them: [paste any research]
My offer: [one sentence]

Return:
- 5 discovery questions tailored to their specific situation (not generic)
- The one pain they most likely have based on their role and company
- 2 objections they will probably raise and how to handle each
- The specific next step to aim for at the end of this call
- What I should NOT say (common mistakes for this persona)"

founder-sales

"Give me a discovery call framework for selling [PRODUCT] to [ROLE] at [COMPANY TYPE].

Context: I am the founder doing my own sales. Average deal: [$N]. Stage: [SEED / SERIES A / SERIES B].

Return:
- Discovery question sequence (8-10 questions in order)
- Objection-handling scripts for the 3 most common objections I face: [list them]
- Deal progression criteria: what has to be true for a deal to move from discovery to demo?
- Close talk track: what do I say when it is time to ask for the decision?
- How to run the call when I am also the product expert (common founder trap: teaching instead of selling)"

# Founder cold email
"Write a founder-to-founder cold email from me to [TARGET FOUNDER / CEO].
My company: [DESCRIBE]. Their company: [DESCRIBE].
Angle: peer outreach, not vendor pitch. I am not selling yet. I am opening a conversation.
Under 80 words. Subject line: [FIRST NAME, 2-3 words max]. One soft ask at the end."

enterprise-sales

"Build an enterprise sales strategy for [DEAL / ACCOUNT].

Stakeholders: [LIST WHO IS INVOLVED]
Champion: [NAME / ROLE]
Blocker: [NAME / ROLE and what they care about]
Business case needed: [what justification does procurement need?]
Timeline: [when does this need to close?]

Return:
- Stakeholder engagement plan (who to contact in what order and with what message)
- Champion enablement: what content to give our champion to sell internally
- Procurement response templates for the most likely procurement questions
- Deal progression milestones: what has to happen in the next 30 / 60 / 90 days
- The one thing most likely to kill this deal and how to prevent it"

# Multi-threaded outreach
"Build a multi-threading strategy for [ACCOUNT].
Current contact: [NAME / ROLE]. I need to add [N] more stakeholders.
Return: who to add, why, in what order, and the outreach message for each person that does not undermine my existing relationship."

sales-qualification

"Build a qualification framework for [PRODUCT] using [MEDDIC / BANT / custom].

ICP: [FROM CLAUDE.md]
Average deal size: [$N]

Return:
- Scoring criteria per MEDDIC field (0-10 per field, threshold for SQL status)
- The 5 discovery questions that reveal qualification fastest
- What a qualified deal looks like at each stage of the pipeline
- Disqualification criteria: what makes a deal not worth pursuing regardless of size
- CRM fields to add for tracking (field name, type, options)"

# MEDDIC scoring sheet
"Score this deal against MEDDIC.

Deal: [COMPANY]
What I know:
- Metrics: [what business outcome they are measuring]
- Economic buyer: [who approves budget]
- Decision criteria: [what they say they are evaluating on]
- Decision process: [steps, timeline, who is involved]
- Identify pain: [what they said the problem is]
- Champion: [who is pushing for this internally]

Return: score 0-10 per field, total score, and the one thing most likely to kill this deal."

Objection handling, pipeline management, and closing skills with full copy-paste prompts.

objection-handling (full SKILL.md)

# SKILL: objection-handling

### The 5 most common SaaS objections

#### 1. "We already have something for this"
What they mean: I do not want another vendor conversation or change management.
Call: "Totally fair. Out of curiosity, what are you using and is it covering everything you need? Teams I talk to often have something in place but have specific gaps that show up over time."
Email: "Makes sense. Most teams we work with had something before us. The question is whether it is covering [specific gap relevant to their profile]. Worth a quick check?"

#### 2. "We are not ready right now"
What they mean: Not a priority, or there is a budget constraint they have not shared.
Call: "No problem. When you say not ready, is that a timing thing or a priority thing? Helps me know whether to check back in 3 months or whether something specific would need to change first."
Email: "Understood. When you say not ready, is that a timing issue or something that needs to change internally first? I want to make sure when I check back it is actually useful."

#### 3. "Your price is too high"
What they mean: I do not yet see enough value to justify the cost.
Call: "Let me ask: is it the absolute number that is the issue, or is it more that the value relative to the cost is not clear yet? Those are two different problems and I want to make sure I address the right one."
Email: "Fair point. Price is always relative to value. Let me show you what teams like yours get from it and you can decide if the math makes sense. Worth a 15-minute walkthrough?"

#### 4. "I need to talk to my team"
What they mean: Not the decision maker, or not yet convinced enough to champion this.
Call: "Of course. Who else would be part of the conversation? I want to make sure you have what you need to bring it to them: one-pager, case study, or something else?"
Email: "Makes sense. What would help most for when you bring it to your team: a one-pager, a short demo recording, or a case study from a similar company?"

#### 5. "We are in a budget freeze"
What they mean: Budget is constrained, or this is not a priority worth fighting for budget.
Call: "Completely understand. Is the freeze across the board or are specific budget lines still moving? Some teams in this situation have moved things under a different cost centre or found room in Q4 budget."
Email: "Understood. When does your freeze lift? I will circle back at the right time with something relevant to where you are then."

### When to push and when to let go
Push: when the objection is a reason, not a decision. Questions reveal reasons.
Let go: when they have given you three reasons and shown no curiosity about your response.

Copy-paste prompt:

"Handle this objection: '[PASTE OBJECTION]'

Context: [stage of sale, what they said before this, what I offered]
My offer: [one sentence]

Return:
- What they likely mean behind the words
- The question to ask to surface the real concern
- A 30-second call response
- An email follow-up version under 80 words
- Whether to push or let go based on this objection"

sales-pipeline

/sales-pipeline

Run a pipeline health check.

[PASTE PIPELINE DATA or describe deals]

For each deal, flag:
- No activity in 7+ days
- No defined next step with a date
- Close date passed with no update
- Wrong stakeholder (not talking to the decision maker)

Diagnose root cause per flagged deal:
bad ICP fit / wrong stakeholder / no confirmed pain / price / timing / competitor

Return:
- Top 5 deals to focus on this week
- Top 3 deals to consider dropping
- Exact next action per priority deal: who to contact, what to say, what to ask for

sales-close

"Build a closing strategy for [DEAL].

Situation:
- Stage: [where we are]
- Decision maker: [confirmed / not confirmed]
- Timeline: [their timeline vs our timeline]
- Blockers remaining: [list them]
- Champion strength: [strong / weak / unknown]

Return:
- The one question that reveals whether they are actually going to close
- A mutual action plan for the next 14 days
- How to create urgency without discount: [forcing function or event we can tie to]
- The close ask: exact words to use when asking for the decision
- If they go dark: the re-engagement sequence (3 touches over 3 weeks)"

sales-compensation

"Design a sales comp plan for a [ROLE: AE / SDR / CSM] at a [STAGE] SaaS company.

Inputs:
- OTE budget: [$N]
- Average deal size / ACV: [$N]
- Quota attainment target: [N% of reps at or above quota]
- Individual vs team incentives: [preference]

Return:
- Base / variable split recommendation with rationale
- Quota number and how you got there
- Accelerator structure above quota (thresholds and multipliers)
- SPIF recommendations for Q4 or specific objectives
- Model showing payouts at 50 / 75 / 100 / 125% attainment
- The one thing that will cause reps to game this plan (and how to prevent it)"

Skills for retaining and growing the revenue you have already closed.

Churn is the most expensive problem in SaaS. These skills catch it before it happens.

onboarding-playbook

"Build a customer onboarding playbook for [PRODUCT].

Customer type: [COMPANY SIZE / TYPE]
Time to value target: [N days from sign to first meaningful outcome]
Key onboarding milestone: [what does done look like at day 7 / 14 / 30?]

Return:
- Week 1 onboarding flow (what happens, who owns it, what success looks like)
- The 3 questions to ask in the kickoff call (that predict whether they will succeed)
- The one in-product action that predicts long-term retention (the activation event)
- Automated touchpoints vs human touchpoints: what to automate and what needs a person
- Early warning signs that onboarding is failing and what to do when you see them"

churn-risk

"Build a churn risk model for my SaaS product.

Product: [DESCRIBE]
Customer size: [SMB / mid-market / enterprise]
Current churn rate: [N% monthly or annual]

Return:
- The 5 product signals that predict churn 30-60 days before it happens
- The 3 non-product signals (contract stage, NPS, support tickets, stakeholder change)
- A health score formula using these signals (weighted 0-100)
- What to do when a customer hits health score below 60
- The save play: what to say, who says it, and what you can offer without devaluing the product"

# Churn risk review
"Review these customers and flag which ones are at risk of churning.

[PASTE CUSTOMER DATA: usage, NPS, last contact, contract date]

For each flagged customer:
- Risk level (high / medium / low)
- The specific signal that flagged them
- Recommended action: who reaches out, what they say, what they offer"

expansion-playbook

"Build an expansion playbook for [PRODUCT].

Expansion motion: [seat expansion / usage-based / upsell to higher tier / cross-sell]
Current customers: [describe the base]
Average expansion deal: [$N]

Return:
- The product usage signals that predict expansion readiness
- The expansion conversation: when to have it and what triggers the ask
- The talk track for a CSM-led expansion call (not a sales call)
- How to involve the AE without making the customer feel re-sold
- Expansion email templates: 3 variants for the moment when the signal fires"

csm-qbr

"Prep a QBR for [CUSTOMER NAME], [COMPANY].

Context:
- Contract value: [$N]
- Contract renewal date: [DATE]
- Usage last quarter: [describe or paste metrics]
- NPS / satisfaction: [score or description]
- Open support issues: [list if any]
- Expansion opportunity: [describe if any]

Return:
- QBR agenda (30-minute format)
- The 3 success metrics to lead with (their outcomes, not our product features)
- How to bring up renewal without it feeling like a sales call
- If there is churn risk: how to address it directly before they do
- The expansion ask: how to introduce it at the right moment if the relationship is healthy"

CRM hygiene, forecasting, territory planning, and reporting skills.

The infrastructure that makes every other skill more reliable.

crm-hygiene

"Run a CRM hygiene audit.

CRM data: [PASTE EXPORT or describe the issues]

Find and fix:
- Contacts without a company association
- Deals with no activity in 14+ days
- Deals with no next step or a next step date in the past
- Duplicate company records
- Contacts who have left their company (use LinkedIn or Exa to verify)
- Stage mismatches (deal in 'proposal sent' with no proposal activity logged)

Return:
- List of specific records to fix with what fix is needed
- The 5 CRM fields most commonly left empty (and why they matter)
- A weekly hygiene checklist for reps"

forecasting

"Build a sales forecast for [MONTH / QUARTER].

Pipeline:
[PASTE DEAL LIST with stage, amount, close date, and probability]

Return:
- Commit forecast (high confidence, >80% probability)
- Best case forecast (if everything goes right)
- The 3 deals most likely to slip and why
- Coverage ratio: do we have enough pipeline to hit target?
- The one thing that would most improve forecast accuracy in our pipeline"

# Forecast call prep
"Prep me for a forecast call.

Target: [$N]
Current commit: [$N]
Gap: [$N]

For each deal in the gap:
- Is the close date realistic?
- What is the single next action that would most move this forward?
- Should this stay in the forecast or move out?"

sales-reporting

"Build a weekly sales report for [TEAM / INDIVIDUAL].

Period: [WEEK OF DATE]
Data: [PASTE CRM EXPORT or describe]

Return:
- Pipeline created this week vs last week
- Deals closed won and lost
- Activities: calls, emails, LinkedIn touches logged
- Stage conversion rates: where are deals getting stuck?
- The one pattern in this week's data worth discussing in the team meeting"

# Board-ready metrics
"Build a board-ready metrics summary for [MONTH / QUARTER].

Return:
- New ARR vs target
- Churn ARR
- Net new ARR
- Pipeline coverage ratio
- CAC payback period (if data available)
- Cohort retention chart description (Month 1, 3, 6, 12)
- The 3 things that went well and the 1 thing that did not"

territory-planning

"Build a territory plan for [REP NAME or TEAM].

Territory: [GEOGRAPHY / VERTICAL / COMPANY SIZE]
Target: [$N new ARR this quarter]
Rep capacity: [N hours per week for outbound]

Return:
- Total addressable accounts in territory (estimate with sources)
- Priority tier breakdown: how many Tier 1 / 2 / 3 accounts
- Weekly activity targets by tier (calls, emails, LinkedIn touches)
- The top 10 accounts to focus on this quarter and why
- Whitespace analysis: which segments in this territory are underpenetrated?"

Hiring, onboarding, and coaching skills for building the revenue team.

building-sales-team

"Help me structure and hire my first [2 / 5 / 10]-person sales team.

Context:
- Current ARR: [$N]
- Average deal size: [$N]
- Sales motion: [inbound / outbound / PLG / hybrid]
- Founder bandwidth for sales: [hours per week]

Return:
- Team structure (who first and why: AE vs SDR vs CS)
- Hire sequence with rationale
- Job description draft for the first hire
- Interview scorecard: what to test for and how
- 30-60-90 day ramp plan for each role
- The one mistake founders make when hiring their first sales rep (and how to avoid it)"

sdr-coaching

"Audit this SDR's outreach and give me one coaching priority.

[PASTE LAST 10 CONNECTION NOTES AND LAST 10 EMAILS]

For each message:
- Does it reference something specific or is it generic?
- Does it sound like a peer or a vendor?
- Is the CTA appropriate for the stage?
- Any rule violations: generic opener, pitch in first message, em dash?

Return:
- Pass/fail per message
- The one coaching priority for this rep this week
- Rewritten version of their weakest message"

# SDR daily review
"Build a daily SDR activity review template.

Metrics to track per rep per day:
- Connection requests sent
- Emails sent
- LinkedIn comments left
- Positive replies received
- Calls booked

Also flag: any rep below [N] activities or above [N] activities (both are problems).
Return a 5-minute daily standup format using these metrics."

product-led-sales

"Build a product-led sales motion for our [FREE TIER / TRIAL] product.

Product: [DESCRIBE]
PQL definition: [describe or ask me to define it]
Team: [sales-assisted or fully automated?]

Return:
- PQL trigger logic: what usage event(s) define a product-qualified lead
- The outreach sequence that fires when a user hits PQL status
  (touch 1: in-app message, touch 2: email, touch 3: call if ACV justifies it)
- The sales play for converting PQLs: what to say, what not to say
- How to implement PQL triggers in [PostHog / Amplitude / Mixpanel]
- The one mistake PLS teams make (treating PQLs like cold outbound)"

All copy-paste prompts from every section in one place.

Model: claude-sonnet-5 at medium effort for most. Opus 4.8 for complex multi-step planning.

ICP and positioning

# Build ICP
"Define my ICP. Ask me one question at a time. Save to CLAUDE.md."

# Build value prop
"Build my value proposition for [ICP ROLE] at [COMPANY TYPE]. Outcome-first. Under 15 words for the one-liner. No em dashes."

# Competitive intel
"Build a competitive brief for [COMPETITOR]. Focus on what they do not do well for [ICP TYPE]. Use G2 and job postings as evidence."

Prospecting

# Prospect list
/sales-prospect
ICP: [TITLES / COMPANY TYPE / SIZE / GEO]
Tools: [Apollo / Clay / Sales Nav]
Volume: [N]

# Research brief
/sales-research
Company: [NAME]. My offer: [ONE SENTENCE]. Under 400 words. Three opening angles.

# Account tiering
"Tier these [N] accounts into Tier 1/2/3 based on my ICP and signal data."

Outbound

# Cold email sequence
"Write a [5]-touch cold email sequence for [TITLE] at [COMPANY TYPE]. Signal: [DESCRIBE]. Offer: [ONE SENTENCE]. Different angle per touch. No em dashes."

# Signal-led variants
"Write 3 cold email variants for a prospect who just [JOB CHANGE / RAISED FUNDING / IS HIRING / USES COMPETITOR]. Angle: [WHAT THE SIGNAL IMPLIES]. Under 100 words. One question CTA."

# Sequence audit
"Audit this sequence. Metrics: open rate [N%], reply rate [N%], positive reply [N%]. Diagnose the failure point and rewrite the two weakest touches."

Discovery and sales

# Call prep
"Prep me for a discovery call with [NAME], [TITLE] at [COMPANY]. 5 tailored questions. Their most likely pain. 2 objections and how to handle them. Specific next step to close on."

# Objection handling
"Handle this objection: '[PASTE]'. What they really mean. Call response under 30 seconds. Email version under 80 words. Push or let go?"

# MEDDIC scoring
"Score this deal against MEDDIC. [PASTE WHAT YOU KNOW]. Score 0-10 per field. Total score. The one thing most likely to kill this deal."

Pipeline and CS

# Pipeline health
/sales-pipeline
[PASTE PIPELINE]. Flag stalled deals. Top 5 to focus. Top 3 to drop. Next action per priority deal.

# Churn risk
"Review these customers and flag churn risk. [PASTE DATA]. Risk level per customer. The specific signal. Recommended action."

# QBR prep
"Prep a QBR for [CUSTOMER]. Contract: [$N]. Renewal: [DATE]. Usage: [DESCRIBE]. The 3 success metrics to lead with. How to bring up renewal. Expansion ask if relationship is healthy."

RevOps and team

# CRM hygiene
"Run a CRM hygiene audit on [PASTE DATA]. Flag stalled deals, missing next steps, duplicates. Weekly checklist for reps."

# Forecast
"Build a sales forecast for [PERIOD]. [PASTE PIPELINE]. Commit / best case / deals most likely to slip / coverage ratio."

# First sales hire
"Help me structure and hire my first [N]-person sales team. ARR: [$N]. Deal size: [$N]. Motion: [outbound]. Sequence, JD, scorecard, ramp plan."