predictable-revenue
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.
What this skill does
# Predictable Revenue Framework
A systematic approach to building a scalable, predictable B2B sales machine. Pioneered 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.
**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.
## Scoring
**Goal: 10/10.** When evaluating or building a sales process, rate 0-10 based on predictability, specialization, and process maturity. A 10/10 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/10.
## The Three Types of Leads
**Not all leads are created equal. Treat them differently.**
| Type | Source | Conversion | Cost | Example |
|------|--------|------------|------|---------|
| **Seeds** | Word of mouth, referrals, organic | Highest (best quality) | Lowest (takes time) | Customer referral, NPS-driven |
| **Nets** | Marketing campaigns, inbound | Medium | Medium | Content marketing, SEO, webinars |
| **Spears** | Outbound prospecting | Lower (but predictable) | Higher (people-intensive) | Cold Calling 2.0, targeted outreach |
**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.
**Revenue mix:**
- **Seeds:** Invest in customer success, NPS, referral programs
- **Nets:** Invest in content, SEO, paid acquisition
- **Spears:** Invest in SDR team, Cold Calling 2.0
See: [references/lead-types.md](references/lead-types.md) for lead source strategy and investment allocation.
## Sales Role Specialization
**The #1 principle: Separate prospecting from closing.**
**Traditional (broken) model:**
- AEs prospect AND close
- Result: AEs hate prospecting, pipeline is feast-or-famine
**Predictable Revenue model:**
| 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 rate, expansion revenue |
### SDR (Sales Development Rep)
**Mission:** Generate qualified pipeline through outbound prospecting.
**Focus:**
- Research target accounts
- Write personalized Cold Calling 2.0 emails
- Get referred to the right person
- Qualify opportunities (ANUM)
- Pass qualified opportunities to AEs
**Not their job:**
- Close deals
- Handle inbound leads
- Manage existing customers
**Metrics:**
- Qualified opportunities generated per month
- Response rate to outbound emails
- Meetings booked per week
- Pipeline value generated
**SDR capacity:** One SDR typically generates 10-20 qualified opportunities per month.
### AE (Account Executive)
**Mission:** Close deals from qualified pipeline.
**Focus:**
- Run discovery calls
- Demo and present solutions
- Negotiate and close
- Hand off to CSM
**Not their job:**
- Prospect for new leads (this is SDR's job)
- Qualify inbound leads (this is MDR's job)
- Manage post-sale relationships (CSM's job)
**Metrics:**
- Revenue closed
- Win rate
- Average deal size
- Sales cycle length
### CSM (Customer Success Manager)
**Mission:** Retain customers and grow accounts.
**Focus:**
- Onboard new customers
- Drive adoption and engagement
- Identify expansion opportunities
- Prevent churn
**Metrics:**
- Net revenue retention
- Churn rate
- Expansion revenue
- NPS / CSAT
**The virtuous cycle:**
```
SDR generates pipeline → AE closes → CSM retains/grows → Happy customer refers (Seeds)
```
See: [references/roles.md](references/roles.md) for role definitions, career paths, and hiring profiles.
## Cold Calling 2.0
**The outbound prospecting methodology that replaces traditional cold calling.**
**Why traditional cold calling fails:**
- Gatekeepers block calls
- Decision makers don't answer phones
- 1-3% connection rate
- Damages brand
- Not scalable
**Cold Calling 2.0 process:**
```
1. Build list → 2. Send mass email → 3. Get referral → 4. Call the referral → 5. Qualify
```
### Step 1: Build Target Account List
**Ideal Customer Profile (ICP):**
- Company size (employees, revenue)
- Industry
- Technology stack
- Geography
- Pain points
**Build list using:**
- LinkedIn Sales Navigator
- ZoomInfo / Apollo / Clearbit
- Company websites
- Industry directories
**Target:** 200-500 accounts per SDR per quarter
### Step 2: The Referral Email
**The core innovation:** Don't email the decision maker directly. Email above them and ask for a referral down.
**Why it works:**
- Senior people are helpful (they forward emails)
- Referrals have 3-5x higher response rate
- Creates warm introduction from within the company
**The email template:**
**Subject:** Quick question
**Body:**
> Hi [Name],
>
> 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.
>
> We help [companies like theirs] with [specific value prop].
>
> Would you mind pointing me to the right person to talk to?
>
> Thanks,
> [Your name]
**Key elements:**
- Short (< 100 words)
- No pitch, no attachments, no links
- Asks for referral, not a meeting
- Specific about what you do
- Easy to forward
**Response rate:** 9-15% (vs. 1-3% for traditional cold emails)
### Step 3: Follow Up
**Follow-up sequence:**
| Day | Action |
|-----|--------|
| Day 1 | Send referral email |
| Day 3 | Follow up if no response |
| Day 7 | Second follow up (different angle) |
| Day 14 | Break-up email ("Should I close your file?") |
| Day 30 | Re-engage (new trigger event or content) |
**Break-up email example:**
> Hi [Name],
>
> I haven't heard back from you. I don't want to be a pest.
>
> Should I close your file, or would it make sense to chat?
>
> [Your name]
**Why break-up emails work:** People respond to the threat of losing access/opportunity (scarcity principle).
### Step 4: Qualify with ANUM
**ANUM qualification framework:**
| Criteria | Question | Strong Signal | Weak Signal |
|----------|----------|---------------|-------------|
| **A**uthority | Can this person decide? | Decision maker or strong influencer | No buying power |
| **N**eed | Do they have the problem you solve? | Active pain, looking for solutions | "Nice to have" |
| **U**rgency | When do they need to solve it? | This quarter, budget allocated | "Someday" |
| **M**oney | Can they afford it? | Budget exists, within range | No budget, too expensive |
**Qualification call structure:**
1. Build rapport (2 min)
2. Set agenda ("I want to understand your situation and see if there's a fit")
3. Discovery questions (10-15 min)
4. ANUM qualification (built into discovery)
5. Next steps (if qualified → schedule AE demo)
### Step 5: Hand Off to AE
**The handoff must include:**
- Account background and ICP match
- Contact details and role
- Pain points discovered
- ANUM qualification notes
- Agreed next steps
- Any competitive intel
**Handoff meeting:** SDR introduces AE on a brief 3-way call or email, then drops off.
See: [references/cold-calling-2.md](references/cold-calling-2.md) for email templates, sequences, and scripts.
## Pipeline Math
**The math of predictable revenue:**
```
Revenue Goal ÷ Average Deal Size = Deals Needed
Deals Needed ÷ Win Rate = Opportunities Needed
Opportunities Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.