| Phase | Content | Indicative duration |
|---|---|---|
| 0 — Discovery and design | Sign off this documentation, UX/UI, coach identity, database design | 2–3 weeks |
| 1 — Core (web MVP) | Landing page, sign-up and sign-in, questionnaire, admin requests, plans, subscription and payment, admin dashboard, basic notifications | 6–8 weeks |
| 2 — Content and coaching | Exercise library, programs, nutrition, measurements and photos, trainee dashboard, coach notes, basic reports | 6–8 weeks |
| 3 — Communication and integration | Chat, Google Meet, full notifications and reminders, Google Sheets | 4–5 weeks |
| 4 — Intelligence and analytics | AI assistant, advanced reports, activity log, page and video tracking | 4–5 weeks |
| 5 — Mobile app | Trainee + coach apps, push, offline, store publishing | 8–10 weeks (starts alongside phase 3) |
| 6 — Launch | Testing, security, performance, client training, soft launch then public launch | 2–3 weeks |
| 7 — Later | Auto-renewal, Tamara/Tabby, challenges and points, blog, wearables, multi-coach | By priority |
Durations are estimates for a small team and are re-baselined after design sign-off and team size are confirmed.
General acceptance criteria
- Every journey in The trainee journey works end to end on web and mobile.
- Every notification in the table arrives through the specified channel at the specified time.
- No user can see another user's data (automated permission tests).
- Admin reports match the real numbers (reconciliation tests).
- A published plan edit creates a version; a refund creates a credit note; a retried webhook never duplicates a payment.
- Arabic RTL and English LTR both work on mobile and desktop sizes.
Change management
Any addition after sign-off is logged as a change request with: the requirement, the reason, affected screens, database and API impact, security impact, time and cost estimate, and an acceptance criterion. Items marked “later” are not included in the baseline price or timeline.