A running app with a recalculated plan and a logbook
You’re probably wondering whether a running app isn’t just a PDF plan with a nice logo. Honestly, fair question. A fixed plan stops being much use the moment your community misses two sessions. Here is what our Cadence demo contains, screen by screen, and what it changes for the people who follow you.
Karim BenaliPartnerships Manager (creators), upd. , 5 min

The PDF sleeps in the phone
You’ve already sold or given away a plan as a PDF, right? The first weeks, it’s fine. Then comes a cold, a trip, a busy week, and the plan matches nothing anymore. The runner no longer knows whether to catch up, skip or start over from zero. They write to you in a private message, or they give up.
The plan itself is fine. It just doesn’t move when life moves.
An app in your name keeps your plan, redoes it when needed and logs what was run. It keeps the logbook for you, without you answering every message.
Open the app and see today’s run
On the demo’s home screen, the current week shows at the top, for example “Week 4 of 10”. Below, today’s run with its type (intervals in the example) and a “Start the run” button.
Further down, three counters: the streak in weeks, the kilometers of the month and the number of runs against the goal. Then a load chart by week, and a small note signed with the coach’s first name, which changes every week.
That note is the one you write. A subscriber comes back because someone is talking to them, rarely for a chart.
When the race changes the plan follows
In the Plan tab, a “Redo my plan” button. The runner picks their race, the date and the number of sessions per week, then touches “Generate my plan”. The weeks get recalculated and their logbook stays.
The app doesn’t invent sessions in your place. They come from your method. We build the engine that reorganizes them around the date and the chosen rhythm. The content and the tone are yours.
One caveat all the same: a recalculated plan is still a general plan. It doesn’t know your subscriber’s knee or their week of short nights. The demo doesn’t claim otherwise.
The home screen
The guided run
Paces that come out of a test
In the Tools tab, a paces section. The runner enters their latest test, in minutes and seconds, and the app derives their training paces from it. A message reminds them that a steady and honest effort is needed, otherwise the numbers are worthless.
The app also gives an estimate of what that means in a race, using Riegel’s rule. The demo presents it as indicative: race day depends on weather and course. We promise no finish time to your subscribers.
The sessions, the plan and the guided run adjust to these paces.
Race day fits on one screen
Still in Tools, the race plan. The runner gives their goal for the day, and the app proposes a strategy with kilometer, pace and split time. The cautious start is explained there: first kilometers that are too fast get paid for at the end. You probably already repeat that in your stories.
One button copies the pace band. One block covers fueling, another the warm-up and the start time. Everything you repeat before each race is filed in the same place.
If you organize a race with your community, this is the page everyone will open the day before.

The guided run with the timer
The Run tab starts today’s session, split into phases. The first is the warm-up. The screen shows a timer, a distance in kilometers that climbs and the time ticking by. The “Let’s go” button starts everything.
To test it, the demo speeds up time: a ×10 button changes the speed. Otherwise you’d wait the real length of the session to see the end of the run.
At the finish, the “Run complete” screen asks how it felt. The runner confirms and the run joins their plan. They can also close without confirming. I think that’s fair: nobody is forced to log a ruined run.
Logbook then shoes and records
The logbook is the journal of runs. You add a run by hand with the distance, the duration and the perceived effort, or you pull it from the guided run. At first it’s empty, and the demo says so.
The shoes section is a surprise. The runner declares their pair, each run adds to the current pair, and a marker recalls that people often change them between 600 and 800 km. The demo gives that marker as is. After that, it depends on the person and the terrain.
There are also the month’s kilometers, personal records and badges. It looks gimmicky. In practice, it’s what makes people open the app on Sunday evening to see where they stand.
On days without a run, Wednesday and Friday in the example, the app offers strength and mobility routines. The demo specifies that these are runner’s habits, not medical advice. Your app won’t give health advice either.
The plan
The tools
What won’t work
I’d rather tell you now. An app doesn’t run in place of your subscribers. If your community stays put, that won’t change. It only removes a few reasons to quit.
It doesn’t replace your one-to-one coaching either, if you sell it. It suits the person who wants a framework without taking individual coaching. Personalized coaching remains something else.
Finally, nobody can tell you how many subscribers will follow you. Our simulator gives an order of magnitude, and it calls itself a simulation, not a promise.
What it costs you and what it asks of you
On the money side, our main formula is nothing upfront: you advance €0. The app is something we build, host and keep running, and we are paid on the net: it’s what’s collected, minus VAT, payment fees, infrastructure, store commissions and refunds. For a more traditional development, the formula on a quote starts at €15,000 and we take no share of the sales.
What we ask in return on the nothing-upfront formula: 1 post and 4 stories a month. And what you keep: an option to buy the app out, at any time.
The exact terms are in the contract, which prevails. Read it before saying yes.
On the first 30-minute call, bring your latest plan, even as a PDF, even imperfect. We’ll look together at what can become the Plan tab of your app.