菜单
Build from founder-led selling to scalable sales engine—match methodology to situation with MEDDIC for enterprise, BANT for SMB, and Challenger for differentiated products. Cold outreach sequences with specific timing and target metrics. Use when designing sales processes, writing outreach, or scaling from founder-led to team-led sales.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | sales |
| description | Build from founder-led selling to scalable sales engine—match methodology to situation with MEDDIC for enterprise, BANT for SMB, and Challenger for differentiated products. Cold outreach sequences with specific timing and target metrics. Use when designing sales processes, writing outreach, or scaling from founder-led to team-led sales. |
Sales isn't convincing people to buy something they don't want. It's finding people who already have the problem and showing them a better path.
Stage 1: Founder closes every deal (0-10 customers)
→ Learn the sales motion, objections, and buying triggers
Stage 2: Founder + first hire (10-30 customers)
→ Document the playbook, hire someone to run it
Stage 3: Small team with process (30-100 customers)
→ Repeatable pipeline, CRM discipline, weekly metrics
Stage 4: Scalable engine (100+ customers)
→ Specialized roles (SDR, AE, CS), quota-based management
| Situation | Methodology | Why |
|---|---|---|
| Complex enterprise, $50K+ ACV | MEDDIC | Multiple stakeholders, long cycles need qualification rigor |
| Quick SMB qualification, < $10K ACV | BANT | Fast yes/no decision on whether to pursue |
| Differentiated product, new category | Challenger | You need to teach buyers why the status quo is risky |
| Transactional, high volume | SPIN | Surface pain through questions, move fast |
M — Metrics: What's the measurable impact of solving this?
E — Economic Buyer: Who signs the check?
D — Decision Criteria: What are they evaluating on?
D — Decision Process: What are the steps to close?
I — Identify Pain: What specific pain drives this purchase?
C — Champion: Who inside will fight for you?
B — Budget: Do they have money allocated?
A — Authority: Am I talking to the decision maker?
N — Need: Is the pain urgent enough to act?
T — Timeline: When do they need this solved?
Disqualify fast: If 2+ are missing, move on.
1. Teach — Share an insight they didn't know about their problem
2. Tailor — Connect the insight to their specific situation
3. Take control — Guide the buying process, don't be passive
Day 1: Pain-based opener (no pitch)
Subject: "[Specific pain point] at [Company]?"
Body: 2-3 sentences about the problem. One question.
Day 3: Value proof
Subject: Re: [previous subject]
Body: "Company X solved this and saw [result]. Here's how."
Day 7: Different angle
Subject: New subject line, different pain point or persona
Body: Brief case study or metric. Soft CTA.
Day 10: Breakup preview
Subject: "Should I close your file?"
Body: "Seems like timing isn't right. Wanted to check before I stop reaching out."
Day 14: Breakup
Subject: "Closing the loop"
Body: "Moving on, but here's [resource] in case it's helpful later."
| Metric | Target | Red Flag |
|---|---|---|
| Open rate | 40-60% | < 25% (subject lines need work) |
| Reply rate | 8-15% | < 5% (messaging or targeting issue) |
| Meeting booked rate | 3-5% of sequence | < 1% (revisit ICP or value prop) |
| Show rate | 80%+ | < 60% (confirmation flow broken) |
Day 0: View their profile
Day 1: Connect request (no note or very brief note)
Day 3: After connection, send a relevant insight (not a pitch)
Day 7: Share content relevant to their challenge
Day 10: Soft ask for conversation
Stage → Criteria to advance → Probability
Prospecting → Identified as ICP match → 10%
Discovery → Pain confirmed, stakeholder → 20%
Evaluation → Demo given, criteria met → 40%
Proposal → Pricing delivered → 60%
Negotiation → Terms under discussion → 80%
Closed Won → Signed → 100%
| Sales Theater | Real Sales |
|---|---|
| "Let me show you our features" | "Tell me about [their problem]" |
| Pitching in the first email | Leading with insight or a question |
| "Following up" with no new value | Each touch adds a new angle or proof point |
| No CRM, deals in your head | Every deal tracked with stage and next action |
| Discounting to close | Selling value, walking away if fit isn't there |
"Design a complete outbound sequence for [ICP] selling [product at $X ACV]. Choose the right methodology (MEDDIC, BANT, or Challenger), write the 5-email sequence, define pipeline stages, and set the target metrics I should track weekly."
The agent becomes your sales architect — building a repeatable process, not just individual pitches.
Create, update, close, and report on Jira tickets. Reads JIRA_URL and JIRA_TOKEN from environment variables or .env file. Provides comprehensive guidance for Jira ticket lifecycle management, API integration, and automation workflows.
AI-powered clarity engine for job seekers and founders. Not a resume fixer — a thinking partner. Helps you find your north star sentence: who you are, what you do, and why it matters to someone else. Produces one core version and targeted variations for different audiences. Use before interviews, investor conversations, networking events, or any moment where you need to introduce yourself under pressure.
Review code for bugs, security issues, and improvements. Use when the user asks to: (1) review code or a diff, (2) check code quality, (3) find bugs or issues, (4) audit for security problems. Trigger on phrases like 'review this', 'check my code', 'any issues with this', 'code review'.
Full-lifecycle career advisor — self-discovery through career growth. Use when the user wants to: (1) discover identity, values, ikigai, or skills inventory, (2) define dream job or analyze career gaps, (3) close gaps via learning, certifications, portfolio, or personal branding, (4) build narrative hats or role-specific positioning, (5) search for jobs, generate resumes, or prepare for interviews, (6) onboard into a new role, track achievements, or generate self-reviews, (7) backfill past roles, run weekly recall, or check career readiness. Proactively nudges users to document achievements NOW — not when they need a resume. Consolidates the former career-resume, career-tracker, portfolio-strategy, and github-profile skills.
Synthesizes professional accomplishments into high-converting landing page content. Triggers when a user wants to build a landing page, launch a consulting service, productize their career expertise, create a service page, or monetize their skills. Also triggers on: "freelance", "consulting offer", "offer page", "service offering", "turn my experience into a business". Uses career-advisor data as the foundation.
Query Google NotebookLM notebooks directly from Claude Code for source-grounded, citation-backed answers. Use when user mentions NotebookLM, shares a notebooklm.google.com URL, asks to query their notebooks/docs, or says "ask my NotebookLM", "check my docs", "query my notebook". Provides browser automation, notebook library management, and persistent auth. Drastically reduced hallucinations through document-only responses from Gemini.