This document describes a single-brand platform for one head coach in the first release, with room to add assistant coaches and nutritionists. It is not assumed to be a multi-tenant SaaS product unless the client explicitly approves that direction.
- Web: the public website, registration, and the admin, coach and trainee portals.
- Mobile: native iOS and Android apps consuming the Laravel REST API; no separate databases are created for the apps.
- Source of truth: the platform database is authoritative. Google Sheets is a presentation, export and sync channel, never an independent operating database.
- Business decisions: pricing, plan contents, refund policy, session counts and renewal eligibility must be approved in writing by the client.
- Legal decisions: privacy policy, tax, e-invoicing and app-store terms need review by a qualified specialist before launch. This documentation is not legal advice.
- Health data: treated as sensitive data. Least privilege and data minimisation apply everywhere.
In scope vs. requiring separate approval#
Item Status Marketing site, landing page and CMS In scope Trainee registration, questionnaire and admin review In scope Plans, subscriptions and payments In scope once a payment provider is selected Training programs, nutrition plans and coaching In scope Chat, notifications, Google Meet and Google Sheets In scope, subject to account and permission approval iOS and Android apps Separate phase after the API and web experience are stable Supplement store or product sales Out of current scope InBody devices, wearables and health integrations Later phase, subject to API availability and client approval Multi-coach SaaS Separate architecture and commercial decision Delivery reality
The phases in Roadmap & phases are estimates for a small team. They are re-baselined after design sign-off, provider selection and confirmation of the open questions.