Startup MVP Spec Example — Notewise (AI meeting notes)
Example document for Startup MVP Specs. Use this as a reference when creating your own.
For Informational Purposes
This document template is provided for informational purposes. Customize it for your specific needs.
Document: Startup MVP Specs
Example Document
Last updated 6/4/2026
Startup MVP Spec — Notewise (AI meeting notes)
Product / working name: Notewise Author: Priya Nandakumar Date: 4 June 2026 Target launch: 30 June 2026
1. Problem and hypothesis
Busy team leads sit through back-to-back video calls and rarely have clean notes or clear action items afterwards, so decisions and follow-ups get lost. We believe that team leads who run five or more video meetings a week have this pain badly enough that they will connect their calendar and let an AI join their calls when offered automatic summaries and action items delivered within five minutes of a call ending.
2. Target user
- Who: Team leads and managers running 5+ recurring video meetings per week.
- Context: They take calls all day, never get time to write notes, and feel follow-ups slipping.
- Where to reach them: A 40-person waitlist from a "remote managers" community plus two friendly teams.
3. Core user flow
- User signs up and connects their work calendar.
- For one selected recurring meeting, the Notewise bot joins the call and records the audio.
- After the call ends, an AI summary plus a list of action items is generated.
- The user opens an email with the summary and rates it useful or not — the action we measure.
4. Scope
| In scope (must-have to test the hypothesis) | Out of scope (explicitly deferred) |
|---|---|
| Calendar connect for a single recurring meeting | Support for every calendar and conferencing tool |
| Bot that joins one call and captures audio | A polished web dashboard with search and history |
| AI summary plus action-item extraction | Team workspaces, sharing, and permissions |
| Summary email with a one-click useful / not-useful rating | Billing, plans, and payment |
| Mobile app and integrations (Slack, CRM, task tools) |
5. Success metrics and kill criteria
- Primary metric: Percentage of delivered summaries rated "useful" by the user.
- Success threshold: 60 percent or more of summaries rated useful across at least 30 meetings.
- Kill criteria: Below 35 percent useful, or fewer than 10 of 40 waitlist users connect a calendar.
- Measurement window: Three weeks from first user onboarded.
6. Non-functional notes
- Platform: Web sign-up and email delivery only; no dashboard for this version.
- Scale to support: Roughly 40 users and a few hundred meetings — small by design.
- Manual vs automated: A human reviews and lightly edits each summary before it sends, so we can test demand for the value before investing in a fully automated pipeline.
- Privacy / data: Explicit consent to record; recordings deleted after the summary is rated.
7. Timeline
| Milestone | Work | When |
|---|---|---|
| 1 | Calendar connect, recording bot, summary email | Week 1 |
| 2 | Onboard the first 15 waitlist users | Week 2 |
| 3 | Collect ratings across 30+ meetings | Weeks 2–3 |
| 4 | Decision: continue, pivot, or stop | End of week 3 |
Notes
- Summaries are human-edited behind the scenes this version; full automation is the first build after a successful test, not now.
Notes
A worked example showing a tight, single-flow MVP with explicit out-of-scope items and pre-set kill criteria. The numbers and thresholds are illustrative.
About this Example
Part of the Startup MVP Specs document collection
Document Type
Startup MVP Specs
A focused specification for a minimum viable product — the smallest build that tests the core hypothesis.