SuperAPI AI Directory

yc-insight-driven-bp

General & other

View repository

Updated 10-16 08:44

About this skill

YC Insight-Driven BP

YC-style insight-led BP framework. Minimalist, insight-led, founder-centric. Investors don't invest in businesses, they invest in insights.

When to Use

Use this skill when:

  • The user needs a minimalist BP framework centered on a counter-consensus insight
  • The user is raising a pre-seed to seed round, facing accelerators or angel investors
  • The user is a first-time founder and needs a founder-centric pitch deck
  • The user needs a 5-8 page minimalist format or a 1-page memo
  • The user needs a direct, conversational, slightly irreverent tone

Do NOT use this skill if:

  • The user needs a rigorous data-driven framework (Series A and beyond, institutional investors) → use sequoia-structured-bp instead
  • The user needs a story-driven live presentation framework (Demo Day/roadshow competition) → use raskin-narrative-bp instead
  • The user needs an editable PPTX file → use pitch-deck-creator instead
  • The user needs a Chinese fundraising BP outline → use fundraising-bp-planner instead

Typical triggers:

  • "YC-style BP", "insight-driven business plan", "minimalist pitch deck", "accelerator application materials"
  • "Y Combinator pitch deck", "insight-first BP", "pre-seed deck", "angel investor presentation"

Workflow

This framework describes the steps of "how to use the YC insight-led BP framework":

This workflow follows a six-step progression method, with 6 steps in total:

  1. Probe: Before starting, fully read all inputs and confirm the goals and constraints.
  2. Constrain: Verify input completeness, set boundaries and non-degradable delivery standards, and switch channels when blocked.
  3. Evidence: Every number must come from inputs, specific sources, or reproducible calculations; collect supporting data.
  4. Execute: Call scripts/APIs/generate content; give impact and conclusions first, then actions and necessary evidence.
  5. Verify: Verify with actions that "could fail"—read back the output in a way different from the generation path.
  6. Deliver: Return results, clean up temporary files.

Step 1: Probe

Fully read the user's project information, confirm the fundraising stage (pre-seed to seed is preferable), industry, founding team background, and core insight. Understand the project's unique worldview.

Step 2: Constrain

Set framework usage boundaries:

  • Output length of 5-8 slides, or a 1-page memo (maximum 500 words)
  • Tone: direct, conversational, slightly irreverent
  • All content serves the core insight
  • The insight must be counter-consensus (smart people would disagree)
  • Do not use vague statements like "AI will change everything"
  • When blocked, switch channels; do not degrade the deliverable

Step 3: Evidence

Collect evidence supporting the insight:

  • The insight must be specific (not "AI is big")
  • The problem must be a direct consequence of the insight
  • Traction metrics must directly validate the insight (not just growth)
  • Customer quotes must confirm the insight (not just "the product is good")
  • Market size must be redefined through the insight (not a generic TAM)
  • The team story must explain "why you can see this insight"

Step 4: Execute

Following the page-by-page guide in the "Framework Content" below, first determine the core insight through the "one-sentence test," then write the BP content page by page. Give the impact and conclusion first, then the actions and necessary evidence. Each page follows the structure: Goal → Structure → Good/Bad Example → Check.

Step 5: Verify

Use the Self-Review Checklist to verify item by item—read back the output in a way different from the generation path:

  • Can the insight be stated in one sentence?
  • Is the insight counter-consensus (would smart people disagree)?
  • Does every page serve the insight?
  • Is the deck fewer than 8 pages?
  • Does it explain "why now"?
  • Does traction validate the insight (not just growth)?
  • Is the team story about "why we can see this," rather than "what we have done"?
  • Is the ask direct and specific?

Step 6: Deliver

Return the complete 5-8 page BP content (Markdown format, page-by-page guide), or a 1-page memo format. Include the core insight, each page's goal, structure, examples, and checklist. Clean up temporary files. If an editable PPTX needs to be generated, use pitch-deck-creator。

Output

Output as a complete BP page-by-page guide in Markdown format or a 1-page memo, including:

  • Core insight (determined through the one-sentence test)
  • 5-8 slides, each including: Goal, Structure, Good/Bad Example, Check checklist
  • Or 1-page memo format (maximum 500 words)
  • Self-Review Checklist
  • Anti-Patterns to Avoid (5 common anti-patterns)
  • YC-Specific Tips (5 YC-specific tips)
  • All examples are based on ChainLedger as a unified case

Framework Content

Meta

  • Style: Minimalist, insight-first, founder-centric
  • Best For: Pre-seed to Seed; accelerators; angel investors; first-time founders
  • Source: Y Combinator Demo Day + partner office hours
  • Output Length: 5–8 slides, or 1-page memo
  • Tone: Direct, conversational, slightly irreverent

Core Philosophy

Investors don't invest in businesses. They invest in insights — a truth about the world that you see and others don't.

"The best founders have a secret. They know something the rest of the world doesn't." — Paul Graham

YC decks are short because the insight should be so compelling that everything else is obvious.


The One-Sentence Test

Before writing a single slide, answer this:

What do you believe about the world that is true, but that most smart people disagree with?

This is your insight. Everything in the deck serves this insight.

Good Examples:

  • "The best software companies will be built outside Silicon Valley."
  • "AI won't replace doctors — it will replace the medical billing industry."
  • "Cross-border B2B payments aren't a fintech problem. They're a compliance data problem."

Bad Examples:

  • "We make the best project management software." (Not contrarian)
  • "AI will change everything." (Too vague)
  • "We have a better UI than our competitors." (Not an insight)

Slide 1: The Insight (The Hook)

Goal: Make the investor lean forward.

Structure:

  1. The counterintuitive truth (1 sentence)
  2. Why most people are wrong (1 sentence)
  3. What this makes possible (1 sentence)

Good Example:

"Most people think cross-border payments are slow because of banking infrastructure. The real bottleneck is compliance data — sanction lists, KYC, trade documentation are checked manually by 3 different parties. If you automate compliance data sharing, settlement drops from 7 days to 4 hours without changing a single bank."

Bad Example:

"ChainLedger is a fintech platform for cross-border payments."

Check:

  • The insight is contrarian (smart people would disagree)
  • The insight is specific (not "AI is big")
  • The insight implies a big opportunity

Slide 2: Problem (From the Insight)

Goal: Show the insight creates a massive, painful problem.

Structure:

  1. The old world (as seen through your insight)
  2. Who suffers most (be specific)
  3. The cost (quantified)

Good Example:

"Because compliance is manual and siloed, every cross-border transaction requires 3–5 intermediaries to re-verify the same data. Mid-market manufacturers importing from Asia spend 7 days and $2,500 per transaction on compliance overhead alone. Their 2-person finance teams are drowning."

Check:

  • The problem is a direct consequence of your insight
  • The suffering party is narrowly defined
  • The cost is quantified

Slide 3: Solution (The Inevitable Answer)

Goal: Show that once you see the insight, your solution is the only logical answer.

Structure:

  1. The mechanism (how you exploit the insight)
  2. The result (what changes for the customer)
  3. Why now (why wasn't this done before?)

Good Example:

"We built a shared compliance data layer. Instead of 3 banks independently verifying the same KYC, our network verifies once and shares the attestation. Result: settlement in 4 hours, compliance cost down 90%. Why now? Open banking APIs + regulatory sandbox programs make data sharing legal for the first time."

Check:

  • The solution directly exploits the insight
  • The mechanism is simple (one sentence)
  • The "why now" answers the "why hasn't this been done" objection

Slide 4: Traction (Proof the Insight is Right)

Goal: Show early evidence that your insight is correct.

Structure:

  1. The metric that validates the insight
  2. Trend
  3. Customer quote (if available)

Good Example:

"In 6 months: 120 customers, $50k MRR, 12% MoM growth. But the key number: 94% of customers say 'we didn't know compliance was the bottleneck until we used ChainLedger.' This validates the insight."

Check:

  • The traction metric directly validates the insight
  • There's a growth trend
  • A customer quote confirms the insight (not just "great product")

Slide 5: Market (Size Through the Insight)

Goal: Show the insight opens a massive market.

Structure:

  1. Market size via the insight (not generic TAM)
  2. Expansion path (adjacent markets your insight unlocks)

Good Example:

"If compliance data is the real bottleneck, the market isn't 'cross-border payments' ($180B). It's 'compliance automation for trade finance' ($42B). And once we own compliance data, we can expand into trade credit, insurance, and supply chain finance."

Check:

  • Market size is reframed through the insight
  • Expansion path is logical, not speculative
  • Numbers are defensible

Slide 6: Business Model (Keep It Simple)

Goal: Show you can make money. One model only.

Structure:

  1. How you charge (one sentence)
  2. Unit economics (if you have them)
  3. Why customers pay (value captured)

Good Example:

"0.15% per transaction + $2k/mo platform fee. We save customers $2,500 per transaction; they pay us $200. That's an 8x ROI."

Check:

  • One primary revenue model
  • Customer ROI is clear
  • Pricing is simple enough to remember

Slide 7: Team (Why You See This)

Goal: Show why your background gives you unique access to this insight.

Structure:

  1. Founder story: How you discovered the insight
  2. Relevant experience: Not credentials, but proof you can execute
  3. Key hire: One person who validates the vision

Good Example:

"I ran payments compliance at Ant Group for 8 years. I watched $2B in settlements get delayed because 3 banks were checking the same data. My co-founder built the compliance API at Stripe. We literally built this before — now we're doing it for everyone."

Check:

  • The team story explains why you see the insight
  • Experience is relevant, not prestigious
  • There's a narrative, not a resume

Slide 8: The Ask

Goal: Be direct. YC founders ask for money like they ask for coffee.

Structure:

Raising $X.
To achieve [3 milestones].
Current runway: X months.

Good Example:

"Raising $1.1M pre-A. 3 milestones: $200k MRR, EU regulatory approval, 3 enterprise pilots. Runway: 8 months."

Check:

  • The ask is a number, not a range
  • Milestones are specific and time-bound
  • Runway is disclosed (YC investors respect honesty)

The YC One-Page Memo Format

For very early stage (pre-launch), YC sometimes prefers a memo over a deck:

[Company] — [One-line description]

Insight: [What you believe that others don't]

Problem: [What broken thing your insight reveals]

Solution: [How you fix it]

Traction: [What evidence you have]

Team: [Why you]

Ask: [How much, on what terms]

Use of funds: [3 specific allocations]

Max 500 words. If you can't explain it in 500 words, you don't understand it.


Self-Review Checklist

  • Can I state the insight in one sentence?
  • Is the insight contrarian (smart people disagree)?
  • Does every slide serve the insight?
  • Is the deck <8 slides?
  • Did I explain "why now"?
  • Is traction validating the insight (not just growth)?
  • Is the team story about why we see this, not what we've done?
  • Is the ask direct and specific?

Anti-Patterns to Avoid

  1. The "Me-Too" Insight: "AI is changing everything." Not contrarian enough.
  2. The Feature List: More than 3 features means you haven't found the core insight.
  3. The Credential Dump: YC doesn't care about your MBA. They care about what you built.
  4. The Hand-Wavy Market: "The market is huge." Reframe it through your insight.
  5. The Range Ask: "We're raising $1–2M." Pick a number.

YC-Specific Tips

  1. Demo if possible: A 60-sec screen recording beats 10 slides.
  2. Talk about users: YC partners want to hear "users love us because..."
  3. Be honest about risks: "We don't know if enterprise sales cycle is 3 or 6 months. We're testing both."
  4. Show iteration: "We started as X, but users kept asking for Y, so we pivoted."
  5. Know your numbers cold: If you say 12% MoM growth, be ready to explain the monthly breakdown.

Guardrails

Anti-patterns

  • NEVER use a "Me-Too" insight—"AI will change everything" is not counter-consensus enough
  • Do NOT list more than 3 features—it means you have not yet found the core insight
  • NEVER pile on academic credentials—YC does not care about your MBA, they care about what you have done
  • Do NOT vaguely say "the market is huge"—redefine the market through the insight
  • NEVER give a range-style ask—"we are raising 1-2 million dollars," choose one number
  • Do NOT exceed 8 slides—YC decks are short because the insight should be persuasive enough
  • NEVER fabricate data—every number must have a source or be defensible

Constraints

  • Output length: 5-8 slides, or a 1-page memo (maximum 500 words)
  • Tone: direct, conversational, slightly irreverent
  • Everything serves the core insight
  • The insight must be counter-consensus and specific
  • Traction must validate the insight (not just growth)
  • The team story must explain "why you can see this insight"
  • The ask must be a specific number rather than a range
  • Runway must be disclosed (YC investors respect honesty)

Related Skills

  • sequoia-structured-bp — Sequoia-style rigorous data-driven framework, suitable for Series A and later, institutional investors
  • raskin-narrative-bp — Andy Raskin-style story-driven narrative framework, suitable for live presentations, Demo Day, and pitch competitions
  • pitch-deck-creator — After the framework content is complete, generate an editable 10-page PPTX file from structured JSON

About UniqueClub

Part of the UniqueClub toolkit. 🌐 https://uniqueclub.ai