Steady keeps the plan you wrote connected to the training you actually ran. Bring in your own plan, sync what happened, and keep the block honest when sessions move, niggles appear, or the goal needs reassessing.
Use the builder for a simple, painless setup. Whether you think in mileage or time on feet, Steady accommodates that. Pick a recommended template, or start from a blank week and shape it day by day.
Steady recognises that injuries happen and that nothing about training is linear. It helps you keep your recovery routine on track, track every annoying niggle, and adjust your race goal when you need to.
Injuries are part of any sport. Steady helps you track all those annoying niggles which may turn into injuries (fingers crossed they don't).
If injured, Steady will help you keep your recovery routine on track and recognise that your race goal may change, and that's fine, too!
Because you're tracking the relevant metrics throughout your block, Steady generates a physio report. A more efficient overview of your mileage and niggle timeline than anything you'd type up the night before. It guides the conversation with your physio so you can spend the visit on actual physical diagnosis and treatment.
Not everything will be ready for day one, and there's a lot more in store.
I'm currently building Steady in private beta. Leave your email and I’ll send one note when Steady is available on the App Store.
I promise no marketing BS or data selling.
I like building my own training from things I’ve picked up online: Pfitz, Jack Daniels, Reddit, sometimes ChatGPT or Claude.
Since I started running more seriously, the hardest part has not been finding a plan. It has been keeping the plan up to date once life happens. Runs move, niggles appear and injuries sadly happen. The spreadsheet (or notebook) says one thing, Strava says another, and suddenly I’m taking screenshots, checking notes and updating many tools at once. I don't think that's how it should be.
It felt too cumbersome to keep track of the changes, and I still felt like I was missing parts of the picture: niggles, injuries, fuelling and all the small context that ends up mattering.
That’s why I’m building Steady: to keep all of it in one place. The training plan you bring, the runs you actually do, the changes you make, and the context behind them. If you need to see a physio, that history should already be there.
I’m starting small, with plenty of ideas for where Steady could go. But more importantly, I want it shaped by runners who know what it feels like to be overwhelmed by running admin.
Cyprian