Investor documents
MVP Definition
Define a shippable first version: scope, non-goals, and success signals.
Example output
Sample document
Full-depth fictional StartupDrafter example — the same section structure, narrative quality, and conservative break-even economics you get from your own plan. Industry-standard length for review before you buy. View only, no download.
mvp-definition.md
View onlyMVP Definition — StartupDrafter
MVP Goal
Outcome (12 weeks): A paying founder can complete discovery → generate a linked plan → export at least three investor documents (executive summary, lean canvas, pitch deck) with median time under 50 minutes, without human support.
Success signal: 60 paid projects and ≥85% export completion rate.
Core Features
| Priority | Feature | Acceptance signal |
|---|---|---|
| P0 | Email auth + project purchase (Paddle) | Checkout → workspace access < 2 min |
| P0 | AI discovery interview (10–15 turns) | ≥90% interviews reach readiness threshold |
| P0 | Core Business Logic dashboard | Edit pricing → financial narrative updates |
| P0 | Generate all 16 document types | Each doc passes section completeness check |
| P0 | Export MD, DOCX, PDF, PPTX, XLSX | Format-specific smoke tests pass |
| P0 | AI assistants (Ask, Discuss, Apply) | Grounded responses cite project context |
| P1 | Usage activity log | Founder sees token debits and key actions |
| P1 | Waitlist + invite flow | Email capture → launch coupon delivery |
Out of Scope (v1)
- Team workspaces and role-based permissions
- White-label or custom export branding
- Dataroom hosting or investor CRM
- Real-time collaborative editing
- Automated cap table or legal entity setup
- Paid ads–driven onboarding flows
Success Metrics
| Type | Metric | Target (90 days) |
|---|---|---|
| Leading | Interview start rate from checkout | > 95% |
| Leading | First export within 24h of purchase | > 80% |
| Lagging | Paid projects | 60 |
| Lagging | Refund rate before generation | < 3% |
| Lagging | Contribution margin / project | > €8 |
Validation Plan
- Willingness to pay: Sample gallery A/B on landing — kill if checkout start < 1.5% on qualified visits.
- Output depth: Founder blind review vs template — kill if < 60% prefer StartupDrafter draft.
- COGS: 20-project inference audit — kill if average > €12 per completed project.
- Support load: Track median support minutes — escalate if > 20 min per project without self-serve fixes.
What it is
A boundary document: what the first release must do, what explicitly waits, and how you will know it worked. It protects you from scope creep.
Why it matters
Scope creep is the default without a written MVP contract. This aligns builders, budget, and investor expectations on what “first release” really means.
Who it's for
Founders, product managers, and engineers before sprint planning; also useful when investors ask what ships first.
What you'll find inside
- Core user stories in priority order
- Out-of-scope items with rationale
- Success metrics and timeline guardrails
When to use it
Before engineering sprints, investor questions on “when is it real?”, or hiring your first builder.
After you generate it
Drop it into sprint tickets, share with contractors, and treat non-goals as guardrails when new feature requests arrive.