Skill: Raskin Narrative BP

Meta

• Style: Story-driven, urgency-led, theatrical
• Best For: Pitch competitions; Demo Day; investor meetings where you present live; B2B sales decks
• Source: Andy Raskin (Silicon Valley's top pitch coach)
• Output Length: 5 narrative beats, not slides
• Tone: Dramatic, prophetic, urgent

Core Philosophy

The best pitch doesn't start with you. It starts with the world.

"The greatest sales deck I've ever seen didn't mention the company's product until slide 14." — Andy Raskin

Investors don't invest in companies. They invest in inevitability — the feeling that this future is already happening and they'd be foolish to miss it.

The 5 Narrative Beats

Unlike Sequoia's 12 slides or YC's insight-first memo, Raskin's framework is 5 narrative beats. Each beat is a story moment, not an information container.

Beat 1: Name a Big, Changeable Problem (The Setup)

Goal: Create tension. The investor must feel that something is wrong with the world.

Rule: Never start with your company. Start with a shift in the world that creates pain.

Techniques:

• The statistic that stuns: A number so large it demands attention.
• The anecdote that hurts: A real customer story that makes the investor wince.
• The trend that terrifies: A shift that threatens an entire industry.

Good Example (Statistic):

"$18 billion. That's how much global enterprises lost last year to compliance fines alone. Not fraud. Not cyber attacks. Just paperwork that was filed incorrectly. And that number has doubled in the last 3 years."

Good Example (Anecdote):

"Last month, a mid-size manufacturer in Shenzhen lost a $2 million order. Not because their product was bad. Not because their price was high. Because their compliance paperwork took 11 days, and the buyer went with a competitor who could do it in 3. Eleven days. For paperwork."

Good Example (Trend):

"In 2019, 73% of CFOs said relationship banking was their top priority. Today, 89% say cash flow visibility is. That's not a preference shift. That's a survival shift. And most banks haven't noticed."

Check:

• The first 30 seconds contain no mention of your company
• The investor feels an emotion (shock, fear, urgency)
• The problem is big enough to justify a billion-dollar company

Beat 2: Show That the Problem Will Inevitably Be Solved (The Promise)

Goal: Create hope. Show that someone is going to solve this, and soon.

Technique: Point to a company in an adjacent space that has already won by solving a similar problem. This proves the pattern.

Good Example:

"Stripe didn't just build better payment infrastructure. They made developers the heroes of payments. The result? $95 billion company. Compliance is the next infrastructure layer that desperately needs a Stripe. The only question is: who builds it?"

Alternative Technique: Show regulatory or technological tailwinds that make the solution inevitable.

Good Example:

"PSD2 in Europe. Open banking APIs in the UK. Regulatory sandboxes in Singapore. Governments worldwide are mandating data sharing between financial institutions. The compliance walls are coming down. Someone is going to build the router that connects them."

Check:

• You've named a comparable success (proves the pattern)
• The investor thinks "of course someone will solve this"
• The inevitable solution is a platform, not a feature

Beat 3: Introduce Your Product as the Inevitable Solution (The Reveal)

Goal: Make your product feel like the only logical answer.

Technique: Don't describe features. Describe capabilities — what your product makes possible that was impossible before.

Good Example:

"ChainLedger is the compliance settlement network. Instead of 3 banks independently verifying the same KYC data, we verify once and share the attestation across the network. What used to take 7 days now takes 4 hours. What used to cost $2,500 now costs $200. And here's the key: we're not replacing banks. We're making them 10x more efficient."

Bad Example:

"ChainLedger is a SaaS platform with AI-powered compliance automation, real-time sanction screening, and automated KYC/KYB workflows."

The Difference:

• Capabilities: "What becomes possible"
• Features: "What we built"

Check:

• You describe capabilities, not features
• There's a before/after that feels magical
• You're not displacing incumbents — you're making them better (removes fear)

Beat 4: Provide Proof (The Evidence)

Goal: Make the inevitable feel real.

Structure:

1. Traction that demonstrates the capability
2. Customer story that validates the transformation
3. Demo (if presenting live)

Good Example (Traction + Story):

"In 6 months, 120 enterprise customers. $50k MRR. 12% MoM growth. But here's the number that matters: our customers' compliance costs dropped 90%, and their settlement times went from 7 days to 4 hours. One customer told us: 'We didn't even know this was possible. We thought 7 days was just the cost of doing business internationally.'"

The Demo Rule: If you're presenting live, show the product. Not a screenshot — the actual product. Walk through one workflow. Make the investor see the magic.

Check:

• The traction metric demonstrates the capability (not just growth)
• The customer quote confirms transformation (not satisfaction)
• If live: you demo, not describe

Beat 5: Reveal the Vision (The Close)

Goal: Expand from product to platform. Show this is bigger than it looks.

Technique: Take the core capability and show how it unlocks 3 adjacent markets.

Good Example:

"Today, we're the compliance layer for cross-border trade. But compliance data is also credit data. Once we know a company's trade history, compliance record, and settlement behavior, we can offer trade credit at 1/10th the cost of traditional letters of credit. Then trade insurance. Then supply chain finance. The compliance network becomes the trade network."

The Formula:

Today: [what you do now]
Next: [adjacent market 1, unlocked by your data/capability]
Then: [adjacent market 2]
Eventually: [the platform vision]

Check:

• The vision is a logical extension, not a pivot
• Each adjacent market builds on the same core capability
• The final vision is a platform, not a product

The Ask (Separate from the Narrative)

Raskin's framework doesn't include the ask in the narrative. The ask comes after the story, when the investor is already emotional.

Good Example:

"We're raising $1.1M to build the compliance layer for global trade. The walls are coming down. We have the team, the traction, and the timing. The only question is whether you're in."

Check:

• The ask feels like an invitation, not a request
• The investor has already decided "yes" before you ask

Delivery Tips (Critical)

This framework fails if read silently. It's designed for live presentation.

Pacing

• Beat 1 (Problem): Slow. Let the pain sink in.
• Beat 2 (Promise): Building. Create anticipation.
• Beat 3 (Reveal): Pause. Let the product land.
• Beat 4 (Evidence): Confident. Show the proof.
• Beat 5 (Vision): Expansive. Paint the future.

Body Language

• Beat 1: Still. Let the statistic/anecdote do the work.
• Beat 2: Moving. Walk to show inevitability.
• Beat 3: Center stage. This is the moment.
• Beat 4: Open. Show the evidence with open palms.
• Beat 5: Expansive. Arms wide for the vision.

Voice

• Beat 1: Lower, slower. Create gravity.
• Beat 2: Rising. Build tension.
• Beat 3: Clear, strong. The reveal.
• Beat 4: Conversational. "Let me show you..."
• Beat 5: Dreamy, then sharp. Vision, then ask.

Adapting to a Deck (If Not Presenting Live)

If you must send a deck (not present live), adapt each beat to 1 slide with minimal text:

Rule: If the investor can understand the deck without you, you've written too much. The deck is a prop, not the pitch.

Self-Review Checklist

• Does the first 30 seconds contain zero mention of my company?
• Does the problem create an emotional reaction (shock, fear, urgency)?
• Have I named a comparable success to prove the pattern?
• Do I describe capabilities, not features?
• Is the traction metric about transformation, not growth?
• Does the vision show 3 logical adjacent markets?
• Does the ask feel like an invitation?
• If presenting live: do I have a 60-second demo ready?

Anti-Patterns to Avoid

1. Starting with "Hi, I'm X and this is Y": The investor doesn't care who you are yet.
2. The Feature Dump: "We have AI, blockchain, and machine learning." Capabilities, not features.
3. The Modest Vision: "We want to be the best compliance tool." Be the platform, not the tool.
4. The Generic Traction: "We're growing fast." Transformation metrics only.
5. The Apologetic Ask: "We were wondering if maybe you might consider..." Invitation, not apology.

When to Use This Framework

Raskin's Greatest Hits — Examples to Study

1. Zuora's subscription economy pitch: Started with "The world is shifting from products to subscriptions" — not "Zuora is a billing platform."
2. Gainsight's customer success pitch: Started with "Your customers are leaving and you don't know why" — not "Gainsight is a customer success platform."
3. ChainLedger (example above): Started with "$18B lost to paperwork" — not "We automate compliance."

The pattern: always start with the shift in the world, never with the company.