[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7B9CDH0WHFX2DA6KT08T2K4":3,"skill-same:01M7B9CDH0WHFX2DA6KT08T2K4":82},{"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":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":14,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7B9CDH0WHFX2DA6KT08T2K4","predictable-revenue",null,"Build a scalable outbound B2B sales machine with specialized roles (SDR, AE, CSM). Use when the user mentions \"outbound sales\", \"Cold Calling 2.0\", \"cold email sequences\", \"sales pipeline\", \"SDR process\", \"sales development\", \"build an outbound sales team\", or \"fill my pipeline\". Also trigger when setting up a B2B SaaS sales team from scratch or building a lead-qualification framework to improve close rates. Covers the three lead types (seeds\u002Fnets\u002Fspears), role specialization, the referral-email method, ANUM qualification, and pipeline math. For offer design, see hundred-million-offers. For persuasion science, see influence-psychology.","Div0011\u002FFrontend-Pipeline","Div0011","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F198384399?v=4","01M7AX16GDZ3959RM6WMDTTFV4","Div","01M7AX16HF6EPV40MA8G0G0JRC",0,"MIT","https:\u002F\u002Fgithub.com\u002FDiv0011\u002FFrontend-Pipeline\u002Fblob\u002Fmain\u002Fartifacts\u002Fskills\u002Fwondelai-skills\u002Fpredictable-revenue\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: predictable-revenue\ndescription: 'Build a scalable outbound B2B sales machine with specialized roles (SDR, AE, CSM). Use when the user mentions \"outbound sales\", \"Cold Calling 2.0\", \"cold email sequences\", \"sales pipeline\", \"SDR process\", \"sales development\", \"build an outbound sales team\", or \"fill my pipeline\". Also trigger when setting up a B2B SaaS sales team from scratch or building a lead-qualification framework to improve close rates. Covers the three lead types (seeds\u002Fnets\u002Fspears), role specialization, the referral-email method, ANUM qualification, and pipeline math. For offer design, see hundred-million-offers. For persuasion science, see influence-psychology.'\nlicense: MIT\nmetadata:\n  author: wondelai\n  version: \"1.4.0\"\n---\n\n# Predictable Revenue Framework\n\nA systematic approach to building a scalable, predictable B2B sales machine — 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. Traditional cold calling is dead; Cold Calling 2.0 (mass, personalized cold emails that generate referrals to the right person) is the new outbound.\n\n## Scoring\n\n**Goal: 10\u002F10.** Score a sales process 0-10 by awarding 2 points for each of the five [Quick Diagnostic](#quick-diagnostic) rows it satisfies (prospecting\u002Fclosing separated, defined outbound process, 3-month pipeline predictability, known lead-type mix, standardized SDR→AE handoff). Bands: **9-10** = role separation plus a repeatable process that predicts pipeline; **5-6** = some specialization but ad-hoc prospecting or unpredictable pipeline; **≤3** = one person prospects and closes, revenue depends on heroics. Always give the current score and the specific diagnostic rows blocking 10\u002F10.\n\n## The Three Types of Leads\n\n**Not all leads are equal — treat them differently.**\n\n| Type | Source | Conversion | Cost | Example |\n|------|--------|------------|------|---------|\n| **Seeds** | Word of mouth, referrals, organic | Highest | Lowest (takes time) | Customer referral, NPS-driven |\n| **Nets** | Marketing campaigns, inbound | Medium | Medium | Content, SEO, webinars |\n| **Spears** | Outbound prospecting | Lower but predictable | Higher (people-intensive) | Cold Calling 2.0 |\n\n**Key insight:** Most companies over-invest in nets and under-invest in spears; seeds are the best but can't be manufactured quickly. Invest accordingly — customer success and referral programs (seeds), content and paid acquisition (nets), SDR team (spears).\n\nSee [references\u002Flead-types.md](references\u002Flead-types.md) when deciding where to invest — it sizes the seeds\u002Fnets\u002Fspears budget split by company stage.\n\n## Sales Role Specialization\n\n**The #1 principle: separate prospecting from closing.** When AEs prospect and close, they hate prospecting and pipeline becomes feast-or-famine.\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, expansion revenue |\n\n### SDR (Sales Development Rep)\n\nGenerate qualified pipeline: research target accounts, send Cold Calling 2.0 emails, get referred to the right person, qualify with ANUM, pass to AEs. Not their job: closing, inbound leads, or existing customers. One SDR typically generates 10-20 qualified opportunities per month — measure opportunities, response rate, meetings booked, and pipeline value.\n\n### AE (Account Executive)\n\nClose deals from qualified pipeline: run discovery, demo, negotiate, close, hand off to CSM. Not their job: prospecting (SDR), inbound qualification (MDR), or post-sale management (CSM). Measure revenue closed, win rate, average deal size, and sales cycle length.\n\n### CSM (Customer Success Manager)\n\nRetain and grow accounts: onboard, drive adoption, surface expansion opportunities, prevent churn. Measure net revenue retention, churn rate, expansion revenue, and NPS\u002FCSAT.\n\n**The virtuous cycle:** SDR generates pipeline → AE closes → CSM retains\u002Fgrows → happy customer refers (Seeds).\n\nSee [references\u002Froles.md](references\u002Froles.md) when defining a new role or org chart — it has full charters, career paths, and hiring profiles for each role.\n\n## Cold Calling 2.0\n\n**Outbound prospecting that replaces traditional cold calling**, which fails on every front: 1-3% connection rate, gatekeepers, brand damage, no scalability.\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\nDefine your Ideal Customer Profile (company size, industry, tech stack, geography, pain points), then build the list via LinkedIn Sales Navigator, ZoomInfo\u002FApollo\u002FClearbit, or industry directories. 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 — email above them and ask for a referral down.** Senior people forward emails, and referrals get 3-5x higher response because the introduction comes from inside the company. The email asks one thing — \"who is the right person?\" — under 100 words, no pitch, no attachments, no links, easy to forward. Response rate: 9-15% vs. 1-3% for traditional cold emails. For the verbatim template, subject-line open-rate table, and the full Day 1\u002F3\u002F7\u002F14\u002F30 sequence bodies, open [references\u002Fcold-calling-2.md](references\u002Fcold-calling-2.md).\n\n### Step 3: Follow Up\n\n| Day | Action |\n|-----|--------|\n| 1 | Send referral email |\n| 3 | Follow up if no response |\n| 7 | Second follow-up (different angle) |\n| 14 | Break-up email (\"Should I close your file?\") |\n| 30 | Re-engage (new trigger event or content) |\n\nThe **break-up email** on Day 14 often draws the highest response in the sequence — people respond to losing the opportunity (scarcity).\n\n### Step 4: Qualify with ANUM\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, seeking solutions | \"Nice to have\" |\n| **U**rgency | When must they solve it? | This quarter, budget allocated | \"Someday\" |\n| **M**oney | Can they afford it? | Budget exists, within range | No budget, too expensive |\n\nCall structure: rapport (2 min) → set agenda (\"understand your situation, see if there's a fit\") → discovery questions with ANUM built in (10-15 min) → next steps (if qualified, schedule AE demo).\n\n### Step 5: Hand Off to AE\n\nInclude account background and ICP match, contact details and role, pain points, ANUM notes, agreed next steps, and competitive intel. SDR introduces AE on a brief 3-way call or email, then drops off.\n\n**Ethical boundary:** Comply with spam laws (CAN-SPAM, GDPR) and honor opt-outs immediately — including removing a hostile \"stop emailing me\" from the sequence on the spot, not at the next scheduled touch.\n\nSee [references\u002Fqualification.md](references\u002Fqualification.md) when running the ANUM discovery call — it has the full discovery question bank per criterion.\n\n## Pipeline Math\n\nWork backward from the revenue goal:\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:** $1M ARR ÷ $20K deals = 50 deals; ÷ 25% win rate = 200 opportunities; at 10% response rate and 10% response-to-qualified conversion = 20,000 emails ≈ 2-3 SDRs (each sends 300-500\u002Fmonth).\n\n| Metric | Benchmark |\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) when sizing the SDR team to a revenue target — it has the full capacity-planning and revenue-modeling templates.\n\n## Building the Sales Development Team\n\nSee [references\u002Fcase-studies.md](references\u002Fcase-studies.md) when you want a worked precedent for standing up or scaling the machine — it walks through Salesforce, HubSpot, and other implementations with starting state, results, and failure modes.\n\n### Hiring SDRs\n\nHire for coachability (the most important trait), curiosity, strong writing, resilience, and organization — experience is optional. Source recent graduates, career changers, and internal transfers. Career path: SDR (6-18 months) → Senior SDR → AE or SDR Manager.\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 quota |\n| Full quota | Month 4+ | 100% of quota |\n\nExpect 3-4 months to full productivity.\n\n### SDR Compensation\n\nBase + variable, typically 60\u002F40 or 70\u002F30. Pay variable per qualified opportunity generated, with bonuses for opportunities that close and for exceeding quota.\n\nSee [references\u002Fteam-building.md](references\u002Fteam-building.md) when hiring or building the comp plan — it has interview scorecards, the onboarding curriculum, and detailed compensation structures.\n\n## Metrics and Dashboards\n\n### Leading Indicators (Predictive)\n\nEmails sent per SDR per day, response rate, meetings booked per week, qualified opportunities per month, pipeline value generated.\n\n### Lagging Indicators (Results)\n\nRevenue closed, win rate, average deal size, sales cycle length, customer acquisition cost (CAC).\n\n### Efficiency Metrics\n\nCost per qualified opportunity, SDR:AE ratio (typically 2-3 SDRs per AE), LTV:CAC (target >3:1), payback period.\n\n**Cadence:** daily activity metrics → weekly pipeline → monthly revenue → quarterly efficiency.\n\nSee [references\u002Fmetrics.md](references\u002Fmetrics.md) when building the sales dashboard — it has KPI definitions, formulas, and dashboard layouts by cadence.\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** | Effort wasted on wrong accounts | Define ICP before hiring SDRs |\n| **Too few SDRs** | Not enough pipeline | 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 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## Further Reading\n\nFor 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, and co-founded Predictable Revenue Inc. His book *Predictable Revenue* — known as \"The Bible of Outbound Sales\" — made Cold Calling 2.0 the standard for B2B outbound prospecting.\n","# Predictable Revenue Framework\n\nA systematic approach to building a scalable, predictable B2B sales machine — 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. Traditional cold calling is dead; Cold Calling 2.0 (mass, personalized cold emails that generate referrals to the right person) is the new outbound.\n\n## Scoring\n\n**Goal: 10\u002F10.** Score a sales process 0-10 by awarding 2 points for each of the five [Quick Diagnostic](#quick-diagnostic) rows it satisfies (prospecting\u002Fclosing separated, defined outbound process, 3-month pipeline predictability, known lead-type mix, standardized SDR→AE handoff). Bands: **9-10** = role separation plus a repeatable process that predicts pipeline; **5-6** = some specialization but ad-hoc prospecting or unpredictable pipeline; **≤3** = one person prospects and closes, revenue depends on heroics. Always give the current score and the specific diagnostic rows blocking 10\u002F10.\n\n## The Three Types of Leads\n\n**Not all leads are equal — treat them differently.**\n\n| Type | Source | Conversion | Cost | Example |\n|------|--------|------------|------|---------|\n| **Seeds** | Word of mouth, referrals, organic | Highest | Lowest (takes time) | Customer referral, NPS-driven |\n| **Nets** | Marketing campaigns, inbound | Medium | Medium | Content, SEO, webinars |\n| **Spears** | Outbound prospecting | Lower but predictable | Higher (people-intensive) | Cold Calling 2.0 |\n\n**Key insight:** Most companies over-invest in nets and under-invest in spears; seeds are the best but can't be manufactured quickly. Invest accordingly — customer success and referral programs (seeds), content and paid acquisition (nets), SDR team (spears).\n\nSee [references\u002Flead-types.md](references\u002Flead-types.md) when deciding where to invest — it sizes the seeds\u002Fnets\u002Fspears budget split by company stage.\n\n## Sales Role Specialization\n\n**The #1 principle: separate prospecting from closing.** When AEs prospect and close, they hate prospecting and pipeline becomes feast-or-famine.\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, expansion revenue |\n\n### SDR (Sales Development Rep)\n\nGenerate qualified pipeline: research target accounts, send Cold Calling 2.0 emails, get referred to the right person, qualify with ANUM, pass to AEs. Not their job: closing, inbound leads, or existing customers. One SDR typically generates 10-20 qualified opportunities per month — measure opportunities, response rate, meetings booked, and pipeline value.\n\n### AE (Account Executive)\n\nClose deals from qualified pipeline: run discovery, demo, negotiate, close, hand off to CSM. Not their job: prospecting (SDR), inbound qualification (MDR), or post-sale management (CSM). Measure revenue closed, win rate, average deal size, and sales cycle length.\n\n### CSM (Customer Success Manager)\n\nRetain and grow accounts: onboard, drive adoption, surface expansion opportunities, prevent churn. Measure net revenue retention, churn rate, expansion revenue, and NPS\u002FCSAT.\n\n**The virtuous cycle:** SDR generates pipeline → AE closes → CSM retains\u002Fgrows → happy customer refers (Seeds).\n\nSee [references\u002Froles.md](references\u002Froles.md) when defining a new role or org chart — it has full charters, career paths, and hiring profiles for each role.\n\n## Cold Calling 2.0\n\n**Outbound prospecting that replaces traditional cold calling**, which fails on every front: 1-3% connection rate, gatekeepers, brand damage, no scalability.\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\nDefine your Ideal Customer Profile (company size, industry, tech stack, geography, pain points), then build the list via LinkedIn Sales Navigator, ZoomInfo\u002FApollo\u002FClearbit, or industry directories. 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 — email above them and ask for a referral down.** Senior people forward emails, and referrals get 3-5x higher response because the introduction comes from inside the company. The email asks one thing — \"who is the right person?\" — under 100 words, no pitch, no attachments, no links, easy to forward. Response rate: 9-15% vs. 1-3% for traditional cold emails. For the verbatim template, subject-line open-rate table, and the full Day 1\u002F3\u002F7\u002F14\u002F30 sequence bodies, open [references\u002Fcold-calling-2.md](references\u002Fcold-calling-2.md).\n\n### Step 3: Follow Up\n\n| Day | Action |\n|-----|--------|\n| 1 | Send referral email |\n| 3 | Follow up if no response |\n| 7 | Second follow-up (different angle) |\n| 14 | Break-up email (\"Should I close your file?\") |\n| 30 | Re-engage (new trigger event or content) |\n\nThe **break-up email** on Day 14 often draws the highest response in the sequence — people respond to losing the opportunity (scarcity).\n\n### Step 4: Qualify with ANUM\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, seeking solutions | \"Nice to have\" |\n| **U**rgency | When must they solve it? | This quarter, budget allocated | \"Someday\" |\n| **M**oney | Can they afford it? | Budget exists, within range | No budget, too expensive |\n\nCall structure: rapport (2 min) → set agenda (\"understand your situation, see if there's a fit\") → discovery questions with ANUM built in (10-15 min) → next steps (if qualified, schedule AE demo).\n\n### Step 5: Hand Off to AE\n\nInclude account background and ICP match, contact details and role, pain points, ANUM notes, agreed next steps, and competitive intel. SDR introduces AE on a brief 3-way call or email, then drops off.\n\n**Ethical boundary:** Comply with spam laws (CAN-SPAM, GDPR) and honor opt-outs immediately — including removing a hostile \"stop emailing me\" from the sequence on the spot, not at the next scheduled touch.\n\nSee [references\u002Fqualification.md](references\u002Fqualification.md) when running the ANUM discovery call — it has the full discovery question bank per criterion.\n\n## Pipeline Math\n\nWork backward from the revenue goal:\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:** $1M ARR ÷ $20K deals = 50 deals; ÷ 25% win rate = 200 opportunities; at 10% response rate and 10% response-to-qualified conversion = 20,000 emails ≈ 2-3 SDRs (each sends 300-500\u002Fmonth).\n\n| Metric | Benchmark |\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) when sizing the SDR team to a revenue target — it has the full capacity-planning and revenue-modeling templates.\n\n## Building the Sales Development Team\n\nSee [references\u002Fcase-studies.md](references\u002Fcase-studies.md) when you want a worked precedent for standing up or scaling the machine — it walks through Salesforce, HubSpot, and other implementations with starting state, results, and failure modes.\n\n### Hiring SDRs\n\nHire for coachability (the most important trait), curiosity, strong writing, resilience, and organization — experience is optional. Source recent graduates, career changers, and internal transfers. Career path: SDR (6-18 months) → Senior SDR → AE or SDR Manager.\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 quota |\n| Full quota | Month 4+ | 100% of quota |\n\nExpect 3-4 months to full productivity.\n\n### SDR Compensation\n\nBase + variable, typically 60\u002F40 or 70\u002F30. Pay variable per qualified opportunity generated, with bonuses for opportunities that close and for exceeding quota.\n\nSee [references\u002Fteam-building.md](references\u002Fteam-building.md) when hiring or building the comp plan — it has interview scorecards, the onboarding curriculum, and detailed compensation structures.\n\n## Metrics and Dashboards\n\n### Leading Indicators (Predictive)\n\nEmails sent per SDR per day, response rate, meetings booked per week, qualified opportunities per month, pipeline value generated.\n\n### Lagging Indicators (Results)\n\nRevenue closed, win rate, average deal size, sales cycle length, customer acquisition cost (CAC).\n\n### Efficiency Metrics\n\nCost per qualified opportunity, SDR:AE ratio (typically 2-3 SDRs per AE), LTV:CAC (target >3:1), payback period.\n\n**Cadence:** daily activity metrics → weekly pipeline → monthly revenue → quarterly efficiency.\n\nSee [references\u002Fmetrics.md](references\u002Fmetrics.md) when building the sales dashboard — it has KPI definitions, formulas, and dashboard layouts by cadence.\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** | Effort wasted on wrong accounts | Define ICP before hiring SDRs |\n| **Too few SDRs** | Not enough pipeline | 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 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## Further Reading\n\nFor 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, and co-founded Predictable Revenue Inc. His book *Predictable Revenue* — known as \"The Bible of Outbound Sales\" — made Cold Calling 2.0 the standard for B2B outbound prospecting.\n",{"name":5,"license":15,"metadata":24,"description":7},{"author":25,"version":26},"wondelai","1.4.0","main","ba06aff3a0c008524409a6bdcf301dfe4e8f165b","artifacts\u002Fskills\u002Fwondelai-skills\u002Fpredictable-revenue","https:\u002F\u002Fgithub.com\u002FDiv0011\u002FFrontend-Pipeline","https:\u002F\u002Fgithub.com\u002FDiv0011","B.Tech Computer Engineering undergrad & Full-Stack Developer. Specialized in Generative AI, Next.js, and Python architecture. Building autonomous systems.","2026-09-07 19:51:50",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add Div0011\u002FFrontend-Pipeline --skill predictable-revenue",{"tool":40,"command":41},"bunx","bunx skills add Div0011\u002FFrontend-Pipeline --skill predictable-revenue",{"tool":43,"command":44},"pnpm","pnpm dlx skills add Div0011\u002FFrontend-Pipeline --skill predictable-revenue","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FDiv0011\u002FFrontend-Pipeline\u002Fblob\u002Fmain\u002Fartifacts\u002Fskills\u002Fwondelai-skills\u002Fpredictable-revenue\u002FSKILL.md",true,[48,54,58,62,66,70,74,78],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"references\u002Fcase-studies.md","REFERENCE","参考文档",14733,"https:\u002F\u002Fgithub.com\u002FDiv0011\u002FFrontend-Pipeline\u002Fblob\u002Fmain\u002Fartifacts\u002Fskills\u002Fwondelai-skills\u002Fpredictable-revenue\u002Freferences\u002Fcase-studies.md",{"path":55,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":56,"sourceHtmlUrl":57},"references\u002Fcold-calling-2.md",12539,"https:\u002F\u002Fgithub.com\u002FDiv0011\u002FFrontend-Pipeline\u002Fblob\u002Fmain\u002Fartifacts\u002Fskills\u002Fwondelai-skills\u002Fpredictable-revenue\u002Freferences\u002Fcold-calling-2.md",{"path":59,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":60,"sourceHtmlUrl":61},"references\u002Flead-types.md",11290,"https:\u002F\u002Fgithub.com\u002FDiv0011\u002FFrontend-Pipeline\u002Fblob\u002Fmain\u002Fartifacts\u002Fskills\u002Fwondelai-skills\u002Fpredictable-revenue\u002Freferences\u002Flead-types.md",{"path":63,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":64,"sourceHtmlUrl":65},"references\u002Fmetrics.md",13827,"https:\u002F\u002Fgithub.com\u002FDiv0011\u002FFrontend-Pipeline\u002Fblob\u002Fmain\u002Fartifacts\u002Fskills\u002Fwondelai-skills\u002Fpredictable-revenue\u002Freferences\u002Fmetrics.md",{"path":67,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":68,"sourceHtmlUrl":69},"references\u002Fpipeline-math.md",10734,"https:\u002F\u002Fgithub.com\u002FDiv0011\u002FFrontend-Pipeline\u002Fblob\u002Fmain\u002Fartifacts\u002Fskills\u002Fwondelai-skills\u002Fpredictable-revenue\u002Freferences\u002Fpipeline-math.md",{"path":71,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":72,"sourceHtmlUrl":73},"references\u002Fqualification.md",15782,"https:\u002F\u002Fgithub.com\u002FDiv0011\u002FFrontend-Pipeline\u002Fblob\u002Fmain\u002Fartifacts\u002Fskills\u002Fwondelai-skills\u002Fpredictable-revenue\u002Freferences\u002Fqualification.md",{"path":75,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":76,"sourceHtmlUrl":77},"references\u002Froles.md",12938,"https:\u002F\u002Fgithub.com\u002FDiv0011\u002FFrontend-Pipeline\u002Fblob\u002Fmain\u002Fartifacts\u002Fskills\u002Fwondelai-skills\u002Fpredictable-revenue\u002Freferences\u002Froles.md",{"path":79,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":80,"sourceHtmlUrl":81},"references\u002Fteam-building.md",13138,"https:\u002F\u002Fgithub.com\u002FDiv0011\u002FFrontend-Pipeline\u002Fblob\u002Fmain\u002Fartifacts\u002Fskills\u002Fwondelai-skills\u002Fpredictable-revenue\u002Freferences\u002Fteam-building.md",[83,92,99,106,113,120],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":87,"licenseFileUrl":88,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M7B9FY1YN4AX6XSKFY1GEB6F","scrapling-official","Scrape web pages using Scrapling with anti-bot bypass (like Cloudflare Turnstile), stealth headless browsing, spiders framework, adaptive scraping, and JavaScript rendering. Use when asked to scrape, crawl, or extract data from websites; web_fetch fails; the site has anti-bot protections; write Python code to scrape\u002Fcrawl; or write spiders.","BSD-3-Clause","https:\u002F\u002Fgithub.com\u002FDiv0011\u002FFrontend-Pipeline\u002Fblob\u002Fmain\u002Fartifacts\u002Fvendor_references\u002FScrapling\u002Fagent-skill\u002FScrapling-Skill\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FDiv0011\u002FFrontend-Pipeline\u002Fblob\u002Fmain\u002Fartifacts\u002Fvendor_references\u002FScrapling\u002Fagent-skill\u002FScrapling-Skill\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":19},"01M7B9FNH5E90KCTDK1MABVBAX","working-with-legacy-code","Safely change and test untested codebases using Feathers' \"Working Effectively with Legacy Code\". Use when the user mentions \"legacy code\", \"no tests\", \"untested codebase\", \"how do I test this\", \"seams\", \"characterization tests\", \"golden master\", \"sprout method\", \"afraid to change this code\", \"monster method\", \"dependency breaking\", or \"inherited a messy codebase\". Also trigger when changing code without tests safely, getting a class under test when constructors, statics, or singletons block it, adding features to tangled modules, or planning incremental test coverage for an old codebase. Covers the legacy-code change algorithm, seams, characterization tests, sprout\u002Fwrap, and dependency-breaking techniques. For refactoring code that already has tests, see refactoring-patterns. For day-to-day code quality, see clean-code.","https:\u002F\u002Fgithub.com\u002FDiv0011\u002FFrontend-Pipeline\u002Fblob\u002Fmain\u002Fartifacts\u002Fskills\u002Fwondelai-skills\u002Fworking-with-legacy-code\u002FSKILL.md",[],[],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":19},"01M7B9FDRG6DG9PKTEMKZXHCXY","web-typography","Select, pair, and implement typefaces for web projects. Use when the user mentions \"font pairing\", \"which typeface\", \"line height\", \"responsive typography\", \"web font loading\", \"type hierarchy\", \"variable fonts\", \"FOUT\u002FFOIT\", \"typographic scale\", or \"the text is hard to read\". Also trigger when choosing between system fonts and web fonts, optimizing font-loading performance, or designing readable long-form content. Covers readability evaluation, CSS implementation, and performance optimization. For overall UI design systems, see refactoring-ui. For dramatic typographic experiences, see top-design.","https:\u002F\u002Fgithub.com\u002FDiv0011\u002FFrontend-Pipeline\u002Fblob\u002Fmain\u002Fartifacts\u002Fskills\u002Fwondelai-skills\u002Fweb-typography\u002FSKILL.md",[],[],{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":19},"01M7B9F6P2Y8R413YJ3WX339HH","ux-heuristics","Evaluate and improve interface usability using heuristic analysis. Use when the user mentions \"usability audit\", \"users are confused\", \"form usability\", \"navigation problems\", \"Nielsen heuristics\", \"cognitive walkthrough\", or \"is this easy to use\". Also trigger when reviewing a design for usability issues, improving form-completion rates, or evaluating information architecture and navigation. Covers Krug's laws, Nielsen's 10 heuristics, severity ratings, dark-pattern recognition, and accessibility. For visual design fixes, see refactoring-ui. For conversion-focused audits, see cro-methodology.","https:\u002F\u002Fgithub.com\u002FDiv0011\u002FFrontend-Pipeline\u002Fblob\u002Fmain\u002Fartifacts\u002Fskills\u002Fwondelai-skills\u002Fux-heuristics\u002FSKILL.md",[],[],{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":19},"01M7B9EZVNSBCXJFQRFVX29NR5","traction-eos","Implement the Entrepreneurial Operating System (EOS) to align vision and execution across a company. Use when the user mentions \"EOS\", \"Entrepreneurial Operating System\", \"V\u002FTO\", \"quarterly rocks\", \"Level 10 meetings\", \"accountability chart\", \"IDS process\", \"my company feels chaotic\", \"we keep having the same problems\", or \"get the whole team aligned\". Also trigger when a growing company needs meeting structure, goal-setting frameworks, or a systematic way to solve recurring organizational issues. Covers the six EOS components: Vision, People, Data, Issues, Process, Traction. For team motivation design, see drive-motivation. For lean experimentation, see lean-startup.","https:\u002F\u002Fgithub.com\u002FDiv0011\u002FFrontend-Pipeline\u002Fblob\u002Fmain\u002Fartifacts\u002Fskills\u002Fwondelai-skills\u002Ftraction-eos\u002FSKILL.md",[],[],{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":126,"publishedAt":19},"01M7B9ESTNAY9WY8NFW590DWGA","top-design","Create award-winning, immersive web experiences at the level of Awwwards-featured agencies. Use when the user mentions \"Awwwards quality\", \"make my site stunning\", \"scroll animations\", \"parallax storytelling\", \"cinematic web design\", \"portfolio site\", or \"brand experience\". Also trigger when elevating a standard landing page into a memorable digital experience. Covers dramatic typography, purposeful motion, scroll-based composition, and performance-optimized animation. For foundational UI, see refactoring-ui. For type selection, see web-typography.","https:\u002F\u002Fgithub.com\u002FDiv0011\u002FFrontend-Pipeline\u002Fblob\u002Fmain\u002Fartifacts\u002Fskills\u002Fwondelai-skills\u002Ftop-design\u002FSKILL.md",[],[]]