MVP
MVP goals, success criteria, and explicit out-of-scope items.
MVP definition
Stakeholder overview: /mvp. Full product context: Product.
Goals
- A learner can complete intake, get matched (or admin-overridden), book/run coaching, submit evidence, and publish a public profile.
- A coach can complete setup and appear match-ready (track + availability + active coaching offering).
- An employer can register, create an org, obtain seats (manual invoice → admin mark paid), search verified talent, shortlist, request intros, and record a placement.
- Marketing and nav sell CMH — not “500+ courses / LMS.”
- Public proof pages (
/u/[slug],/credentials/[code]) are shareable and distinct from/verify.
Success criteria
| Signal | Target |
|---|---|
| Coaches live | ~5 coaches across ≥3 active tracks; setup checklist complete |
| Proof inventory | ≥20 public profiles with full three-evidence verification on target skills |
| Demand | First employer org with seats activated; ≥1 real intro |
| Funnel | Measure time-to-first-session after intake |
Ops detail: Launch checklist.
In scope
- Learner intake → coach match → evidence → public profile → employer intro
- Coach setup checklist (match ready)
- Employer talent search / pipeline / jobs / billing (manual invoice activation)
- Public proof:
/u/[slug],/credentials/[code] - Admin career tracks & skills; match override
Out of scope
- Self-serve employer payment (Stripe etc.) — invoices + admin
mark paidonly - Full ATS / LinkedIn clone
- AI tutor replacing coaches
- Seeding 20 real profiles in engineering (ops owns this)
- Course catalog growth as the growth strategy
- App-wide spacing/padding redesigns as deliverables