Protocol: building a fitness OS for coaches who've outgrown their tools
-
Moe Hachem - March 31, 2026
Protocol launched March 1, 2026. In its current form, it’s free to use for personal training — any athlete can sign up and use it to manage their own programming. The longer-term direction is B2B2C: independent coaches and boutique studios as the paying tier, with their athletes as downstream users.
That sequencing is deliberate, and it reflects something about how the product was designed.
What Protocol is built around
The product starts with the athlete because that’s where the core utility lives — structured training management, program design, progression tracking. The interface is built for someone who takes their training seriously and has outgrown what generic fitness apps offer. Free personal use is the entry point.
The coach tier is the business model. A coach managing 10 or 20 athletes has a fundamentally different problem than an athlete managing their own training — and the tools available to most coaches don’t reflect that. Most end up running their practice across spreadsheets, WhatsApp threads, and whatever their clients happen to be tracking on their own side. It works until the client count makes the overhead unmanageable.
The B2B2C architecture means the same product serves both. Athletes use it directly. Coaches get the coordination layer on top — program assignment, client oversight, progression tracking across a roster. The coach pays for the layer that solves their specific problem. The athletes benefit from a more structured experience as a byproduct.
The design decision that shapes the product
The athlete-first entry point isn’t just a growth strategy — it’s a validation mechanism. If the product doesn’t work well for an individual athlete managing their own training, it won’t work well as the foundation for a coach managing twenty of them. The free tier forces the core to be genuinely good before the B2B layer gets built on top of it.
What two weeks of build time actually required
Protocol went from concept to live product in approximately two weeks. That’s not a flex — it’s a data point about what the methodology makes possible.
The build started with an SR-SI context index, not with code. Architecture was documented before it was built. Every significant decision had a home in the index. The AI agents building the product could orient themselves to the existing codebase at the start of each session without re-explanation.
What that compresses is not the hard thinking. The hard thinking — what does a coach actually need, how does the data model work, where does the B2B2C logic live — takes the time it takes. What the methodology compresses is the re-orientation overhead between sessions. Every session started with the AI knowing what existed. None of them started from scratch.
Protocol is currently live and in active polish. The UX is being refined. The core infrastructure is production-grade.
If you’re a coach or a serious athlete, or just need an app to help you plan and track your workouts with minimal effort then:
