At SEED, your MVP must move beyond the whiteboard. This is where you prove your idea is not just possible in theory, but buildable in practice.
It’s not about raising money to try — it’s about showing visible traction in the build itself.
If CONCEPT was a sketch, SEED is a hand-built working prototype.
The shape may not be final, but it’s real, touchable, and testable.
Purpose
- Demonstrate that the MVP is live, functioning, and advancing.
- Show architecture choices that balance today’s build with tomorrow’s scale.
- Provide proof through demos, tests, and real usage.
When to Complete
- Once core features of the MVP are coded, built, or running live.
- After early test runs or sandbox demos with actual users.
- Before seeking larger checks — investors at this stage want proof in hand.
Proof Sections
MVP Status & Milestones
- What’s already built and tested?
- What’s staged for the next sprint or milestone?
- Is the core loop or value path functional?
- B2B SaaS – “Login, dashboard, and workflow live in staging. Stripe integration scheduled for next sprint.”
- B2C CPG – “3 SKUs shelf-stable at 8 weeks, dry-run production run completed.”
- Services – “New client onboarding workflow tested with 4 pilot customers.”
Architecture or System Design
- What stack, process, or system are you building on?
- Is it stable today, and upgradeable for tomorrow?
- Can you show architecture diagrams or process flows?
- B2B SaaS – “React + Firebase. Migration path to PostgreSQL + AWS at 10K MAU.”
- B2C CPG – “Cold-chain validated through local co-packer; expansion path mapped to national distributor.”
- Services – “Workflow software built in Airtable + Zapier prototype; migrating to custom platform in 6 months.”
Test Results or Tech Demos
- Who has touched this?
- Any performance benchmarks, sandbox runs, or demo data?
- Do you have recorded or live demos to show?
- B2B SaaS – “20 users ran onboarding through demo; 80% completed successfully.”
- B2C CPG – “Prototype produced at 200-unit batch; <2% defect rate.”
- Services –“Pilot client cycle ran 4 weeks; delivered 97% SLA compliance.”
Team Execution & Coverage
- Who owns build vs. test vs. design?
- Which work is in-house vs. outsourced?
- Do you have coverage for core risks?
- B2B SaaS – “CTO owns backend dev; front-end handled by contractor; QA offshore resource tests weekly.”
- B2C CPG – “Head of Ops runs pilot logistics; co-packer covers production; fractional QA consultant validates process.”
- Services – “Lead consultant designs delivery workflow; junior staff execute client engagements; external QA advisor reviews process.”
Execution Requirements
- Clear MVP build summary.
- Visual: screenshot, demo link, or diagram.
- Evidence: test results, early benchmarks, or usage metrics.
Domain Adaptability: Specialized
Every MVP looks different, but the goal is the same: prove it works.
- B2B SaaS – Core workflow + early integrations.
- B2C CPG – Prototype runs + shelf-life validation.
- Services – Repeatable, tested delivery workflows.
Expected Output
- 1–2 paragraph MVP build status.
- Optional bullets: stack, sprint progress, or component list.
- Supporting visuals (screenshots, diagrams, demo links).
Linked Asset
View
Edit
Optional Enhancements (Pro-Level Execution)
- Architecture Evolution Map – Current stack + migration path.
- Live Demo Video – Short recording walking through the MVP.
- Stress Test Results – Early failure tests under simulated load.