Fitness · Booking & Membership Case study

EducoGym

A booking and membership platform for an appointment-based gym operating across thirteen locations, where members train in short supervised sessions rather than dropping in.

Role
Full-Stack Engineering
Disclosure
Public product · Described from public sources · Implementation not disclosed

Operational outcome

Manual gym operations → member self-service booking and admin platform

EducoGym product screens: the member app showing sign-in, membership pause and booking slots, beside the staff booking portal
Approved, public-safe project imagery.

The problem

What the system had to solve.

EducoGym trains people in short supervised sessions rather than open gym access, across thirteen locations. When the service is the appointment, the booking is not a convenience feature - it is the product. Running that on manual booking and membership admin puts a person between every member and every session.

What I owned

The responsibility behind the work.

Contributed to building the platform that moved those operations into a dedicated product: member booking, workout-slot management, membership administration and the staff portal behind them.

Publicly documented as replacing manual gym operations with online booking, workout-slot management, membership management and a full admin portal. Members book a slot per day against available gym hours and can request a membership pause; staff work from a portal covering transactions, trainee plans and booking monitoring.

Engineering approach

How it was built.

The domain problem in a system like this is agreement between three views of the same slot: what the member sees as available, what the schedule actually holds, and what an administrator has changed underneath. Bookings, reschedules, membership pauses and slot changes all move that state, and each has to leave the other two correct. Implementation detail beyond the publicly documented stack is not mine to publish.

Booking path

  1. Availability
  2. Slot booking
  3. Membership action
  4. Admin review

Engineering scope

What I worked on.

  1. Member booking against available workout slots
  2. One slot per day, resolved against the gym’s open hours
  3. Membership pause requests of up to four weeks
  4. Workout-slot and booking administration
  5. Trainee plans and transaction views for staff
  6. Analytics and booking dashboard
  7. Online payments

Product surface

Who uses it, against the same model.

Member
Browsing availability, booking a daily slot and requesting a membership pause
Operations
Workout-slot management and booking administration
Administration
Trainee plans, transactions and the booking dashboard

Impact

What the product replaced.

The result was a digital operating layer for appointment-based training: members manage their own booking and membership requests, and staff run slots, bookings and plans from one portal instead of by hand.

Technology

The technical surface.

  • Next.js
  • TypeScript
  • Node.js
  • NestJS
  • AWS

Next: VanGo

Back to all work Start a conversation