The plan that answers back
Swipe or use arrow keys to explore the full week
They ask
Most plans answer that in week six, when you’re already behind. PaceBeats answers it before the week is built. It checks the hours you have, the biggest session you’ve completed, and whether you can physically hold the intervals it wrote.
Next week · a week ahead
Next week’s plan needs about 45 minutes more than your calendar has. I’ll build the best week I can with your current hours — but if you can find that time, it fits.
Tap a day to add 15 min
Next week · Tuesday
To your watchThreshold intervals
1h15m · 62 load
Workout structure
| Step | Plan | Target |
|---|---|---|
| Warm-upeasy running | 15min | 5:55–6:25 /km |
| Threshold cruise3min easy jog between | 4 × 10min | 4:45–4:55 /km |
| Cool-downeasy running | 11min | 6:10–6:50 /km |
Before a week is built, PaceBeats checks the ask against the hours your calendar actually gives you. If it doesn't fit, you get the verdict a week early and see whether the problem is your availability or the plan's arithmetic.
Every interval is checked against how long a real athlete can hold that intensity: bike Z5 for 3–8 minutes, run I-pace under 5, swim CSS reps of 100–400 m. A 45-minute “threshold step” gets flagged before it reaches you.
No single session goes more than about 10% beyond the biggest session of that type you've completed. Your history sets the ceiling, not an ideal template.
Weekly load can’t jump by more than your own derived ramp cap. Running ramps stay at 65% of that cap because impact injuries come from running. An independent brake compares your 7-day load with your 28-day load.
They ask
Tell it, in your own words, and next week is built around what happened instead of the week you were supposed to have. Missed sessions do not get stacked onto the next two days. There is no guilt. A gap between plan and actual is data, not a character flaw.
Try asking
Swipe or use arrow keys to explore the full week
“Travelling Thursday, keep the long ride.” PaceBeats maps that to a closed set of intents and applies it through rules. Anything it cannot honour is shown to you instead of quietly dropped.
Set a constraint mode in plain language by describing what's going on, what you can still do, and what training should aim for. The plan reorganizes every week around that mode until you turn it off.
The preview generates a week without writing it to your plan. Say “still too much” and PaceBeats previews a smaller version while keeping the days you already liked. When you activate it, PaceBeats persists exactly the week you approved.
Shrink-only mode removes every action that would raise load. The “did that go as planned?” prompts go quiet because the plan already expects you to be off-pattern.
They ask
Nobody, until you do. Sometimes you ask — and sometimes PaceBeats speaks first: it reads the rides and runs you actually record, and when your own power says the threshold on file is out of date, it says so and then waits. Either way the change arrives as a card you approve, with the before and after in plain numbers. Keeping your current plan takes one click and costs you nothing.
Coach suggestion
On your Saturday ride on Aug 1 you held 332 W for 20 minutes — your best 20-minute power in the last four months, and 11% above the 300 W on file. Bike FTP is roughly the highest power you could hold for about an hour flat out, and a hard 20-minute effort usually sits about 5% above it, which puts your real FTP nearer 315 W. You entered 300 W on Apr 13.
What changes
Set your bike FTP to 315 W (from 300 W)
Nothing changes unless you confirm.
Recent decisions
3 decisions, 1 waiting · Show all →
Today
Update your bike FTP
Keep Wednesday clear this week — I'm away for work.
Wednesday cleared: 2 sessions removed, load 500 → 423.
Saturday, August 1
Move your long ride to the day you actually ride
Wednesday, July 29
Ease your next run tempo
Why this week
Load held at your ramp capGuardrail
The season plan asked ~540 load this week. Held to 500 — the top of your own ramp band.
A question PaceBeats raised on its own sits open until you answer it. Dismiss it and it does not happen — nothing is applied without an explicit yes. Say yes to a new threshold and it shapes the sessions built from that point on; the sessions already on your calendar keep the numbers they were given.
The same engine function computes the before → after you see and runs when you confirm. After you confirm, the server re-derives and re-validates everything. It never trusts your browser's version of the story.
Declining is one guilt-free click. Your plan stays as-is; we don't penalize or nag you, and we won't ask whether you're sure. Undos are always free.
You get a full, paginated ledger of every proposal and what you did with it, plus a strip showing which decisions are actively shaping this week and whether each one was your choice or a guardrail we applied. A suggestion for a week that has since been rebuilt quietly expires instead of applying the wrong change.
They ask
You get a rep-by-rep readout of the workout you actually did. Every prescribed step is matched against what your watch recorded and gets its own verdict. It mirrors the session instead of grading you.
Threshold 4×10′· Wednesday
78%| Step | Plan | Done | Target | Actual | Verdict |
|---|---|---|---|---|---|
| Warm-up | 15min | 15min | 120–160 W | 141 W | On target |
| Interval 1/4 | 10min | 10min | 250–270 W | 258 W | On target |
| Recovery 1/4 | 5min | 5min | -- | -- | Done |
| Interval 2/4 | 10min | 10min | 250–270 W | 264 W | On target |
| Recovery 2/4 | 5min | 5min | -- | -- | Done |
| Interval 3/4 | 10min | 10min | 250–270 W | 281 W | Above target |
| Recovery 3/4 | 5min | 5min | -- | -- | Done |
| Interval 4/4 | 10min | -- | 250–270 W | -- | Skipped |
| Recovery 4/4 | 5min | -- | -- | -- | Skipped |
| Cool-down | 10min | 6:15 | 100–140 W | 118 W | 63% |
Threshold 4×10′78%
PaceBeats matches each prescribed step to the recording with the device's own step index, sequence alignment, or time slicing. The table still works when you skip the structured workout button.
Your weekly execution score compares the time you spent in each zone with the intensity you planned. Redlining easy days or sandbagging intervals won't look like a well-executed week.
A trimmed warm-up never triggers a question. Minor deviations stay out of the conversation. When something real happens, your explanation shapes future weeks.
They ask
To a date you picked. Enter your races and PaceBeats lays out every week from today to race day: base, build, peak, taper. It anchors the plan to your race dates instead of a template’s week one, so you see the whole plan before you commit to anything.
You peak for the A, perform at the B, and use the C for pacing and logistics practice with no taper. Move or reprioritize a race and PaceBeats rebuilds the season, then tells you what changed.
Every race gets a required build runway from its distance, its priority and your capacity. An under-prepared goal race is named up front, not discovered in week twelve.
PaceBeats carries your fitness, fatigue and form forward day by day through the taper, then tunes the taper to put you in the race-ready band on race day.
Preview the phased season build for free during onboarding. You see your actual plan as a chart and approve it before anything activates.
The race predictor uses your own thresholds and physiology to give you a range and per-leg splits. Its “what this projection considers” checklist names every layer it ran: course profile, the climate normal for your date, T1 and T2, running off the bike, and whether your bike plan is even pace-able. It also names the passes still waiting on data and what would unlock them.
The connection
PaceBeats starts with Garmin. Your history and recovery signals flow in, and the sessions you approve land on your watch overnight.

Garmin Connect
required · biometrics + activities
PaceBeats
unifies context, builds the week
Your watch
workouts land, ready to start
Strava
optional · finished sessions out
Garmin recovery signals shape next week’s plan — they won’t rewrite today’s workout on you.

Connect through Garmin’s consent screen and choose the data categories to share. PaceBeats never sees your password. Finished sessions reach us within minutes, so you don’t have to press “Sync now.” We decode the FIT record stream for per-second pace, heart rate, and power. That also lets us recover your true pool-swim time instead of Garmin’s elapsed-only number.
Your swim, bike, and run sessions upload as native Garmin workouts with the exact target bands shown in the app, scheduled for the right day. Tomorrow’s session is waiting when you wake up. Strength sessions stay in the app. Garmin doesn’t support them, and we’d rather say so than fail silently.
PaceBeats can write the coached title and description to your Strava activity. Strava is outbound only, and PaceBeats sends only what you turn on. Withings weigh-ins provide weight and body-composition data.
PaceBeats builds your profile from your Garmin data, and a Garmin connection is required at sign-up. If you record your training somewhere else, this isn’t the right tool for you yet. We’d rather tell you before you sign up. You can also upload an individual .FIT, .TCX, or .GPX file for any session. Uploaded files get the same analysis.
Pricing
Bring your training data and see every metric for free: fitness, fatigue, form, load, efficiency, recovery, records, and a full race prediction. Every new account starts with 14 days of full Performance. No card required. Coaching starts at €24 a month billed annually, or €29 month to month.
Free
No credit card required
Bring your data. See every training metric for free, forever.
Every new account starts with 14 days of full Performance. No card required.
€24/mo
Billed annually · €290/yr · 2 months free · €29/mo month to month
PaceBeats rebuilds your full adaptive plan each week from your free metrics and proposes changes for your approval.
Everything in Starter, plus
€66/mo
Billed annually · €790/yr · 2 months free · €79/mo month to month
The full coaching experience for athletes chasing a result. Every 14-day trial runs on Performance.
Everything in Age-Grouper, plus
Your 14-day trial runs on Performance. Keep it and nothing changes.
Connect your Garmin, set your race, and see your whole season, including its phases, load, and hours, before you commit to anything.
See my plan