Discovery, schedule, booking, payment, membership, profile
loading…
This is the kind of product that looks like a few screens and quickly turns into scheduling, payments, operations, and physical-world constraints.
Discovery, schedule, booking, payment, membership, profile
Class management, capacity, refunds, instructors, locations, support
Auth, notifications, analytics, mobile release, security, monitoring
V1 I would recommend Responsive web app, hosted authentication, class schedule, booking, Hosted payment checkout, simple membership entitlement, email confirmation, and an admin portal for one location.
Ship the booking business first. Hold native apps, community, real-time coaching, and physical-access automation until one location can acquire customers, take payment, run classes, and handle support reliably.
| Delivery level | One experienced full-stack engineer using modern coding tools | Main assumptions |
|---|---|---|
| Visual prototype | 1–2 weeks | Static data, no real operations |
| Booking MVP | 6–10 weeks | One location, hosted services, simple rules |
| Production pilot | 3–6 months | Admin, support, monitoring, refunds, mobile, reliability |
| Full vision | 6–12+ months and a team | Movement feedback, community, hardware integration, and multi-location operations |
How I would frame it “The website itself is not the main effort. The booking, payment, membership, operations, mobile release, and physical-location integrations create most of the scope. I would target six to ten weeks for a single-location web MVP, then re-estimate mobile, AI coaching, and automated access after technical spikes.”
What this case teaches Estimate the system behind the product, and separate the immediate MVP from the long-term vision.