The organisation needed one fitness membership platform for members, coaches, and studio managers. The existing journey divided memberships, class schedules, bookings, waitlists, coaching plans, attendance, payments, progress notes, and studio reporting between separate tools and informal follow-up, so the project had to solve the operating model as well as the interface.
A complete fitness membership platform shaped around members, coaches, and studio managers
The organisation needed one fitness membership platform for members, coaches, and studio managers. The existing journey divided memberships, class schedules, bookings, waitlists, coaching plans, attendance, payments, progress notes, and studio reporting between separate tools and informal follow-up, so the project had to solve the operating model as well as the interface.
Discovery followed the full journey from the first customer or staff action to its operational and commercial close. That exposed the handoffs between memberships, class booking, and coaching progress, including the exceptions that a feature list would have missed.
- Map the people, decisions, and records across the whole fitness membership platform.
- Separate firm fitness and wellness rules from habits created by the old tools.
- Agree what the first release must complete from end to end.
The product joined memberships, class booking, and coaching progress without blurring roles
Keep membership entitlement, class capacity, and coaching records connected while giving each role a simple daily view.
In the fitness membership platform, each audience receives a focused home while the underlying state remains shared. The interface shows what needs attention, who owns the next action, and why work is blocked, while secondary detail stays available for review without crowding everyday tasks.
- Design the primary journey for every audience named in the brief.
- Give exceptions, corrections, and cancellations an explicit route.
- Use realistic records to test the complete flow before widening the surface area.
Flutter, Angular, .NET APIs formed one supportable fitness membership platform
The architecture follows business ownership rather than the navigation menu. Flutter, Angular, .NET APIs share versioned contracts, server-side permissions, observable integrations, and one authoritative record for the decisions behind class booking.
In the fitness membership platform, slower or external work runs through durable jobs with idempotent handling and visible failure states. Logs retain the organisation, actor, and product record needed to investigate a problem without guessing from a generic error message.
- Flutter supports the primary product surface.
- Angular owns a bounded part of the product journey.
- .NET APIs keeps operational data and handoffs reviewable.
The release had to prove the whole fitness membership platform, not one polished screen
Members can plan training and studios can manage capacity, coaching, and subscriptions without separate systems. The release plan therefore followed representative work across every audience and the complete path through memberships, class booking, and coaching progress.
Acceptance for the fitness membership platform included ordinary work, missing inputs, repeated requests, failed integrations, permission boundaries, and the route back to a trustworthy state. The team checked whether staff could understand and recover from a problem without direct database help.
- Run the busiest realistic journey from start to operational close.
- Rehearse a failed integration and a repeated customer action.
- Confirm that every role sees only the work and data it owns.
- Trace a management result back to the records that produced it.
What the work established
Members can plan training and studios can manage capacity, coaching, and subscriptions without separate systems.
- 01
The fitness membership platform now gives members, coaches, and studio managers one shared operating record.
- 02
Memberships, class booking, and coaching progress follow the same product rules.
- 03
The system makes ownership and exceptions visible instead of hiding them in manual follow-up.
- 04
The product can grow from clear workflow, data, and service boundaries rather than isolated features.