Helix writes the training on the Helix Method. It also runs the desk that gets an athlete through the door — intake, billing, scheduling, waivers, attendance — against one record, in one system.
A gym is three jobs happening at the same time. Each gets its own surface. All three write to the same record, so nothing is typed twice into two systems.
The coach
Drafts in minutes, approved by a human.
An assessment goes in; a four-week block comes out, written to the Helix Method. Every exercise Helix chooses carries its reason, so an edit is a decision a coach can defend rather than an override of a black box.
The athlete
Logged on the floor, not after it.
The week, the session, the set — on a phone, as it happens. What gets logged is what the next block is built from.
The front desk
The half that decides whether a gym runs.
Leads, memberships, bookings, waivers, attendance, payments. Nothing to do with programming, and everything to do with whether the programming ever reaches anyone.
The desk is where a gym is won or lost.
A missed renewal, an unsigned waiver, a class nobody was billed for. None of it is training, and all of it decides whether the training happens.
Front of house
The half nobody demos
Most training software stops at the program. A gym doesn't — and the gap is where the spreadsheets breed.
Leads and intake
Enquiries land, get tracked, and become an athlete record without anyone re-typing a name. Email capture runs on its own.
Bookings, classes and coach availability on one calendar, with a coach's own Google Calendar read in beside them — so the desk sees the hours already spoken for.
Waivers
Sent, signed and stored against the athlete. Not a PDF in somebody's inbox.
Attendance
Reconciled against what was booked and what was billed. The three agree, or the desk gets told which one doesn't.
Reporting
Engagement and lifecycle — who is drifting, while there is still time to pick up the phone.
Underneath
Everything above has to survive the second gym
One gym is a product. Two is an architecture — separate records, separate policy, separate billing, one codebase. That is a different page, and it is the one to read if you are asking whether this holds up past the first floor.