investor-pitch-deck

$npx mdskill add mohitagw15856/pm-claude-skills/investor-pitch-deck

Builds investor pitch decks with slide-by-slide structure and key messages

  • Solves the problem of creating compelling investor presentations from scratch
  • Uses no external APIs, relies on internal knowledge of startup fundraising
  • Analyzes company stage, metrics, and audience to shape narrative flow
  • Delivers structured output with proof points and content guidance per slide

SKILL.md

.github/skills/investor-pitch-deckView on GitHub ↗
---
name: investor-pitch-deck
description: "Build the narrative and slide structure for an investor pitch deck. Use when asked to create a pitch deck, investor presentation, fundraising deck, or startup pitch. Produces a slide-by-slide structure with narrative beats, key messages, and what each slide must prove to an investor."
---

# Investor Pitch Deck Skill

Builds the complete narrative and slide structure for an investor pitch deck — focused on what investors need to see, not what founders want to show.

## Required Inputs
- **Company name and one-line description**
- **Stage** (Pre-seed / Seed / Series A / Series B)
- **Ask** (how much raising and what for)
- **Key metrics** (revenue, growth, users, retention)
- **Target investors** (generalist / sector-specific / angels)
- **Deck length** (10 / 12 / 15 slides)

## Output Structure

For each slide:
- **What this slide must prove** (the investor question it answers)
- **Content guidance** (specific, not generic)
- **Common mistake to avoid**

---

**Slide 1: Cover** — Proves you can say what you do in one sentence.
**Slide 2: Problem** — Proves the problem is real, painful, and large. Lead with the human problem, not market size.
**Slide 3: Solution** — Proves your solution is meaningfully better. Focus on outcome, not features.
**Slide 4: Product** — Proves this is real and works. Show the actual product.
**Slide 5: Traction** — Proves people want this. Show retention and revenue, not signups.
**Slide 6: Market** — Proves the market is large enough. Use bottoms-up TAM where possible.
**Slide 7: Business Model** — Proves you understand unit economics. Include CAC and LTV.
**Slide 8: Go-To-Market** — Proves you can acquire customers efficiently. Focus on what is actually working.
**Slide 9: Competition** — Proves you understand the landscape. Never say "no competitors."
**Slide 10: Team** — Proves this team can execute this opportunity. One sentence per person, specific.
**Slide 11: Financials** — Proves you understand your business. Show assumptions, not just projections.
**Slide 12: The Ask** — Proves you know exactly what you need. Specific use of funds and 18-month milestones.

## Narrative Principles
- Every slide answers one investor question
- Investors decide go/no-go on slides 1-5 — front-load evidence
- Keep to 10-12 slides for a first meeting

## Quality Checks

- [ ] Each slide answers one specific investor question
- [ ] Slides 1-5 front-load the strongest evidence
- [ ] Traction slide shows retention and revenue, not just signups
- [ ] Competition slide does not say "no competitors"
- [ ] Ask slide specifies use of funds and 18-month milestones
- [ ] TAM is bottoms-up where possible

## Example Trigger Phrases
- "Build a pitch deck structure for [company]"
- "Help me structure my Series A deck"
- "What slides should my investor pitch have?"

More from mohitagw15856/pm-claude-skills

SkillDescription
360-feedback-templateDesign a 360-degree feedback survey or write a structured 360 feedback report. Use when asked to build a 360 feedback process, write 360 feedback for a colleague, design a feedback survey, or produce a feedback report. Produces either a complete survey instrument with rating scales and open-ended questions, or a structured narrative feedback report with themes, strengths, and development areas.
ab-test-plannerDesign statistically rigorous A/B tests for product features, UI changes, onboarding flows, and pricing experiments. Use when asked to set up an experiment, design an A/B test, calculate sample size, or interpret test results. Produces a complete test plan with hypothesis, variant definitions, sample size, duration estimate, guardrail metrics, and a results interpretation guide.
accessibility-auditGenerate a WCAG 2.2 accessibility audit checklist and remediation suggestions for any UI or design. Use when asked to audit for accessibility, check WCAG compliance, review a design for a11y issues, or create an accessibility remediation plan. Produces a prioritised checklist with pass/fail assessments and specific fixes.
account-planBuild a structured account plan for any key customer or target account. Use when asked to create an account plan, key account strategy, strategic account review, or territory plan. Produces a complete account plan with relationship map, growth opportunities, risks, and 90-day action plan.
aeo-optimizerOptimize an article for Answer Engine Optimization (AEO) — restructuring content so AI engines like ChatGPT, Perplexity, and Claude can extract, quote, and cite it. Rewrites headings as questions, drops 50-80 word answer capsules, audits paragraph length, and flags trust signals. Use when asked to AEO-optimize, make content AI-readable, improve AI citation chances, or adapt an article for answer engines.
ai-ethics-reviewConduct an ethical review of an AI or ML feature, model, or product. Use when asked to run an AI ethics review, assess AI risks, audit a model for bias, or produce an AI impact assessment. Produces a structured ethics review covering fairness, transparency, privacy, safety, accountability, and societal impact with prioritised mitigations.
ai-product-canvasStructure AI and ML product decisions with the rigour of any product decision. Use when building AI-powered features, evaluating LLM integrations, designing AI products, or assessing AI readiness. Produces a complete AI product canvas covering problem definition, model approach, data requirements, evaluation framework, UX design, responsible AI checklist, and launch monitoring plan.
ambiguity-resolverStructure vague opportunities and unclear briefs into actionable one-page problem statements. Use when asked to clarify a vague brief, frame an undefined problem, make sense of an unclear opportunity, or when the user says 'we need to figure out what to do about X' or 'I've been asked to look into Y'. Produces a structured problem brief with reframed questions, scoped boundaries, and a minimum viable research plan.
api-docs-writerWrite clear, developer-facing API documentation. Use when asked to document an API endpoint, write API reference docs, create a developer guide, or turn a raw spec/Postman collection into documentation. Produces endpoint documentation with descriptions, parameters, request/response examples, and error codes.
api-versioning-strategyWrite an API versioning strategy document for a service or API platform. Use when asked to define versioning policy, plan API deprecation, classify breaking changes, or document version lifecycle. Produces a complete versioning strategy with breaking-change classification table, deprecation timeline, migration guide template, and client communication template.