Four ways in, and they are not variations on one thing — they suit different people and cost different amounts of effort. Start with the one that matches how you want to work, not with the most powerful.
For a lifter who knows the sessions they want.
In the app · no code · minutes to an hour
Lay out your own programme in the member app: the cycles, the sessions inside them, the lifts in each session and the sets, reps and weights. It runs exactly like a built-in programme — the same logging, the same rest timer, the same charts and personal bests.
This is the route for “I already know what I want to do each week and I want the app to track it.” You do not need to describe how the weights progress in the abstract; you write down the programme.
Premium to build and to run. The 16-week signup grace counts as Premium, so a new account can use it straight away. The builder in the member app offers the double-progression engine.
For a coach or a programmer who wants a rule, not a spreadsheet.
In the coach console · writes real code · an afternoon the first time
A progression engine is the piece that decides what happens next: how a training max moves after a good session, when a deload lands, how a ladder adds a rung. Write the rule once and every programme that names your engine follows it, for every member, without you touching the sessions again.
It is a deterministic script against a fixed contract, with a test centre for trying it against real session data before anyone runs it. This is the most capable of the four and the one that asks most of you.
Premium, annual plan to author. A monthly Premium plan can view, preview and run engines but not write them. The coach console itself needs a paid subscription — the signup grace does not cover it.
For someone who knows the rule in words but not in code.
Your own AI assistant · copy, paste, converse · under an hour
The console hands you a prompt to paste into whichever AI assistant you already use. It interviews you about your rule one step at a time, writes the engine to our live contract, and hands back code you paste into the editor.
The part worth knowing: when you ask for something the contract cannot express, it is briefed to stop and draft a feature request rather than invent an API that does not exist. So a conversation that hits our limits ends with a request we can read, not with code that fails later.
Same plan as the engine builder, because it is the same editor at the end of it. The prompt is generated by us and stays in step with the contract automatically.
For someone whose AI agent should do the work directly.
Your agent, connected to us · no copying and pasting · minutes to connect
Connect an external AI agent — Claude, or any MCP-capable host — to your account over OAuth. It then builds and tests programmes and engines through our tools directly: drafting an engine, previewing it, creating a test and running it, without you moving code between windows.
You approve the connection on a consent screen that names exactly what the agent is asking for, and you can withdraw it. The agent works to the same brief as the prompt above, because it is literally the same brief.
Premium to connect an agent. Every action the agent takes is checked again as it happens, so a lapsed subscription stops it mid-session rather than at the next login.
The first is in the member app. The other three live in the coach console, which is where engines are written, tested and published.
Plans and what they include are described on the pricing page; this page describes the routes rather than the prices. If a route below sounds right but the plan does not, tell us — we would rather know which door you were trying to open.