Template 07 — PRD / MVP Spec

Copy and fill to scope a product/feature. Full method: Phase 15.04.


MVP Spec: <product/feature>

Author: <name> · Date: <date>

1. ICP (who it's for) (Phase 15.02)

  • Industry / size: <...> · Buyer: <role> · User: <role> · Acute pain: <...> · Willingness to pay: <$>

2. User stories (JTBD)

  • As a <role>, I want to <job>, so that <outcome>. (×3–5 for the core workflow)

3. Critical workflow (the ONE thing — own it end-to-end) (Phase 15.03)

  • <ingest → AI step → validate → human touchpoint → output → integration>
  • System of record / action layer owned: <...>
  • Explicitly OUT of scope (MVP): <auth/settings/dashboards/extra workflows>

4. Technical design (minimal)

PieceChoice
Model<capable API model now; route later> (Phase 5)
RAG<minimal pipeline if needed> (Phase 9)
Agent/tools<least-agentic that works> (Phase 10)
Eval plan<golden set + metric> (template 02)
Cost model<cost/resolved task + margin> (template 05)
Security posture<no secrets in prompts, PII, isolation, trust boundary> (template 06)

5. Demo script (before → after → trust → outcome) (Phase 15.07)

  1. Painful before (their words): <...>
  2. After on real data: <...>
  3. Trust shown: <citations / approval / accuracy>
  4. Outcome + CTA: <time/$ saved><pilot/payment>

6. Plans

  • 30-day: ship embarrassingly-simple core workflow to <N> design partners; collect first eval examples.
  • 90-day: first paying users/pilots; eval harness + cost instrumentation; first moat investment (Phase 15.06).

7. Success metrics

  • Activation / D7 retention / willingness-to-pay / cost per resolved task / eval score.

Smallest complete slice of one workflow. Ship in weeks, not months. Don't build infra before users.