Bookings, plans, meals and members on one platform.

Barn Gym runs personal training and group fitness in Burwash, East Sussex. Before, it ran on several paid tools that did not talk to each other: a community platform in one place, booking in another. Consultations, coach diaries and time off were tracked outside any system. Every workout and meal plan was written by hand, for every client. Members had nowhere to log training, food, photos and measurements together, and there was no admin view of bookings, credits or how each coach was doing. Every one of those gaps was a job somebody did by hand.

Coaches get their own portal. Their schedules and time off now live inside the system, where the owner can see them, and coach analytics finally show how each coach is doing. Plans are built from a library of 205 exercises and a database of 120 meals, so a coach assembles a plan from parts that already exist instead of writing it from scratch for every client. The hand-written plan, the line at the top of this page, is the job this part was built to retire.

The platform replaces the paid community tool and the separate booking. The community now lives inside it: spaces, channels, challenges, polls, events and coach-to-member messaging, with 37 of 37 community API tests passing - automated checks that each part does what it should. The admin side has dashboards, bulk actions, audit logs and CSV export, so the data can leave with its owner. Members, coaches and the owner now work from the same system, and the same numbers. It runs to about 50,000 lines of code across roughly 85 database tables, and each gym’s branding is set separately. That last part matters, because the system is now becoming a product for other gyms. The foundations for running more than one gym are in place, and the work to keep each gym’s data fully separate is under way.