[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71RMCGC7DAD8GER2R2CKC2M":3,"skill-same:01M71RMCGC7DAD8GER2R2CKC2M":108},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":52,"commitSha":53,"skillDirectory":54,"forksCount":55,"repositoryHtmlUrl":56,"repositoryHomepageUrl":6,"ownerHtmlUrl":57,"ownerBlogUrl":6,"ownerDescription":58,"updatedAt":59,"install":60,"resources":73},"01M71RMCGC7DAD8GER2R2CKC2M","predictable-revenue",null,"Build a scalable outbound B2B sales process with specialized roles (SDR, AE, CSM). Use when the user mentions \"outbound sales\", \"Cold Calling 2.0\", \"prospecting emails\", \"sales pipeline\", \"SDR process\", \"B2B SaaS sales\", \"sales development\", or \"pipeline velocity\". Also trigger when setting up a sales team from scratch, designing cold email sequences, or building qualification frameworks to improve close rates. Covers lead generation, qualification frameworks, and separating prospecting from closing. For offer design, see hundred-million-offers. For persuasion science, see influence-psychology.","vitalikpestov\u002FSkills-Catalog","vitalikpestov","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F13882997?v=4","01M71N4QG0CWRXX4R24JQZXDDQ","Vitalik Pestov","01M71N4QGMSYRW607DDSE0CQMM",2,"MIT","https:\u002F\u002Fgithub.com\u002Fvitalikpestov\u002FSkills-Catalog\u002Fblob\u002Fmain\u002F_Mobile-Dev\u002Ffrom-article-18-ui-ux\u002Fwondelai-skills\u002Fpredictable-revenue\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000005","邮件与沟通","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"predictable revenue","revenue","sequences","close","velocity","closing","lead generation","cold email","specialized","outbound","team","when","design","improve","up","pipeline","hundred-million","email sequences","cold","b2b","2026-11-10 13:02:02",false,"---\nname: predictable-revenue\ndescription: 'Build a scalable outbound B2B sales process with specialized roles (SDR, AE, CSM). Use when the user mentions \"outbound sales\", \"Cold Calling 2.0\", \"prospecting emails\", \"sales pipeline\", \"SDR process\", \"B2B SaaS sales\", \"sales development\", or \"pipeline velocity\". Also trigger when setting up a sales team from scratch, designing cold email sequences, or building qualification frameworks to improve close rates. Covers lead generation, qualification frameworks, and separating prospecting from closing. For offer design, see hundred-million-offers. For persuasion science, see influence-psychology.'\nlicense: MIT\nmetadata:\n  author: wondelai\n  version: \"1.1.0\"\n---\n\n# Predictable Revenue Framework\n\nA systematic approach to building a scalable, predictable B2B sales machine. Pioneered the outbound prospecting system that helped Salesforce add $100M in recurring revenue.\n\n## Core Principle\n\n**Predictable lead generation drives predictable revenue.** The biggest mistake in sales is having the same people prospect AND close. Specialization creates a repeatable, scalable machine.\n\n**The foundation:** Cold calling is dead. Cold Calling 2.0 — mass, personalized cold emails that generate referrals to the right person — is the new outbound. Combined with sales role specialization, this creates predictable, scalable revenue.\n\n## Scoring\n\n**Goal: 10\u002F10.** When evaluating or building a sales process, rate 0-10 based on predictability, specialization, and process maturity. A 10\u002F10 means clear role separation, repeatable prospecting process, and predictable pipeline generation; lower scores indicate ad-hoc sales or reliance on heroics. Always provide current score and improvements to reach 10\u002F10.\n\n## The Three Types of Leads\n\n**Not all leads are created equal. Treat them differently.**\n\n| Type | Source | Conversion | Cost | Example |\n|------|--------|------------|------|---------|\n| **Seeds** | Word of mouth, referrals, organic | Highest (best quality) | Lowest (takes time) | Customer referral, NPS-driven |\n| **Nets** | Marketing campaigns, inbound | Medium | Medium | Content marketing, SEO, webinars |\n| **Spears** | Outbound prospecting | Lower (but predictable) | Higher (people-intensive) | Cold Calling 2.0, targeted outreach |\n\n**Key insight:** Most companies over-invest in nets (marketing) and under-invest in spears (outbound). Seeds are the best but can't be manufactured quickly. A balanced mix of all three creates predictable revenue.\n\n**Revenue mix:**\n- **Seeds:** Invest in customer success, NPS, referral programs\n- **Nets:** Invest in content, SEO, paid acquisition\n- **Spears:** Invest in SDR team, Cold Calling 2.0\n\nSee: [references\u002Flead-types.md](references\u002Flead-types.md) for lead source strategy and investment allocation.\n\n## Sales Role Specialization\n\n**The #1 principle: Separate prospecting from closing.**\n\n**Traditional (broken) model:**\n- AEs prospect AND close\n- Result: AEs hate prospecting, pipeline is feast-or-famine\n\n**Predictable Revenue model:**\n\n| Role | Focus | Metrics |\n|------|-------|---------|\n| **SDR (Sales Development Rep)** | Outbound prospecting → qualified opportunities | Qualified meetings\u002Fmonth |\n| **MDR (Market Development Rep)** | Inbound lead qualification | Qualified leads\u002Fmonth |\n| **AE (Account Executive)** | Close deals | Revenue closed, win rate |\n| **CSM (Customer Success Manager)** | Retain and grow accounts | Retention rate, expansion revenue |\n\n### SDR (Sales Development Rep)\n\n**Mission:** Generate qualified pipeline through outbound prospecting.\n\n**Focus:**\n- Research target accounts\n- Write personalized Cold Calling 2.0 emails\n- Get referred to the right person\n- Qualify opportunities (ANUM)\n- Pass qualified opportunities to AEs\n\n**Not their job:**\n- Close deals\n- Handle inbound leads\n- Manage existing customers\n\n**Metrics:**\n- Qualified opportunities generated per month\n- Response rate to outbound emails\n- Meetings booked per week\n- Pipeline value generated\n\n**SDR capacity:** One SDR typically generates 10-20 qualified opportunities per month.\n\n### AE (Account Executive)\n\n**Mission:** Close deals from qualified pipeline.\n\n**Focus:**\n- Run discovery calls\n- Demo and present solutions\n- Negotiate and close\n- Hand off to CSM\n\n**Not their job:**\n- Prospect for new leads (this is SDR's job)\n- Qualify inbound leads (this is MDR's job)\n- Manage post-sale relationships (CSM's job)\n\n**Metrics:**\n- Revenue closed\n- Win rate\n- Average deal size\n- Sales cycle length\n\n### CSM (Customer Success Manager)\n\n**Mission:** Retain customers and grow accounts.\n\n**Focus:**\n- Onboard new customers\n- Drive adoption and engagement\n- Identify expansion opportunities\n- Prevent churn\n\n**Metrics:**\n- Net revenue retention\n- Churn rate\n- Expansion revenue\n- NPS \u002F CSAT\n\n**The virtuous cycle:**\n```\nSDR generates pipeline → AE closes → CSM retains\u002Fgrows → Happy customer refers (Seeds)\n```\n\nSee: [references\u002Froles.md](references\u002Froles.md) for role definitions, career paths, and hiring profiles.\n\n## Cold Calling 2.0\n\n**The outbound prospecting methodology that replaces traditional cold calling.**\n\n**Why traditional cold calling fails:**\n- Gatekeepers block calls\n- Decision makers don't answer phones\n- 1-3% connection rate\n- Damages brand\n- Not scalable\n\n**Cold Calling 2.0 process:**\n\n```\n1. Build list → 2. Send mass email → 3. Get referral → 4. Call the referral → 5. Qualify\n```\n\n### Step 1: Build Target Account List\n\n**Ideal Customer Profile (ICP):**\n- Company size (employees, revenue)\n- Industry\n- Technology stack\n- Geography\n- Pain points\n\n**Build list using:**\n- LinkedIn Sales Navigator\n- ZoomInfo \u002F Apollo \u002F Clearbit\n- Company websites\n- Industry directories\n\n**Target:** 200-500 accounts per SDR per quarter\n\n### Step 2: The Referral Email\n\n**The core innovation:** Don't email the decision maker directly. Email above them and ask for a referral down.\n\n**Why it works:**\n- Senior people are helpful (they forward emails)\n- Referrals have 3-5x higher response rate\n- Creates warm introduction from within the company\n\n**The email template:**\n\n**Subject:** Quick question\n\n**Body:**\n> Hi [Name],\n>\n> I'm not sure if you're the right person to speak to about [specific topic] at [Company], but I was hoping you could point me to the right person.\n>\n> We help [companies like theirs] with [specific value prop].\n>\n> Would you mind pointing me to the right person to talk to?\n>\n> Thanks,\n> [Your name]\n\n**Key elements:**\n- Short (\u003C 100 words)\n- No pitch, no attachments, no links\n- Asks for referral, not a meeting\n- Specific about what you do\n- Easy to forward\n\n**Response rate:** 9-15% (vs. 1-3% for traditional cold emails)\n\n### Step 3: Follow Up\n\n**Follow-up sequence:**\n\n| Day | Action |\n|-----|--------|\n| Day 1 | Send referral email |\n| Day 3 | Follow up if no response |\n| Day 7 | Second follow up (different angle) |\n| Day 14 | Break-up email (\"Should I close your file?\") |\n| Day 30 | Re-engage (new trigger event or content) |\n\n**Break-up email example:**\n> Hi [Name],\n>\n> I haven't heard back from you. I don't want to be a pest.\n>\n> Should I close your file, or would it make sense to chat?\n>\n> [Your name]\n\n**Why break-up emails work:** People respond to the threat of losing access\u002Fopportunity (scarcity principle).\n\n### Step 4: Qualify with ANUM\n\n**ANUM qualification framework:**\n\n| Criteria | Question | Strong Signal | Weak Signal |\n|----------|----------|---------------|-------------|\n| **A**uthority | Can this person decide? | Decision maker or strong influencer | No buying power |\n| **N**eed | Do they have the problem you solve? | Active pain, looking for solutions | \"Nice to have\" |\n| **U**rgency | When do they need to solve it? | This quarter, budget allocated | \"Someday\" |\n| **M**oney | Can they afford it? | Budget exists, within range | No budget, too expensive |\n\n**Qualification call structure:**\n1. Build rapport (2 min)\n2. Set agenda (\"I want to understand your situation and see if there's a fit\")\n3. Discovery questions (10-15 min)\n4. ANUM qualification (built into discovery)\n5. Next steps (if qualified → schedule AE demo)\n\n### Step 5: Hand Off to AE\n\n**The handoff must include:**\n- Account background and ICP match\n- Contact details and role\n- Pain points discovered\n- ANUM qualification notes\n- Agreed next steps\n- Any competitive intel\n\n**Handoff meeting:** SDR introduces AE on a brief 3-way call or email, then drops off.\n\nSee: [references\u002Fcold-calling-2.md](references\u002Fcold-calling-2.md) for email templates, sequences, and scripts.\n\n## Pipeline Math\n\n**The math of predictable revenue:**\n\n```\nRevenue Goal ÷ Average Deal Size = Deals Needed\nDeals Needed ÷ Win Rate = Opportunities Needed\nOpportunities Needed ÷ SDR Conversion = Prospects Needed\nProspects Needed ÷ Response Rate = Emails Needed\n```\n\n**Example:**\n- **Revenue goal:** $1M ARR\n- **Average deal:** $20K ARR\n- **Deals needed:** 50\n- **Win rate:** 25%\n- **Opportunities needed:** 200\n- **SDR conversion:** 10% of responses become qualified\n- **Response rate:** 10% of emails get responses\n- **Emails needed:** 20,000\n- **SDRs needed:** ~2-3 (each sends 300-500 emails\u002Fmonth)\n\n**Capacity planning:**\n\n| Metric | Benchmark | Your Number |\n|--------|-----------|-------------|\n| Emails per SDR per day | 50-100 | |\n| Response rate | 9-15% | |\n| Qualified opportunities per SDR per month | 10-20 | |\n| AE demo-to-close rate | 20-30% | |\n| Average sales cycle | 30-90 days | |\n\nSee: [references\u002Fpipeline-math.md](references\u002Fpipeline-math.md) for revenue modeling templates.\n\n## Building the Sales Development Team\n\n### Hiring SDRs\n\n**Ideal SDR profile:**\n- Coachable (most important trait)\n- Curious and intelligent\n- Strong writing skills\n- Resilient (handles rejection)\n- Organized and process-oriented\n- Not necessarily experienced\n\n**Where to hire:**\n- Recent graduates\n- Career changers\n- Internal transfers\n- SDR-to-AE career path candidates\n\n**SDR career path:**\n```\nSDR (6-18 months) → Senior SDR → AE or SDR Manager\n```\n\n### SDR Ramp Time\n\n| Phase | Timeline | Expectations |\n|-------|----------|-------------|\n| **Training** | Weeks 1-2 | Product knowledge, tools, process |\n| **Shadowing** | Weeks 3-4 | Observe experienced SDRs, practice |\n| **Ramping** | Months 2-3 | 50% of full quota |\n| **Full quota** | Month 4+ | 100% of quota |\n\n**Full ramp:** Expect 3-4 months to full productivity.\n\n### SDR Compensation\n\n**Structure:** Base salary + variable (commission on qualified opportunities)\n\n**Typical split:** 60\u002F40 or 70\u002F30 (base\u002Fvariable)\n\n**Variable triggers:**\n- Per qualified opportunity generated\n- Bonus for opportunities that close\n- Bonus for hitting\u002Fexceeding quota\n\nSee: [references\u002Fteam-building.md](references\u002Fteam-building.md) for hiring, onboarding, and compensation.\n\n## Metrics and Dashboards\n\n**Key metrics to track:**\n\n### Leading Indicators (Predictive)\n- Emails sent per SDR per day\n- Response rate\n- Meetings booked per week\n- Qualified opportunities per month\n- Pipeline value generated\n\n### Lagging Indicators (Results)\n- Revenue closed\n- Win rate\n- Average deal size\n- Sales cycle length\n- Customer acquisition cost (CAC)\n\n### Efficiency Metrics\n- Cost per qualified opportunity\n- SDR:AE ratio (typically 2-3 SDRs per AE)\n- LTV:CAC ratio (target >3:1)\n- Payback period\n\n**Dashboard cadence:**\n- **Daily:** Activity metrics (emails, calls, responses)\n- **Weekly:** Pipeline metrics (opportunities, meetings)\n- **Monthly:** Revenue metrics (closed, win rate, cycle)\n- **Quarterly:** Efficiency metrics (CAC, LTV, ratios)\n\nSee: [references\u002Fmetrics.md](references\u002Fmetrics.md) for dashboard templates.\n\n## Common Mistakes\n\n| Mistake | Why It Fails | Fix |\n|---------|-------------|------|\n| **AEs prospecting** | Feast-or-famine pipeline | Hire dedicated SDRs |\n| **Long, pitchy emails** | Low response rate | Short, referral-focused emails |\n| **No ICP definition** | Wasted effort on wrong accounts | Define ICP before hiring SDRs |\n| **Too few SDRs** | Can't generate enough pipeline | Pipeline math: work backward from revenue goal |\n| **No hand-off process** | Leads fall through cracks | Standardize SDR→AE handoff |\n| **Measuring activity, not results** | Busy but not productive | Track qualified opportunities, not just emails |\n\n## Quick Diagnostic\n\nAudit any B2B sales process:\n\n| Question | If No | Action |\n|----------|-------|--------|\n| Are prospecting and closing separated? | SDRs doing both = bottleneck | Create dedicated SDR role |\n| Is there a defined outbound process? | Ad-hoc prospecting | Implement Cold Calling 2.0 |\n| Can you predict pipeline 3 months out? | Revenue is unpredictable | Build pipeline math model |\n| Do you know your lead type mix? | Over-reliance on one source | Balance seeds, nets, spears |\n| Is SDR→AE handoff standardized? | Leads lost in transition | Create handoff checklist |\n\n## Reference Files\n\n- [lead-types.md](references\u002Flead-types.md): Seeds, nets, spears strategy and investment\n- [roles.md](references\u002Froles.md): SDR, MDR, AE, CSM role definitions and hiring\n- [cold-calling-2.md](references\u002Fcold-calling-2.md): Email templates, sequences, follow-up cadence\n- [pipeline-math.md](references\u002Fpipeline-math.md): Revenue modeling, capacity planning\n- [team-building.md](references\u002Fteam-building.md): Hiring, onboarding, compensation, career paths\n- [metrics.md](references\u002Fmetrics.md): Dashboard templates, KPI tracking\n- [qualification.md](references\u002Fqualification.md): ANUM framework, discovery questions\n- [case-studies.md](references\u002Fcase-studies.md): Salesforce, HubSpot, and scaling stories\n\n## Further Reading\n\nThis skill is based on Aaron Ross's Predictable Revenue methodology. For the complete system:\n\n- [*\"Predictable Revenue\"*](https:\u002F\u002Fwww.amazon.com\u002FPredictable-Revenue-Business-Practices-Salesforce-com\u002Fdp\u002F0984380213?tag=wondelai00-20) by Aaron Ross & Marylou Tyler\n- [*\"From Impossible to Inevitable\"*](https:\u002F\u002Fwww.amazon.com\u002FImpossible-Inevitable-Hyper-Growth-Companies-Predictable\u002Fdp\u002F1119166713?tag=wondelai00-20) by Aaron Ross & Jason Lemkin (scaling to $100M+ ARR)\n\n## About the Author\n\n**Aaron Ross** built the outbound sales process at Salesforce.com that added $100M+ in recurring revenue. His Cold Calling 2.0 methodology became the standard for B2B outbound prospecting and is used by thousands of companies worldwide. *Predictable Revenue* is known as \"The Bible of Outbound Sales\" and has influenced an entire generation of SaaS sales organizations. Ross is also co-founder of Predictable Revenue Inc., which helps companies build outbound sales machines.\n","# Predictable Revenue Framework\n\nA systematic approach to building a scalable, predictable B2B sales machine. Pioneered the outbound prospecting system that helped Salesforce add $100M in recurring revenue.\n\n## Core Principle\n\n**Predictable lead generation drives predictable revenue.** The biggest mistake in sales is having the same people prospect AND close. Specialization creates a repeatable, scalable machine.\n\n**The foundation:** Cold calling is dead. Cold Calling 2.0 — mass, personalized cold emails that generate referrals to the right person — is the new outbound. Combined with sales role specialization, this creates predictable, scalable revenue.\n\n## Scoring\n\n**Goal: 10\u002F10.** When evaluating or building a sales process, rate 0-10 based on predictability, specialization, and process maturity. A 10\u002F10 means clear role separation, repeatable prospecting process, and predictable pipeline generation; lower scores indicate ad-hoc sales or reliance on heroics. Always provide current score and improvements to reach 10\u002F10.\n\n## The Three Types of Leads\n\n**Not all leads are created equal. Treat them differently.**\n\n| Type | Source | Conversion | Cost | Example |\n|------|--------|------------|------|---------|\n| **Seeds** | Word of mouth, referrals, organic | Highest (best quality) | Lowest (takes time) | Customer referral, NPS-driven |\n| **Nets** | Marketing campaigns, inbound | Medium | Medium | Content marketing, SEO, webinars |\n| **Spears** | Outbound prospecting | Lower (but predictable) | Higher (people-intensive) | Cold Calling 2.0, targeted outreach |\n\n**Key insight:** Most companies over-invest in nets (marketing) and under-invest in spears (outbound). Seeds are the best but can't be manufactured quickly. A balanced mix of all three creates predictable revenue.\n\n**Revenue mix:**\n- **Seeds:** Invest in customer success, NPS, referral programs\n- **Nets:** Invest in content, SEO, paid acquisition\n- **Spears:** Invest in SDR team, Cold Calling 2.0\n\nSee: [references\u002Flead-types.md](references\u002Flead-types.md) for lead source strategy and investment allocation.\n\n## Sales Role Specialization\n\n**The #1 principle: Separate prospecting from closing.**\n\n**Traditional (broken) model:**\n- AEs prospect AND close\n- Result: AEs hate prospecting, pipeline is feast-or-famine\n\n**Predictable Revenue model:**\n\n| Role | Focus | Metrics |\n|------|-------|---------|\n| **SDR (Sales Development Rep)** | Outbound prospecting → qualified opportunities | Qualified meetings\u002Fmonth |\n| **MDR (Market Development Rep)** | Inbound lead qualification | Qualified leads\u002Fmonth |\n| **AE (Account Executive)** | Close deals | Revenue closed, win rate |\n| **CSM (Customer Success Manager)** | Retain and grow accounts | Retention rate, expansion revenue |\n\n### SDR (Sales Development Rep)\n\n**Mission:** Generate qualified pipeline through outbound prospecting.\n\n**Focus:**\n- Research target accounts\n- Write personalized Cold Calling 2.0 emails\n- Get referred to the right person\n- Qualify opportunities (ANUM)\n- Pass qualified opportunities to AEs\n\n**Not their job:**\n- Close deals\n- Handle inbound leads\n- Manage existing customers\n\n**Metrics:**\n- Qualified opportunities generated per month\n- Response rate to outbound emails\n- Meetings booked per week\n- Pipeline value generated\n\n**SDR capacity:** One SDR typically generates 10-20 qualified opportunities per month.\n\n### AE (Account Executive)\n\n**Mission:** Close deals from qualified pipeline.\n\n**Focus:**\n- Run discovery calls\n- Demo and present solutions\n- Negotiate and close\n- Hand off to CSM\n\n**Not their job:**\n- Prospect for new leads (this is SDR's job)\n- Qualify inbound leads (this is MDR's job)\n- Manage post-sale relationships (CSM's job)\n\n**Metrics:**\n- Revenue closed\n- Win rate\n- Average deal size\n- Sales cycle length\n\n### CSM (Customer Success Manager)\n\n**Mission:** Retain customers and grow accounts.\n\n**Focus:**\n- Onboard new customers\n- Drive adoption and engagement\n- Identify expansion opportunities\n- Prevent churn\n\n**Metrics:**\n- Net revenue retention\n- Churn rate\n- Expansion revenue\n- NPS \u002F CSAT\n\n**The virtuous cycle:**\n```\nSDR generates pipeline → AE closes → CSM retains\u002Fgrows → Happy customer refers (Seeds)\n```\n\nSee: [references\u002Froles.md](references\u002Froles.md) for role definitions, career paths, and hiring profiles.\n\n## Cold Calling 2.0\n\n**The outbound prospecting methodology that replaces traditional cold calling.**\n\n**Why traditional cold calling fails:**\n- Gatekeepers block calls\n- Decision makers don't answer phones\n- 1-3% connection rate\n- Damages brand\n- Not scalable\n\n**Cold Calling 2.0 process:**\n\n```\n1. Build list → 2. Send mass email → 3. Get referral → 4. Call the referral → 5. Qualify\n```\n\n### Step 1: Build Target Account List\n\n**Ideal Customer Profile (ICP):**\n- Company size (employees, revenue)\n- Industry\n- Technology stack\n- Geography\n- Pain points\n\n**Build list using:**\n- LinkedIn Sales Navigator\n- ZoomInfo \u002F Apollo \u002F Clearbit\n- Company websites\n- Industry directories\n\n**Target:** 200-500 accounts per SDR per quarter\n\n### Step 2: The Referral Email\n\n**The core innovation:** Don't email the decision maker directly. Email above them and ask for a referral down.\n\n**Why it works:**\n- Senior people are helpful (they forward emails)\n- Referrals have 3-5x higher response rate\n- Creates warm introduction from within the company\n\n**The email template:**\n\n**Subject:** Quick question\n\n**Body:**\n> Hi [Name],\n>\n> I'm not sure if you're the right person to speak to about [specific topic] at [Company], but I was hoping you could point me to the right person.\n>\n> We help [companies like theirs] with [specific value prop].\n>\n> Would you mind pointing me to the right person to talk to?\n>\n> Thanks,\n> [Your name]\n\n**Key elements:**\n- Short (\u003C 100 words)\n- No pitch, no attachments, no links\n- Asks for referral, not a meeting\n- Specific about what you do\n- Easy to forward\n\n**Response rate:** 9-15% (vs. 1-3% for traditional cold emails)\n\n### Step 3: Follow Up\n\n**Follow-up sequence:**\n\n| Day | Action |\n|-----|--------|\n| Day 1 | Send referral email |\n| Day 3 | Follow up if no response |\n| Day 7 | Second follow up (different angle) |\n| Day 14 | Break-up email (\"Should I close your file?\") |\n| Day 30 | Re-engage (new trigger event or content) |\n\n**Break-up email example:**\n> Hi [Name],\n>\n> I haven't heard back from you. I don't want to be a pest.\n>\n> Should I close your file, or would it make sense to chat?\n>\n> [Your name]\n\n**Why break-up emails work:** People respond to the threat of losing access\u002Fopportunity (scarcity principle).\n\n### Step 4: Qualify with ANUM\n\n**ANUM qualification framework:**\n\n| Criteria | Question | Strong Signal | Weak Signal |\n|----------|----------|---------------|-------------|\n| **A**uthority | Can this person decide? | Decision maker or strong influencer | No buying power |\n| **N**eed | Do they have the problem you solve? | Active pain, looking for solutions | \"Nice to have\" |\n| **U**rgency | When do they need to solve it? | This quarter, budget allocated | \"Someday\" |\n| **M**oney | Can they afford it? | Budget exists, within range | No budget, too expensive |\n\n**Qualification call structure:**\n1. Build rapport (2 min)\n2. Set agenda (\"I want to understand your situation and see if there's a fit\")\n3. Discovery questions (10-15 min)\n4. ANUM qualification (built into discovery)\n5. Next steps (if qualified → schedule AE demo)\n\n### Step 5: Hand Off to AE\n\n**The handoff must include:**\n- Account background and ICP match\n- Contact details and role\n- Pain points discovered\n- ANUM qualification notes\n- Agreed next steps\n- Any competitive intel\n\n**Handoff meeting:** SDR introduces AE on a brief 3-way call or email, then drops off.\n\nSee: [references\u002Fcold-calling-2.md](references\u002Fcold-calling-2.md) for email templates, sequences, and scripts.\n\n## Pipeline Math\n\n**The math of predictable revenue:**\n\n```\nRevenue Goal ÷ Average Deal Size = Deals Needed\nDeals Needed ÷ Win Rate = Opportunities Needed\nOpportunities Needed ÷ SDR Conversion = Prospects Needed\nProspects Needed ÷ Response Rate = Emails Needed\n```\n\n**Example:**\n- **Revenue goal:** $1M ARR\n- **Average deal:** $20K ARR\n- **Deals needed:** 50\n- **Win rate:** 25%\n- **Opportunities needed:** 200\n- **SDR conversion:** 10% of responses become qualified\n- **Response rate:** 10% of emails get responses\n- **Emails needed:** 20,000\n- **SDRs needed:** ~2-3 (each sends 300-500 emails\u002Fmonth)\n\n**Capacity planning:**\n\n| Metric | Benchmark | Your Number |\n|--------|-----------|-------------|\n| Emails per SDR per day | 50-100 | |\n| Response rate | 9-15% | |\n| Qualified opportunities per SDR per month | 10-20 | |\n| AE demo-to-close rate | 20-30% | |\n| Average sales cycle | 30-90 days | |\n\nSee: [references\u002Fpipeline-math.md](references\u002Fpipeline-math.md) for revenue modeling templates.\n\n## Building the Sales Development Team\n\n### Hiring SDRs\n\n**Ideal SDR profile:**\n- Coachable (most important trait)\n- Curious and intelligent\n- Strong writing skills\n- Resilient (handles rejection)\n- Organized and process-oriented\n- Not necessarily experienced\n\n**Where to hire:**\n- Recent graduates\n- Career changers\n- Internal transfers\n- SDR-to-AE career path candidates\n\n**SDR career path:**\n```\nSDR (6-18 months) → Senior SDR → AE or SDR Manager\n```\n\n### SDR Ramp Time\n\n| Phase | Timeline | Expectations |\n|-------|----------|-------------|\n| **Training** | Weeks 1-2 | Product knowledge, tools, process |\n| **Shadowing** | Weeks 3-4 | Observe experienced SDRs, practice |\n| **Ramping** | Months 2-3 | 50% of full quota |\n| **Full quota** | Month 4+ | 100% of quota |\n\n**Full ramp:** Expect 3-4 months to full productivity.\n\n### SDR Compensation\n\n**Structure:** Base salary + variable (commission on qualified opportunities)\n\n**Typical split:** 60\u002F40 or 70\u002F30 (base\u002Fvariable)\n\n**Variable triggers:**\n- Per qualified opportunity generated\n- Bonus for opportunities that close\n- Bonus for hitting\u002Fexceeding quota\n\nSee: [references\u002Fteam-building.md](references\u002Fteam-building.md) for hiring, onboarding, and compensation.\n\n## Metrics and Dashboards\n\n**Key metrics to track:**\n\n### Leading Indicators (Predictive)\n- Emails sent per SDR per day\n- Response rate\n- Meetings booked per week\n- Qualified opportunities per month\n- Pipeline value generated\n\n### Lagging Indicators (Results)\n- Revenue closed\n- Win rate\n- Average deal size\n- Sales cycle length\n- Customer acquisition cost (CAC)\n\n### Efficiency Metrics\n- Cost per qualified opportunity\n- SDR:AE ratio (typically 2-3 SDRs per AE)\n- LTV:CAC ratio (target >3:1)\n- Payback period\n\n**Dashboard cadence:**\n- **Daily:** Activity metrics (emails, calls, responses)\n- **Weekly:** Pipeline metrics (opportunities, meetings)\n- **Monthly:** Revenue metrics (closed, win rate, cycle)\n- **Quarterly:** Efficiency metrics (CAC, LTV, ratios)\n\nSee: [references\u002Fmetrics.md](references\u002Fmetrics.md) for dashboard templates.\n\n## Common Mistakes\n\n| Mistake | Why It Fails | Fix |\n|---------|-------------|------|\n| **AEs prospecting** | Feast-or-famine pipeline | Hire dedicated SDRs |\n| **Long, pitchy emails** | Low response rate | Short, referral-focused emails |\n| **No ICP definition** | Wasted effort on wrong accounts | Define ICP before hiring SDRs |\n| **Too few SDRs** | Can't generate enough pipeline | Pipeline math: work backward from revenue goal |\n| **No hand-off process** | Leads fall through cracks | Standardize SDR→AE handoff |\n| **Measuring activity, not results** | Busy but not productive | Track qualified opportunities, not just emails |\n\n## Quick Diagnostic\n\nAudit any B2B sales process:\n\n| Question | If No | Action |\n|----------|-------|--------|\n| Are prospecting and closing separated? | SDRs doing both = bottleneck | Create dedicated SDR role |\n| Is there a defined outbound process? | Ad-hoc prospecting | Implement Cold Calling 2.0 |\n| Can you predict pipeline 3 months out? | Revenue is unpredictable | Build pipeline math model |\n| Do you know your lead type mix? | Over-reliance on one source | Balance seeds, nets, spears |\n| Is SDR→AE handoff standardized? | Leads lost in transition | Create handoff checklist |\n\n## Reference Files\n\n- [lead-types.md](references\u002Flead-types.md): Seeds, nets, spears strategy and investment\n- [roles.md](references\u002Froles.md): SDR, MDR, AE, CSM role definitions and hiring\n- [cold-calling-2.md](references\u002Fcold-calling-2.md): Email templates, sequences, follow-up cadence\n- [pipeline-math.md](references\u002Fpipeline-math.md): Revenue modeling, capacity planning\n- [team-building.md](references\u002Fteam-building.md): Hiring, onboarding, compensation, career paths\n- [metrics.md](references\u002Fmetrics.md): Dashboard templates, KPI tracking\n- [qualification.md](references\u002Fqualification.md): ANUM framework, discovery questions\n- [case-studies.md](references\u002Fcase-studies.md): Salesforce, HubSpot, and scaling stories\n\n## Further Reading\n\nThis skill is based on Aaron Ross's Predictable Revenue methodology. For the complete system:\n\n- [*\"Predictable Revenue\"*](https:\u002F\u002Fwww.amazon.com\u002FPredictable-Revenue-Business-Practices-Salesforce-com\u002Fdp\u002F0984380213?tag=wondelai00-20) by Aaron Ross & Marylou Tyler\n- [*\"From Impossible to Inevitable\"*](https:\u002F\u002Fwww.amazon.com\u002FImpossible-Inevitable-Hyper-Growth-Companies-Predictable\u002Fdp\u002F1119166713?tag=wondelai00-20) by Aaron Ross & Jason Lemkin (scaling to $100M+ ARR)\n\n## About the Author\n\n**Aaron Ross** built the outbound sales process at Salesforce.com that added $100M+ in recurring revenue. His Cold Calling 2.0 methodology became the standard for B2B outbound prospecting and is used by thousands of companies worldwide. *Predictable Revenue* is known as \"The Bible of Outbound Sales\" and has influenced an entire generation of SaaS sales organizations. Ross is also co-founder of Predictable Revenue Inc., which helps companies build outbound sales machines.\n",{"name":5,"license":15,"metadata":49,"description":7},{"author":50,"version":51},"wondelai","1.1.0","main","fbfb242f793fdf040f3a1a6b100896c188c228c8","_Mobile-Dev\u002Ffrom-article-18-ui-ux\u002Fwondelai-skills\u002Fpredictable-revenue",1,"https:\u002F\u002Fgithub.com\u002Fvitalikpestov\u002FSkills-Catalog","https:\u002F\u002Fgithub.com\u002Fvitalikpestov","Listing on crypto exchanges","2026-06-15 22:12:56",{"source":8,"skillName":5,"commands":61,"prompt":71,"zipAvailable":72},[62,65,68],{"tool":63,"command":64},"npx","npx skills add vitalikpestov\u002FSkills-Catalog --skill predictable-revenue",{"tool":66,"command":67},"bunx","bunx skills add vitalikpestov\u002FSkills-Catalog --skill predictable-revenue",{"tool":69,"command":70},"pnpm","pnpm dlx skills add vitalikpestov\u002FSkills-Catalog --skill predictable-revenue","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fvitalikpestov\u002FSkills-Catalog\u002Fblob\u002Fmain\u002F_Mobile-Dev\u002Ffrom-article-18-ui-ux\u002Fwondelai-skills\u002Fpredictable-revenue\u002FSKILL.md",true,[74,80,84,88,92,96,100,104],{"path":75,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":78,"sourceHtmlUrl":79},"references\u002Fcase-studies.md","REFERENCE","参考文档",14733,"https:\u002F\u002Fgithub.com\u002Fvitalikpestov\u002FSkills-Catalog\u002Fblob\u002Fmain\u002F_Mobile-Dev\u002Ffrom-article-18-ui-ux\u002Fwondelai-skills\u002Fpredictable-revenue\u002Freferences\u002Fcase-studies.md",{"path":81,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":82,"sourceHtmlUrl":83},"references\u002Fcold-calling-2.md",12539,"https:\u002F\u002Fgithub.com\u002Fvitalikpestov\u002FSkills-Catalog\u002Fblob\u002Fmain\u002F_Mobile-Dev\u002Ffrom-article-18-ui-ux\u002Fwondelai-skills\u002Fpredictable-revenue\u002Freferences\u002Fcold-calling-2.md",{"path":85,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":86,"sourceHtmlUrl":87},"references\u002Flead-types.md",11290,"https:\u002F\u002Fgithub.com\u002Fvitalikpestov\u002FSkills-Catalog\u002Fblob\u002Fmain\u002F_Mobile-Dev\u002Ffrom-article-18-ui-ux\u002Fwondelai-skills\u002Fpredictable-revenue\u002Freferences\u002Flead-types.md",{"path":89,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":90,"sourceHtmlUrl":91},"references\u002Fmetrics.md",13827,"https:\u002F\u002Fgithub.com\u002Fvitalikpestov\u002FSkills-Catalog\u002Fblob\u002Fmain\u002F_Mobile-Dev\u002Ffrom-article-18-ui-ux\u002Fwondelai-skills\u002Fpredictable-revenue\u002Freferences\u002Fmetrics.md",{"path":93,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":94,"sourceHtmlUrl":95},"references\u002Fpipeline-math.md",10734,"https:\u002F\u002Fgithub.com\u002Fvitalikpestov\u002FSkills-Catalog\u002Fblob\u002Fmain\u002F_Mobile-Dev\u002Ffrom-article-18-ui-ux\u002Fwondelai-skills\u002Fpredictable-revenue\u002Freferences\u002Fpipeline-math.md",{"path":97,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":98,"sourceHtmlUrl":99},"references\u002Fqualification.md",15782,"https:\u002F\u002Fgithub.com\u002Fvitalikpestov\u002FSkills-Catalog\u002Fblob\u002Fmain\u002F_Mobile-Dev\u002Ffrom-article-18-ui-ux\u002Fwondelai-skills\u002Fpredictable-revenue\u002Freferences\u002Fqualification.md",{"path":101,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":102,"sourceHtmlUrl":103},"references\u002Froles.md",12938,"https:\u002F\u002Fgithub.com\u002Fvitalikpestov\u002FSkills-Catalog\u002Fblob\u002Fmain\u002F_Mobile-Dev\u002Ffrom-article-18-ui-ux\u002Fwondelai-skills\u002Fpredictable-revenue\u002Freferences\u002Froles.md",{"path":105,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":106,"sourceHtmlUrl":107},"references\u002Fteam-building.md",13138,"https:\u002F\u002Fgithub.com\u002Fvitalikpestov\u002FSkills-Catalog\u002Fblob\u002Fmain\u002F_Mobile-Dev\u002Ffrom-article-18-ui-ux\u002Fwondelai-skills\u002Fpredictable-revenue\u002Freferences\u002Fteam-building.md",[109,150,176,193,216,247],{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":129,"publishedAt":44},"01M71V1MC994P553631JZSWVYD","solana-dev","Use when user asks to \"build a Solana dapp\", \"write an Anchor program\", \"create a token\", \"debug Solana errors\", \"set up wallet connection\", \"test my Solana program\", \"deploy to devnet\", or \"explain Solana concepts\" (rent, accounts, PDAs, CPIs, etc.). End-to-end Solana development playbook covering wallet connection, Anchor\u002FPinocchio programs, Codama client generation, LiteSVM\u002FMollusk\u002FSurfpool testing, and security checklists. Integrates with the Solana MCP server for live documentation search. Prefers framework-kit (@solana\u002Fclient + @solana\u002Freact-hooks) for UI, wallet-standard-first connection (incl. ConnectorKit), @solana\u002Fkit for client\u002FRPC code, and @solana\u002Fweb3-compat for legacy boundaries.","https:\u002F\u002Fgithub.com\u002Fvitalikpestov\u002FSkills-Catalog\u002Fblob\u002Fmain\u002F_Web3\u002Fsolana-dev\u002Fskill\u002FSKILL.md",[115,118,121,124],{"categoryNo":116,"categoryName":117,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":119,"categoryName":120,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",{"categoryNo":122,"categoryName":123,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":125,"categoryName":126,"taxonomyType":127,"taxonomyTypeDesc":128},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[130,131,132,133,134,135,136,137,138,139,140,141,142,143,144,145,146,147,148,149],"dev","solana dev","solana","Wallet","search","testing","solana cli","kit","MCP","web3","react","create","server","write","playbook","live","security","ui","concepts","toolchain",{"skillNo":151,"name":152,"nameZh":6,"description":153,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":154,"categories":155,"keywords":156,"publishedAt":44},"01M71TYQPHE2YGKTT7DG9QCW3K","generating-trading-signals","Generate trading signals using technical indicators (RSI, MACD, Bollinger Bands, etc.).\nCombines multiple indicators into composite signals with confidence scores.\nUse when analyzing assets for trading opportunities or checking technical indicators.\nTrigger with phrases like \"get trading signals\", \"check indicators\", \"analyze for entry\",\n\"scan for opportunities\", \"generate buy\u002Fsell signals\", or \"technical analysis\".","https:\u002F\u002Fgithub.com\u002Fvitalikpestov\u002FSkills-Catalog\u002Fblob\u002Fmain\u002F_Trading-Finance\u002Fgenerating-trading-signals\u002FSKILL.md",[],[157,158,159,160,161,162,163,164,165,166,167,168,169,35,170,171,172,173,174,175],"generating trading signals","signals","trading signals","trading","get","technical indicators","for","scan","rsi","trigger","python","technical","use","Bash","analysis","code","io","check","analyze",{"skillNo":177,"name":178,"nameZh":6,"description":179,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":180,"categories":181,"keywords":182,"publishedAt":44},"01M71TY4CR3GKGQ3M12X9WN95Y","prediction-monitor","Prediction Monitor - Auto-activating skill for ML Deployment.\nTriggers on: prediction monitor, prediction monitor\nPart of the ML Deployment skill category.","https:\u002F\u002Fgithub.com\u002Fvitalikpestov\u002FSkills-Catalog\u002Fblob\u002Fmain\u002F_Trading-Finance\u002FAI Predictions\u002Fprediction-monitor\u002FSKILL.md",[],[183,184,185,163,186,187,143,188,189,190,191,192,170],"prediction","monitor","prediction monitor","deployment","read","edit","triggers","grep","auto","ml",{"skillNo":194,"name":195,"nameZh":6,"description":196,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":197,"categories":198,"keywords":199,"publishedAt":44},"01M71TXD9MYXZC39HCPP909HTZ","strategy-advisor","High-level strategic thinking and business decision guidance for planning and direction-setting.\nUse when: making strategic decisions, evaluating business options, setting direction, analyzing\ntrade-offs, or when user mentions strategy, business planning, competitive analysis, or long-term planning.","https:\u002F\u002Fgithub.com\u002Fvitalikpestov\u002FSkills-Catalog\u002Fblob\u002Fmain\u002F_Product-Apps\u002Fstrategy-advisor\u002FSKILL.md",[],[200,201,202,203,204,205,206,207,208,163,209,210,211,169,212,213,35,214,171,215],"strategy advisor","strategy","advisor","competitive","setting","thinking","planning","direction","trade-offs","long","decision","strategic","business","apps","decisions","trade",{"skillNo":217,"name":218,"nameZh":6,"description":219,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":220,"sourceHtmlUrl":221,"categories":222,"keywords":229,"publishedAt":44},"01M71TWHBT2R1P1FNWTW67ZREP","app-paywall-pilot","Design, audit, debug, and implement App Store-compliant mobile paywalls, subscription flows, pricing screens, trials, offers, feature gates, and subscription lifecycle UX. Use when the user asks to audit my paywall, fix App Store 3.1.2 rejection, improve trial-to-paid, choose plans\u002Fprices\u002Ftrials, review RevenueCat\u002FAdapty\u002FApphud\u002FSuperwall setup, calculate LTV\u002FROAS, or build paywall implementation.","https:\u002F\u002Fgithub.com\u002Fvitalikpestov\u002FSkills-Catalog\u002Fblob\u002Fmain\u002F_Product-Apps\u002Ffrom-dosesync\u002Fapp-paywall-pilot\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fvitalikpestov\u002FSkills-Catalog\u002Fblob\u002Fmain\u002F_Product-Apps\u002Ffrom-dosesync\u002Fapp-paywall-pilot\u002FSKILL.md",[223,226],{"categoryNo":224,"categoryName":225,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":227,"categoryName":228,"taxonomyType":127,"taxonomyTypeDesc":128},"01JBSEEDCAT000000000000032","设计师",[230,231,232,233,234,235,236,237,238,37,36,239,35,240,241,242,243,244,245,246],"app","paywall","app paywall pilot","paid","paywalls","prices","choose","flows","fix","app store","review","audit","ux","subscription","mobile","my","calculate",{"skillNo":248,"name":249,"nameZh":6,"description":250,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":251,"licenseFileUrl":252,"sourceHtmlUrl":253,"categories":254,"keywords":257,"publishedAt":44},"01M71TWET8GFKEB7ZHJPMQX29V","figma","Use the Figma MCP server to fetch design context, screenshots, variables, and assets from Figma, and to translate Figma nodes into production code. Trigger when a task involves Figma URLs, node IDs, design-to-code implementation, or Figma MCP setup and troubleshooting.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fvitalikpestov\u002FSkills-Catalog\u002Fblob\u002Fmain\u002F_Product-Apps\u002Ffigma\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fvitalikpestov\u002FSkills-Catalog\u002Fblob\u002Fmain\u002F_Product-Apps\u002Ffigma\u002FSKILL.md",[255,256],{"categoryNo":122,"categoryName":123,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":227,"categoryName":228,"taxonomyType":127,"taxonomyTypeDesc":128},[249,258,259,260,261,166,36,138,169,35,262,263,172,264,142,265,266,267,268,269],"fetch","ids","mcp setup","translate","mcp server","Variables","task","Nodes","figma mcp","code implementation","node","assets"]