sales-playbook（销售手册）

When this skill is activated, always start your first response with the 🧢 emoji.

Sales Playbook

A structured, methodology-driven approach to the full B2B sales cycle - from first touch to closed-won. This skill covers outbound prospecting, discovery, qualification, demos, objection handling, and closing. It draws from proven frameworks (MEDDIC, SPIN, Challenger) and translates them into actionable templates and decision trees an agent can apply immediately.

The core philosophy: selling is problem-solving. Every outreach, question, and response should be oriented around the buyer's pain - not your product's features.

When to use this skill

Trigger this skill when the user:

• Wants to design or improve an outbound email or LinkedIn sequence
• Needs help handling a specific sales objection
• Is preparing for a discovery or qualification call
• Wants to apply MEDDIC, BANT, or another sales framework
• Asks how to write a cold email that gets replies
• Needs help structuring a product demo
• Is trying to close a deal or enter negotiation
• Wants to build a repeatable sales process from scratch

Do NOT trigger this skill for:

• Marketing campaign strategy or paid acquisition (use a marketing skill)
• Customer success or post-sale retention (different motion, different triggers)

Key principles

1. Discovery before demo - Never pitch before you understand the problem. Run a full discovery call first. A demo presented to an unqualified prospect is a waste of both parties' time. Earn the demo by demonstrating you understand their situation.
2. Multi-thread every deal - Relying on a single champion is a single point of failure. Map the buying committee early. Build relationships with economic buyers, technical evaluators, and end users in parallel.
3. Follow up relentlessly - 80% of deals close after 5+ touches. Most reps stop at 2. A structured, value-adding follow-up sequence - not just "checking in" - is a primary differentiator between top performers and average ones.
4. Sell to pain, not features - Buyers don't care about features; they care about outcomes. Always connect capabilities to specific pains the buyer has articulated. Feature-led pitches commoditize your product.
5. Document everything in CRM - Verbal commitments evaporate. Every call insight, next step, and stakeholder detail must live in the CRM. This enables forecasting accuracy and deal handoffs without information loss.

Core concepts

Sales funnel stages

MEDDIC qualification

MEDDIC is the gold standard for enterprise deal qualification. Use it to assess deal health and identify gaps before forecasting.

• M - Metrics: What quantifiable outcome does the buyer want? (e.g., "reduce churn by 15%", "save 10 hours/week per rep"). No metrics = no business case.
• E - Economic Buyer: Who has budget authority? Have you met them? Their priorities must align with your value prop, not just your champion's.
• D - Decision Criteria: What criteria will be used to evaluate vendors? Technical fit, security, price, integration? Get this in writing if possible.
• D - Decision Process: What is the step-by-step process to get to a signed contract? Who reviews, who approves, what does legal look like, what is the timeline?
• I - Identify Pain: What is the specific, urgent, business pain? Pain that is not urgent or not quantified will not drive a deal to close.
• C - Champion: Who inside the account is selling on your behalf when you are not in the room? A champion has influence, believes in your solution, and has a personal stake in the outcome.

Buyer personas

Sales cycle anatomy

A healthy B2B sales cycle follows this arc:

1. ICP research - Firmographic + technographic fit before first touch
2. Personalized outreach - Specific trigger or insight drives the first email
3. Discovery call - 70% questions, 30% talking. Uncover MEDDIC elements.
4. Tailored demo - Show only features that address confirmed pain
5. Mutual action plan - Written timeline co-created with the buyer
6. Proposal + business case - Numbers tied to buyer's stated metrics
7. Negotiation - Anchor high, give on terms not on price, protect margin
8. Close - Ask for the order. Silence is not a close.

Common tasks

Design an outbound sequence (5-touch template)

A multi-touch outbound sequence maximizes reply rates while respecting prospect attention. Space touches 2-4 business days apart.

Key rules:

• Every touch must add value or perspective - never just "bump this up"
• Personalization is non-negotiable on touch 1; touches 3-5 can be semi-templated
• Subject lines: 3-5 words, no caps, no punctuation (e.g., quick question)
• One call to action per email - asking for a 15-minute call, not a 30-minute demo

Run a discovery call (question framework)

Discovery is the most important part of the sales cycle. Use SPIN questioning:

Situation questions (understand current state - keep brief):

• "Walk me through how your team handles [process] today."
• "What tools are you currently using for [area]?"

Problem questions (surface pain):

• "What's the biggest friction point in that workflow?"
• "How much time does your team spend on [manual task] each week?"
• "What happens when [problem] occurs? What's the downstream impact?"

Implication questions (quantify the cost of inaction):

• "If nothing changes, what does that mean for [goal] this quarter?"
• "How does that affect your team's ability to hit [metric]?"

Need-payoff questions (buyer articulates the value themselves):

• "If you could eliminate [pain], what would that mean for [goal]?"
• "How valuable would it be to get [outcome] by [timeline]?"

Call structure:

1. Set the agenda and confirm time (1 min)
2. Build rapport and context (2-3 min)
3. SPIN questions (15-20 min)
4. Summarize pain in their words (3-5 min)
5. Tease the solution and book next step (5 min)

Handle common objections (response templates)

See references/objection-handling.md for full response templates on 15+ common objections. The meta-framework for any objection:

1. Acknowledge - Validate the concern without agreeing it is a dealbreaker
2. Clarify - Ask a question to understand the real root concern
3. Respond - Address the specific objection with evidence or reframe
4. Confirm - Check that the response actually resolved the concern

Example - "Your price is too high":

• Acknowledge: "I completely understand - budget decisions are serious."
• Clarify: "Is it that the number is outside your budget, or that you're not yet seeing enough value to justify it?"
• Respond (if value gap): Walk through the ROI calculation tied to their metrics
• Confirm: "Does that help clarify the value relative to the investment?"

Qualify deals with MEDDIC

Use MEDDIC as a deal scorecard. Score each element 0-2:

• 0 = Unknown or missing
• 1 = Partially confirmed
• 2 = Fully confirmed and documented

Score 10-12: Forecast as commit. Push hard to close on timeline. Score 6-9: Upside. Identify and fill the gap elements before forecast. Score 0-5: Pipeline. Do not forecast. Focus on discovery to qualify or disqualify.

Ask these questions to fill MEDDIC gaps:

Write cold emails that get replies

The anatomy of a high-converting cold email:

Subject: [3-5 word trigger-based subject]

[Personalized first sentence - specific trigger, observation, or mutual connection]

[One-sentence problem statement - "Teams like yours often struggle with X"]

[One-sentence value proof - "We helped [similar company] achieve [specific result]"]

[Low-friction CTA - "Worth a 15-minute call this week?"]

[Name]

Rules:

• No attachments on first touch
• No "I hope this finds you well"
• No feature lists
• Maximum 100 words
• One question at the end, not three
• Preview text matters - it shows in inbox before the email is opened

Run an effective demo

A demo should be a story, not a product tour.

Structure:

1. Recap pain (2 min) - "Based on our discovery call, you said your biggest challenge is X. I want to make sure today addresses that directly."
2. Show the before state (2 min) - Illustrate the problem they described
3. The moment of change (5 min) - Show your product solving that exact problem
4. Proof / social proof (2 min) - "Here's how [similar company] used this"
5. Handle questions (10 min)
6. Next step (3 min) - Always end with a booked next step, not "let me know"

Anti-patterns:

• Never click every feature in the product
• Never say "and here you can also..." unless they asked
• Never show the admin settings panel unless the buyer is technical
• Never let the demo run over time

Close and negotiate

Closing approaches by deal stage:

• Trial close (mid-cycle): "If we could solve X and Y, would that be enough to move forward?" - Tests commitment without asking for the order.
• Assumptive close (late-cycle): "Let me send over the contract for your review. Do you prefer DocuSign or PDF?" - Assumes the yes.
• Summary close: Recap the pain they shared, the value you demonstrated, and ask directly: "Based on everything we've discussed, are you ready to move forward?"

Negotiation principles:

• Anchor first - your first number sets the range
• Never discount without getting something in return (longer term, faster close, reference, case study)
• Protect unit price - offer add-ons or volume instead of rate cuts
• Create urgency legitimately: end-of-quarter pricing, limited onboarding slots, or timeline tied to their stated deadline

Gotchas

1. Multi-threading too late - Waiting until the deal is advanced to map the buying committee means you discover unknown stakeholders during legal review, not discovery. Map the buying committee in meeting two, not meeting eight.
2. MEDDIC without Metrics kills forecasting - Deals scored as "commit" without a confirmed, quantified metric (not just "they want to reduce costs") are systematically overforecast. Treat no Metrics as a discovery task, not a pass.
3. Break-up emails trigger no-reply ghosting - A break-up email sent before the prospect is warm signals desperation and gets archived. Only send touch 5 (break-up) if you have had at least one reply or engagement from them first.
4. Assumptive close on unqualified deals backfires - Using closing language before the economic buyer has been engaged causes prospects to go cold or loop in a new stakeholder who restarts the process. Run trial closes first.
5. Discounting to beat a deadline creates a pattern - A one-time end-of-quarter discount trains the buyer (and their colleagues) to wait for discounts every cycle. Link urgency to a legitimate business reason (implementation timeline, their stated deadline) rather than your quota.

Anti-patterns

References

For detailed content on specific objections and responses, load the relevant file:

• references/objection-handling.md - Response templates for 15+ common objections including price, timing, competition, and stakeholder concerns

Only load the references file when the current task requires specific objection response language or detailed scripts.

Companion check

On first activation of this skill in a conversation: check which companion skills are installed by running ls ~/.claude/skills/ ~/.agent/skills/ ~/.agents/skills/.claude/skills/.agent/skills/.agents/skills/ 2>/dev/null. Compare the results against the recommended_skills field in this file's frontmatter. For any that are missing, mention them once and offer to install: `` npx skills add AbsolutelySkilled/AbsolutelySkilled --skill <name> ` Skip entirely if recommended_skills` is empty or all companions are already installed.