Pitch Deck Content

---
description: Generate structured pitch deck content from codebase analysis
allowed-tools: Read, Glob, Grep
---

# Pitch Deck Content Generator

Analyze the codebase and documentation to generate structured content for a pitch deck, grounded in what the product actually does.

## Steps

1. **Deep product discovery**:
   - Read `README.md` for the product overview and stated value proposition.
   - Read `package.json`, `Cargo.toml`, `pyproject.toml`, or equivalent for product metadata.
   - Glob for `**/docs/**`, `**/wiki/**`, `**/about*` for additional context.
   - Grep for pricing-related patterns (`plan`, `tier`, `price`, `subscription`, `free`, `pro`, `enterprise`).
   - Grep for analytics/metrics patterns (`track`, `event`, `analytics`, `metric`, `count`).

2. **Analyze technical architecture** for talking points:
   - Glob for infrastructure files (`Dockerfile`, `docker-compose*`, `*.tf`, `serverless*`).
   - Grep for database and storage technologies.
   - Grep for third-party integrations and APIs.
   - Identify the tech stack from dependencies.

3. **Generate slide content** for each standard pitch deck section:

   **Slide 1: Title**
   - Product name and one-line description.
   - Tagline (under 8 words, benefit-driven).

   **Slide 2: Problem**
   - Define the problem in 2-3 bullet points.
   - Include a "status quo" description that the audience can relate to.
   - Quantify the problem if possible (time wasted, money lost, errors made).

   **Slide 3: Solution**
   - Describe the solution in plain language (no jargon).
   - Include a "how it works" in 3 steps.
   - Map each step to actual product functionality found in the code.

   **Slide 4: Demo Talking Points**
   - List 3-5 key workflows to demonstrate.
   - For each workflow, note: what to show, what to say, what makes it impressive.
   - Order from most impactful to least.

   **Slide 5: Market Opportunity**
   - Identify the target market based on product functionality.
   - Suggest TAM/SAM/SOM framing (note: these will need real market data).
   - List 2-3 market trends that create tailwinds for this product.

   **Slide 6: Business Model**
   - Infer the business model from code signals (pricing tiers, subscription logic, API rate limits).
   - If no pricing code exists, suggest 2-3 viable monetization strategies based on the product type.

   **Slide 7: Traction & Metrics**
   - Extract any metrics from code: number of API endpoints, supported integrations, test count, supported platforms.
   - Suggest which metrics to track and present (even if current data is not in the code).
   - Frame technical metrics as business signals (e.g., "47 API endpoints" → "comprehensive platform coverage").

   **Slide 8: Competitive Advantages**
   - Identify technical moats from the architecture (proprietary algorithms, unique data, network effects).
   - List 3-5 differentiators grounded in actual code capabilities.
   - Frame each as a defensible advantage, not just a feature.

   **Slide 9: Team Slide Suggestions**
   - Grep for contributor information (`CONTRIBUTORS`, `AUTHORS`, git config).
   - Suggest what expertise to highlight based on the tech stack complexity.
   - Recommend which technical achievements to call out.

   **Slide 10: Ask**
   - Suggest what to ask for based on the product stage.
   - Recommend how to frame next milestones.

4. **Generate speaker notes** for each slide with timing suggestions (aim for 3-4 minutes total for a 10-slide deck).

## Rules

- Ground every claim in actual codebase evidence. If something is inferred, mark it as "[Inferred]".
- Use plain, non-technical language suitable for investor audiences.
- Mark placeholders clearly where real data is needed (e.g., "[Insert monthly active users]").
- Do not fabricate metrics — use "[TBD]" for data that must come from the team.
- Keep bullet points to 3-5 per slide maximum.
- Each slide should convey one key idea.