Examples
Example conversations.
Nine kinds of athlete.
From a first-timer’s “where do I even start?” to a PB chaser’s bad day. These are written samples, but every feature they show is real, and your coach works from your own training.
No pace pressure yet. We build the habit first, then the speed. I’ll draft week one now - change anything you don’t fancy.
New to this? It starts where you are.
You don’t need to know your zones or what a tempo is. Tell it your goal and it builds a beginner-friendly plan from the runs you’ve actually done, explaining everything in plain English as you go.
Mon Easy 8 km Tue Threshold (moved up) Wed Long run 18 km (moved up) Thu-Sat Rest (travel) Sun Easy 6 km58 km becomes 50 km. One lighter week at this stage won’t cost you any fitness.
Life happens. The plan adapts.
Tell it about travel, illness or a busy week in plain words, or a voice note. It reshapes the week to keep the sessions that matter, shows you the change, and waits for your OK.
Tell me how it feels tomorrow and we’ll take it from there.
It remembers the last niggle, and what fixed it
It remembered the March niggle and how you recovered from it, and eased the week off before it could turn into something bigger.
Your long run went from 16 to 19 km in two weeks, and your weekly total from 47 to 61 km. That’s a bigger jump than your body is used to, and a niggle like this is often the result.
Let’s drop this week’s long run back to 16 km and see how the knee responds. If it’s still there in 7-10 days, or gets worse mid-run, see a physio - don’t wait.
Logged, so I can keep an eye on it.
It connects a niggle to what caused it
Mention a niggle in plain words. It checks it against your recent training, spots jumps in volume, and keeps tracking it, so small problems don’t become big ones.
You’re not losing fitness. You had two hard days too close together, so the legs were already spent. Easy tomorrow, and I mean properly easy.
A bad session, explained rather than judged
It reads your splits and recent training, and finds the reason behind the heavy legs, instead of just telling you the session went badly.
Your recent races and threshold sessions put you at 43:30-44:30 for 10K. You’re carrying a bit of fatigue right now, which is exactly what a taper clears.
Plan: two easy days, one short sharpener (4 x 1 km) on day 8, then easy to the start line. You’ll arrive fresh.
Know your actual fitness, not a guess
Race predictions come from your recent results and training paces (Jack Daniels’ method) and how much fatigue you’re carrying, then it plans the taper to get you there fresh.
Every sport counts towards your load
It reads every sport you log - run, ride, swim, tri and hike - so its advice accounts for all your training, not just one slice of it.
Want the full picture? Type
/aboutme to read everything I hold, and correct anything I’ve got wrong.
Ask what it knows, and correct it
Most apps forget you between sessions. This one builds a picture of you over months and plans, and keeps it honest. For the first two weeks it even tells you it’s still learning you.
You’ll enter your Garmin email and password on a private HTTPS form on openpacemaker.com. Your password never goes through this Telegram chat.
Your plan, straight to your watch
Link Garmin Connect once and each new week can go to your watch as structured workouts, with pace targets and intervals. It also reads your Garmin sleep, HRV and resting heart rate each morning.
On the password: Garmin doesn’t offer a sign-in button for apps like this one, so you enter it on our private page. It’s used once to get a connection token from Garmin, then discarded.
Coaching a group? See how a human coach works alongside the AI.