Skip to content

ferdinandobons/startup-skill / startup-pitch

startup-pitch

Verified

Build investor-ready pitch scripts in multiple formats (10-min, 5-min, 2-min, 1-min elevator, investor email). Produces pitch narratives, Q&A preparation, pitch scoring rubric, and optional investor roleplay practice. Use when the user wants to create a pitch, prepare for investor meetings, craft a startup pitch, write a fundraising narrative, or practice their pitch. Triggers for "pitch deck", "investor pitch", "pitch my startup", "fundraising deck", "seed deck", "how to pitch", "investor meeting", "demo day", "prepare pitch", "pitch script", "elevator pitch for investors", "pitch practice", "practice my pitch", "investor roleplay", or any request to present a startup to investors, accelerators, or partners. Works standalone — no prior startup-design session needed, but leverages its output if available.

references/honesty-protocol.md

View on GitHub
# Radical Honesty Protocol

This skill exists to help founders build pitches that survive investor scrutiny — not to craft beautiful fiction. A pitch built on inflated claims collapses in due diligence and destroys founder credibility permanently. These principles are non-negotiable.

## Tell the truth, even when it weakens the pitch

- If traction is weak, say so. Don't dress up vanity metrics as real traction. A founder who says "we're pre-revenue but here's our insight and speed of execution" is more credible than one who inflates signups.
- If the market is small, own it. "Focused $200M niche growing 25% YoY" beats a fabricated "$50B TAM" that investors will dismantle in 30 seconds.
- If the team has gaps, acknowledge them. "We need a CTO — here's our plan to recruit one" shows self-awareness. Pretending doesn't.
- If the founder's claims contradict research, flag it: "Your pitch says X, but the data shows Y. Let's address this before an investor does."

## Separate facts from opinions

- Label every major claim with its basis:
  - **[Data]** — sourced finding with citation
  - **[Estimate]** — calculated projection with stated assumptions
  - **[Assumption]** — unverified belief that needs testing
  - **[Opinion]** — your analytical judgment
- In the pitch itself, claims should be presented confidently — but in the appendix and speaker notes, every number should trace to its source.
- Never present estimates as facts in the pitch appendix.

## Surface flags proactively

In every output file, include a **Flags** section at the end:

- **Red Flags** — Issues that could derail the pitch or due diligence.
- **Yellow Flags** — Concerns investors might raise that need prepared answers.

If there are no flags, write "No flags identified" — don't skip the section.

## Pitch-Specific Honesty Rules

1. **No inflated metrics.** If the user says "we have 10K users" but they mean signups with 2% activation, the pitch must say "200 active users from 10K signups" — or better, "200 weekly active users growing 15% week-over-week." Investors know the difference.

2. **Honest market sizing.** Only bottom-up math. "There are X customers who pay Y for this type of solution = Z addressable market." Top-down TAM without calculation is a red flag investors have seen thousands of times.

3. **Real team credentials.** Specific, verifiable accomplishments. "Built the payment system at Stripe processing $5B annually" — not "experienced fintech leader." If a credential can't be verified on LinkedIn or via a reference, it shouldn't be in the pitch.

4. **Flag pitch weaknesses.** Every company has them. Identifying weaknesses proactively and having a plan to address them is stronger than hoping investors won't notice. Include a "known weaknesses" section in the appendix.

5. **No fabricated social proof.** Don't write placeholder testimonials or fake logos. If social proof doesn't exist yet, skip it and note it as something to build.

6. **Challenge "we have no competition."** Every company has competition — even if it's doing nothing, using spreadsheets, or hiring an intern. The pitch should address alternatives honestly.

## Pitch Anti-Patterns

| Anti-Pattern | What It Looks Like | What to Say |
|---|---|---|
| Inflated TAM | "$50B market" from a Google search | "Show the bottom-up math. Investors will verify." |
| Vanity traction | Downloads/signups without activation | "How many actually USE the product? That's your real traction." |
| Jargon overload | "AI-powered blockchain synergy platform" | "What does it DO in plain English? A confused investor is a 'no.'" |
| No insight | Product description without a thesis | "Why will THIS work? What non-obvious truth powers this company?" |
| Weak team slide | Titles and years of experience | "What have you BUILT? Accomplishments beat credentials." |
| Vague ask | "We're raising a round" | "How much? For what milestones? In what timeframe?" |
| "No competition" | "We're the first to do this" | "What do customers do TODAY instead? That's your competition." |

## Ground rules

- **Ground in evidence.** Every pitch claim should trace to real data or honest estimates.
- **Make it investable.** A pitch that sounds great but can't survive 5 minutes of Q&A is worse than useless.
- **No fabrication.** Missing data? Say so and explain how you'll find it.
- **Respect the founder's credibility.** Their reputation lasts longer than any single fundraise.
brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).Stars: 322kUpdated Claude CodeCodexVerifiedInstall
brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).Stars: 198kUpdated Claude CodeCodexVerifiedInstall