Coaching
BuiltClaude drafts multi-week programmes from each member's goals, level and equipment, and revises them on a coach's feedback.
A coach approves every programme.
AI-native gym software · Built in Kampala
Fitness Arena runs a gym end to end — members, assessments, coaching, classes, staff pay and the cash desk — with Claude built into the core. Today it drafts training programmes; next it explains the finances and helps keep members coming back.
The problem
Most gyms we know track members in notebooks, take payment in cash and mobile money, and coordinate staff over WhatsApp. The result is the same everywhere:
Members can't see whether they're improving, so they drift away. Coaches write plans from memory, not data.
Cash at the desk, informal advances and per-class coach pay settled by hand — with no record when amounts disagree.
A good coach can write a few personal programmes a week. Every member deserves one.
AI-native
We're designing the platform with Claude in the loop — not a chatbot bolted on, but a layer that drafts, explains and recommends inside the workflows staff already use, with a person making every decision that matters.
Claude drafts multi-week programmes from each member's goals, level and equipment, and revises them on a coach's feedback.
A coach approves every programme.
One layer every Claude feature runs through: model settings, spend limits, usage tracking, approved-model rules for health data and an audit log.
New AI features inherit the guardrails.
Claude explains the month to an owner — revenue, what's outstanding, what needs chasing — and ranks anomalies into a worklist.
The model never produces a number. Every figure is computed in SQL and cited.
Claude drafts win-back and renewal messages, proposes rewards for milestones, and answers members' questions on WhatsApp from the gym's own knowledge base.
The model drafts; a person sends. Rewards come from an approved list, and anything account-specific goes to staff.
No programme, message, reward or post reaches a member without a person approving it.
Numbers, segments and eligibility are computed; Claude explains and writes, it doesn't invent.
Each call gets only what it needs, with consent where health data is involved.
Built with Claude, too
We build the platform with Claude Code. Since July 2026 it has co-authored most of our changes — 277 of the 391 commits in the codebase — with every change tested in CI before it ships.
The platform
A staff dashboard and a member app on one platform. Everything below is built; we're hardening it with Fitness Arena's coaches and front desk ahead of launch.
Fitness tests with defined protocols, and the analytics on top of them.
A programme builder for coaches and a training log for members.
Claude drafts a programme from the gym's own exercise catalogue. A coach reviews, refines and approves it.
Members ask for a programme around their goals; it lands in a coach's queue.
Timetables, per-session enrolment and attendance that feeds coach pay.
Salaries, class payouts and advances, with the owner as the approver.
The front-desk till, spending and money in — where cash gyms lose track.
Inventory, service records and schedules for every unit on the floor.
Members, plans, subscriptions and payments, behind role-based access.
Claude in coaching · Built
Claude, through the Anthropic API, turns a member's goals, level and available equipment into a structured multi-week programme. It drafts; a coach decides. Here is the path every programme takes.
A coach starts a draft, or a member asks for a programme and gives consent.
Only what the draft needs is sent — goals, level, equipment. No names, no emails.
Claude builds the week, choosing exercises only from the gym's catalogue.
Every exercise is checked against the real catalogue; incomplete output is rejected.
A coach edits, asks for a revision, or approves. Only then does a member see it.
A monthly USD cap, a per-person daily limit and a concurrency cap. Owners are emailed as the cap nears.
Member health inputs only go to models an admin has approved with zero or short data retention.
Generations, refusals and model-setting changes are recorded in an append-only log.
The content of drafts nobody accepted is wiped after a retention window.
Drafts use the gym's in-service equipment — or a member's home kit — so plans are doable.
When coaches edit an accepted draft, we record how much changed to measure draft quality.
Illustration of the request flow — not live member data.
Built for how gyms here pay
Payments in Uganda move through cash and mobile money, in UGX. The platform is designed around that, with integrations with Eversend for mobile-money payouts and collections — and a rule that the person who records money is never the person who approves it.
Engineering
A Go API on PostgreSQL with a React front end. Every change runs the Go test suite against a real, fully migrated database in CI before it can ship, and new capabilities go live behind feature flags.
Figures from our code repository, October 2026.
Also next
Designed and specified, not yet built.
Bringing heart rate and activity from members' devices into their progress.
Live plans, the class timetable, enquiries and click-and-collect merchandise.
Built with a real gym
We're building the platform alongside Fitness Arena, a gym in Kampala, where it will launch first. Its coaches and front desk shape every workflow — from how a till is closed to how a programme is approved — so the software fits how a gym actually runs.
Test.Train.Retest.
Contact
Gym owners, coaches and partners — we'd like to hear from you.