정보
이 스킬은 확장 가능한 B2B 아웃바운드 영업 시스템을 구축하기 위한 Predictable Revenue 프레임워크를 제공합니다. 콜드 이메일, 영업 파이프라인 또는 처음부터 영업팀을 구축하는 것에 대한 질의가 트리거될 때, 개발자에게 전문 영업 역할(SDR, AE, CSM) 설정, 리드 자격 평가(ANUM), 파이프라인 수학에 대한 지침을 안내합니다. 주요 기능으로는 세 가지 리드 유형(씨앗/그물/창) 처리와 레퍼럴-이메일 방식을 포함합니다.
빠른 설치
Claude Code
추천npx skills add wondelai/skills -a claude-code/plugin add https://github.com/wondelai/skillsgit clone https://github.com/wondelai/skills.git ~/.claude/skills/predictable-revenueClaude Code에서 이 명령을 복사하여 붙여넣어 스킬을 설치하세요
문서
Predictable Revenue Framework
A systematic approach to building a scalable, predictable B2B sales machine — the outbound prospecting system that helped Salesforce add $100M in recurring revenue.
Core Principle
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.
Scoring
Goal: 10/10. Score a sales process 0-10 by awarding 2 points for each of the five Quick Diagnostic rows it satisfies (prospecting/closing 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/10.
The Three Types of Leads
Not all leads are equal — treat them differently.
| Type | Source | Conversion | Cost | Example |
|---|---|---|---|---|
| Seeds | Word of mouth, referrals, organic | Highest | Lowest (takes time) | Customer referral, NPS-driven |
| Nets | Marketing campaigns, inbound | Medium | Medium | Content, SEO, webinars |
| Spears | Outbound prospecting | Lower but predictable | Higher (people-intensive) | Cold Calling 2.0 |
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).
See references/lead-types.md when deciding where to invest — it sizes the seeds/nets/spears budget split by company stage.
Sales Role Specialization
The #1 principle: separate prospecting from closing. When AEs prospect and close, they hate prospecting and pipeline becomes feast-or-famine.
| Role | Focus | Metrics |
|---|---|---|
| SDR (Sales Development Rep) | Outbound prospecting → qualified opportunities | Qualified meetings/month |
| MDR (Market Development Rep) | Inbound lead qualification | Qualified leads/month |
| AE (Account Executive) | Close deals | Revenue closed, win rate |
| CSM (Customer Success Manager) | Retain and grow accounts | Retention, expansion revenue |
SDR (Sales Development Rep)
Generate 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.
AE (Account Executive)
Close 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.
CSM (Customer Success Manager)
Retain and grow accounts: onboard, drive adoption, surface expansion opportunities, prevent churn. Measure net revenue retention, churn rate, expansion revenue, and NPS/CSAT.
The virtuous cycle: SDR generates pipeline → AE closes → CSM retains/grows → happy customer refers (Seeds).
See references/roles.md when defining a new role or org chart — it has full charters, career paths, and hiring profiles for each role.
Cold Calling 2.0
Outbound prospecting that replaces traditional cold calling, which fails on every front: 1-3% connection rate, gatekeepers, brand damage, no scalability.
1. Build list → 2. Send mass email → 3. Get referral → 4. Call the referral → 5. Qualify
Step 1: Build Target Account List
Define your Ideal Customer Profile (company size, industry, tech stack, geography, pain points), then build the list via LinkedIn Sales Navigator, ZoomInfo/Apollo/Clearbit, or industry directories. Target 200-500 accounts per SDR per quarter.
Step 2: The Referral Email
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/3/7/14/30 sequence bodies, open references/cold-calling-2.md.
Step 3: Follow Up
| Day | Action |
|---|---|
| 1 | Send referral email |
| 3 | Follow up if no response |
| 7 | Second follow-up (different angle) |
| 14 | Break-up email ("Should I close your file?") |
| 30 | Re-engage (new trigger event or content) |
The break-up email on Day 14 often draws the highest response in the sequence — people respond to losing the opportunity (scarcity).
Step 4: Qualify with ANUM
| Criteria | Question | Strong Signal | Weak Signal |
|---|---|---|---|
| Authority | Can this person decide? | Decision maker or strong influencer | No buying power |
| Need | Do they have the problem you solve? | Active pain, seeking solutions | "Nice to have" |
| Urgency | When must they solve it? | This quarter, budget allocated | "Someday" |
| Money | Can they afford it? | Budget exists, within range | No budget, too expensive |
Call 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).
Step 5: Hand Off to AE
Include 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.
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.
See references/qualification.md when running the ANUM discovery call — it has the full discovery question bank per criterion.
Pipeline Math
Work backward from the revenue goal:
Revenue Goal ÷ Average Deal Size = Deals Needed
Deals Needed ÷ Win Rate = Opportunities Needed
Opportunities Needed ÷ SDR Conversion = Prospects Needed
Prospects Needed ÷ Response Rate = Emails Needed
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/month).
| Metric | Benchmark |
|---|---|
| Emails per SDR per day | 50-100 |
| Response rate | 9-15% |
| Qualified opportunities per SDR per month | 10-20 |
| AE demo-to-close rate | 20-30% |
| Average sales cycle | 30-90 days |
See references/pipeline-math.md when sizing the SDR team to a revenue target — it has the full capacity-planning and revenue-modeling templates.
Building the Sales Development Team
See references/case-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.
Hiring SDRs
Hire 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.
SDR Ramp Time
| Phase | Timeline | Expectations |
|---|---|---|
| Training | Weeks 1-2 | Product knowledge, tools, process |
| Shadowing | Weeks 3-4 | Observe experienced SDRs, practice |
| Ramping | Months 2-3 | 50% of quota |
| Full quota | Month 4+ | 100% of quota |
Expect 3-4 months to full productivity.
SDR Compensation
Base + variable, typically 60/40 or 70/30. Pay variable per qualified opportunity generated, with bonuses for opportunities that close and for exceeding quota.
See references/team-building.md when hiring or building the comp plan — it has interview scorecards, the onboarding curriculum, and detailed compensation structures.
Metrics and Dashboards
Leading Indicators (Predictive)
Emails sent per SDR per day, response rate, meetings booked per week, qualified opportunities per month, pipeline value generated.
Lagging Indicators (Results)
Revenue closed, win rate, average deal size, sales cycle length, customer acquisition cost (CAC).
Efficiency Metrics
Cost per qualified opportunity, SDR:AE ratio (typically 2-3 SDRs per AE), LTV:CAC (target >3:1), payback period.
Cadence: daily activity metrics → weekly pipeline → monthly revenue → quarterly efficiency.
See references/metrics.md when building the sales dashboard — it has KPI definitions, formulas, and dashboard layouts by cadence.
Common Mistakes
| Mistake | Why It Fails | Fix |
|---|---|---|
| AEs prospecting | Feast-or-famine pipeline | Hire dedicated SDRs |
| Long, pitchy emails | Low response rate | Short, referral-focused emails |
| No ICP definition | Effort wasted on wrong accounts | Define ICP before hiring SDRs |
| Too few SDRs | Not enough pipeline | Work backward from revenue goal |
| No hand-off process | Leads fall through cracks | Standardize SDR→AE handoff |
| Measuring activity, not results | Busy but not productive | Track qualified opportunities, not emails |
Quick Diagnostic
Audit any B2B sales process:
| Question | If No | Action |
|---|---|---|
| Are prospecting and closing separated? | SDRs doing both = bottleneck | Create dedicated SDR role |
| Is there a defined outbound process? | Ad-hoc prospecting | Implement Cold Calling 2.0 |
| Can you predict pipeline 3 months out? | Revenue is unpredictable | Build pipeline math model |
| Do you know your lead type mix? | Over-reliance on one source | Balance seeds, nets, spears |
| Is SDR→AE handoff standardized? | Leads lost in transition | Create handoff checklist |
Further Reading
For the complete system:
- "Predictable Revenue" by Aaron Ross & Marylou Tyler
- "From Impossible to Inevitable" by Aaron Ross & Jason Lemkin (scaling to $100M+ ARR)
About the Author
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.
GitHub 저장소
자주 묻는 질문
predictable-revenue Skill이란 무엇인가요?
predictable-revenue은(는) wondelai이(가) 만든 Claude Skill입니다. Skill은 Claude가 필요할 때 불러오는 지침과 리소스를 묶어 추가 프롬프트 없이 predictable-revenue 관련 작업을 수행할 수 있게 합니다.
predictable-revenue은(는) 어떻게 설치하나요?
이 페이지의 설치 명령을 사용하세요. predictable-revenue을(를) Claude Code 플러그인으로 추가하거나 저장소를 skills 디렉터리에 복제한 다음 Claude를 다시 시작해 Skill을 불러옵니다.
predictable-revenue은(는) 어떤 카테고리에 속하나요?
predictable-revenue은(는) 메타 카테고리에 속합니다.
predictable-revenue은(는) 무료로 사용할 수 있나요?
네. predictable-revenue은(는) AIMCP에 등록되어 있으며 무료로 설치할 수 있습니다.
연관 스킬
이 스킬은 콘텐츠 콜렉션(Content Collections)을 위한 프로덕션 검증된 설정을 제공합니다. 콘텐츠 콜렉션은 Markdown/MDX 파일을 Zod 검증이 포함된 타입 안전한 데이터 콜렉션으로 변환해주는 TypeScript 최우선 도구입니다. 블로그, 문서 사이트 또는 콘텐츠 중심의 Vite + React 애플리케이션을 구축할 때 타입 안전성과 자동 콘텐츠 검증을 보장하기 위해 사용하세요. Vite 플러그인 구성과 MDX 컴파일부터 배포 최적화 및 스키마 검증에 이르기까지 모든 것을 다룹니다.
이 스킬은 개발자들이 Polymarket 예측 시장 플랫폼을 활용한 애플리케이션을 구축할 수 있도록 지원하며, 거래 및 시장 데이터를 위한 API 통합 기능을 포함합니다. 또한 WebSocket을 통한 실시간 데이터 스트리밍을 제공하여 실시간 거래와 시장 활동을 모니터링할 수 있습니다. 이를 통해 거래 전략을 구현하거나 실시간 시장 업데이트를 처리하는 도구를 생성하는 데 활용할 수 있습니다.
이 스킬은 개발자들이 명령어, 파일, LSP 작업 등 25개 이상의 이벤트 유형에 연결되는 OpenCode 플러그인을 만들 수 있도록 돕습니다. JavaScript/TypeScript 모듈을 위한 플러그인 구조, 이벤트 API 명세, 구현 패턴을 제공합니다. OpenCode AI 어시스턴트의 라이프사이클을 사용자 정의 이벤트 기반 로직으로 가로채거나, 모니터링하거나, 확장해야 할 때 사용하세요.
SGLang은 RadixAttention 프리픽스 캐싱을 활용하여 JSON, 정규식, 에이전트 워크플로우를 위한 고속 구조화 생성에 특화된 고성능 LLM 서빙 프레임워크입니다. 특히 반복되는 프리픽스가 있는 작업에서 상당히 빠른 추론 속도를 제공하여 복잡한 구조화 출력 및 다중 턴 대화에 이상적입니다. 제약 디코딩이 필요하거나 광범위한 프리픽스 공유가 있는 애플리케이션을 구축할 때는 vLLM과 같은 대안보다 SGLang을 선택하십시오.
