Gain speed · Increase mobility · Prevent injury
Gain speed · Increase mobility · Prevent injury
Tap a day to change what it prescribes. Edits survive into the next block.
—
A block is four weeks of training that build on each other, plus an easy fifth week. These settings decide when it starts, which session lands on which day, and how it ends. Change one and save — nothing you've already logged moves.
Which day the training week turns over on. A stored day stays a real day — Tuesday is still Tuesday.
A deload is a week of the same movements done deliberately easy — half the sets, around half the weight. It isn't time off and it isn't a wasted week: four weeks of climbing volume is the stimulus, and this is the week your body actually turns it into strength. Skipping it is how fatigue becomes a tweak.
How you like the app — nothing below changes your program.
Drills adapt to what you just trained — balance work after legs, tempo after pressing, putting only on recovery days.
Changes how running and walking distances are shown and entered. Sessions you've already logged convert automatically — nothing is rewritten.
Begins the next block on the date above. Edits and history are kept.
Discards this program and puts the stock four weeks back. Logged workouts are untouched. Coach only — it would undo what you built.
Tempo
Sets × reps × weight per week — the number that should climb.
This client's training, measurements, rounds, agreements, bookings and messages as one JSON file.
A lean build shows up here before it shows up on the bar.
Weight and squat numbers are proxies. Your scorecard isn't.
Mark when you're playing and the program checks itself against it — heavy lifting too close to a round is the main way this goes wrong.
18-hole rounds only. A falling line is progress.
What's booked, and the hours clients can book into.
Clients book one-hour slots inside these hours. Anything outside them isn't offered.
Leave the hours blank to block the whole day.
Everyone you coach. Anything waiting on you is flagged.
Tap ↳ on a movement to have it done in the rest between sets of the one above — press-ups between squat sets, say. Optional.
Claude reads how they have actually been training, the other six days of this week, and anything you say here — then proposes a session for this day. Nothing changes until you accept it.
Logs alongside whatever's already scheduled — it doesn't replace it.
Three ways to show a movement, and a client can tell them apart. Your own clip plays in the guide itself — you, filming the movement the way you coach it. Your pick is somebody else's video you have chosen, and opens in a new tab. Everything else falls back to a YouTube search, labeled as a search and explicitly not your recommendation. MP4 or WebM for clips, YouTube or Vimeo for links.
The library has written guides for 106 movements. Most of what a generated program draws from has none — the sheet still shows the reason and a video. This drafts guides for the movements actually in your clients' programs, and nothing reaches a client until you approve it: read each one, change what you'd say differently, then approve. Ten at a time, one call each.
The model proposes and you approve — which is backwards for the person whose name is on the program. Add a movement here and it is in the library for every client: the generator may pick it, the day editor lists it, and it is screened for injuries like anything else. A guide is optional; the sheet shows the reason and a search without one.
Added after the generator proposed them. Approving one makes it available for every client, with its guide.
What people see at your public page before they're clients. Changes go live as soon as you save.
The names of the sections themselves. Typed once, then usually left alone. Clearing one puts the standard wording back rather than leaving a section with no name on it.
Only real ones. The section is hidden on the page until there's at least one.
What's here, recorded once. Clients answering the intake get a one-press shortcut for "same as here", and anybody who trains only with you never sees the equipment question at all — their program is written against this instead.
Every booking says where it is. The first one came from the address on your public page. Add another when you start working somewhere else — closing one keeps the sessions that happened there.
What your clients see in the app: the name in "Ask …" and "Book a session with …". The name on your public page is separate, under Your public page above.
Everyone who can sign in. Every action here asks for your own password first — a signed-in session on its own isn't enough to reset somebody or add a coach.
A coach sees every client's training, health screening and injuries. There is no partial coach.
What the assistant, program generation and the daily notes have cost with Anthropic since the 1st.
A hard stop, not a warning. Past this, generation and the assistant pause until the 1st.
How many days before a client's row says something. Blank means the default, shown beside each one.
Your own mail server. With auto-send on, invites go out when you add a client and the plan PDF goes out when you approve one.
Gmail needs an app password, not your account password.
Everything consequential that has happened, newest first.
Program generation runs on Anthropic's API. Paste a key here to set or rotate it — no redeploy, no SSH. It is checked against Anthropic before it's saved, and never shown again afterwards.
On a shared phone, or when you're done. Nothing is lost — everything you've logged is on the server.
Light is the default — it reads better in bright sun. Dark is there for a garage at 6am, where dark surfaces cut glare.
How running and walking distances are shown and entered. Sessions you've already logged convert — nothing is rewritten.
Everything held about the client you are viewing — training, measurements, goals, agreements, bookings and messages — as a JSON file.
This removes your account and your entire training history. It happens immediately and it cannot be undone.