What this prompt does
This prompt scaffolds a full 14-slide pitch deck script with hard constraints baked in: a timed demo flow, explicit market sizing methodology, a technical architecture slide built for credibility (not vanity), and an honest competitive moat analysis. The template forces you to provide real variables — your actual metrics, funding stage, and team composition — so the output stays grounded in your specific situation rather than producing generic startup language.
What makes it work structurally is the sequencing. It mirrors how experienced investors actually read decks: story first (problem, solution, demo), proof second (traction, architecture, competition), then ask. The separate investor Q&A section is generated from the same inputs, so the 10 prepared answers are calibrated to your stage and numbers — not a generic list of "hard questions."
The explicit instruction "make it a story, not a feature list" acts as a guardrail. It keeps the AI from defaulting to bullet-point product descriptions, which is the most common failure mode in AI-generated pitch content.
When to use it
- You are preparing a seed or Series A deck and need a full narrative draft before engaging a designer.
- Your technical co-founder needs a credibility slide that explains the architecture without dumbing it down or going too deep.
- You are rehearsing a live pitch and need a timestamped demo script so you do not blow your time allocation.
- You received investor feedback that your competitive positioning is weak and you need a structured 2x2 reframe.
- You are iterating across multiple funding stages and want to quickly reframe the same core story for a different audience.
Example output
[Slide 8 — Technical Architecture]
Headline: "Hard to build. Harder to replicate."
What to say: "We process real-time inventory signals from 40+ ERP connectors
using an event-driven pipeline — Kafka ingestion, custom conflict-resolution
layer, PostgreSQL materialized views updated sub-200ms. The non-obvious
part is the conflict-resolution logic: 18 months of edge-case data from
our first three enterprise customers is baked into those rules. A new
entrant starts from zero there."
Visual suggestion: Three-column diagram — data sources → processing layer
→ customer-facing API. Highlight the middle column in brand color.
[Investor Q&A — Q3]
Q: "What stops a large ERP vendor from adding this natively?"
A: "SAP and Oracle move on 3-5 year product cycles. We already have two
customers who evaluated Oracle's roadmap and chose us because they needed
this in Q1, not 2028. Speed is the moat right now."
Pro tips
- Fill
[metrics]with specifics, not categories. "ARR $240K, MoM growth 18%, NRR 112%, 14 enterprise logos" produces a calibrated traction slide. "Good growth and retention" produces filler. - Set
[demo_duration]shorter than you think. Investors routinely interrupt. A 4-minute demo script is safer than 8 — you can always extend, never compress gracefully. - The architecture slide is for a non-technical partner. If you have deeply technical moats, run this prompt once for investors and again with a more technical framing for due diligence calls.
- Run the Q&A section separately after your first draft. Paste your generated slides back in and ask the AI to identify which answers contradict or weaken the narrative — that gap analysis is where the real prep happens.
- Match
[funding_stage]precisely to traction expectations. A pre-seed ask with Series A metrics framing creates cognitive dissonance. The prompt calibrates language per stage, but only if you are honest about where you actually are.
