AI Coach for Cyclists: Power-Based Training, FTP, and What the Data Can Do

Cycling is the sport where AI coaching has the best raw material. A runner's pace bends with hills, wind, heat, and GPS error. A power meter measures the work itself, at the crank or the pedal, in watts, the same way every ride. 250 watts on a cold Tuesday in February is the same 250 watts on a July climb. That repeatability is what a coach, human or AI, needs before any plan means anything.

So the question for a cyclist is not whether the data is good enough. It is. The question is what gets done with it. Your head unit and your platform of choice already compute most of the classic numbers. An AI coach earns its place in the layer above the math: reading those numbers against your strength work, your sleep, your food, and your actual week, then adjusting the plan and explaining why.

This guide walks through power as the signal, what the device ecosystem already handles, what it structurally cannot, what an adaptive cycling plan looks like in practice, and the honest limits.

Power is the signal

Everything in structured cycling hangs off one anchor: FTP, the highest power you can hold for roughly an hour. From that number come your training zones, your interval targets, and your load scores. Test it with a 20-minute protocol or estimate it from recent rides, then retest every 6-8 weeks in a build. The FTP calculator runs the standard estimate, and the power zones tool turns the result into watt ranges for each zone.

Two derived numbers do most of the analytical work after that.

Normalized power answers the question a raw average cannot: how hard did that ride cost you? A punchy group ride with surges and coasting might average 180 watts but cost your body what a steady 230 would. The weighting math behind that is covered in the normalized power explainer, and you can run the calculation on any ride yourself.

Training load stacks those ride costs into a picture over weeks. One number per ride, scaled by how hard it was relative to your FTP and how long it went. Track the rolling sum and you can see fatigue building before your legs report it. The Training Stress Score guide covers the mechanics and what the rolling numbers mean.

A third model sits underneath both for riders who race short and hard. Critical power describes the boundary between the effort you can sustain and the effort that burns a finite reserve above it. It comes from two or three all-out tests at different durations and predicts what you can hold for any time in between. Useful for pacing a 10-minute climb or a pursuit effort where FTP alone is too blunt. The critical power tool runs the model from your test results.

None of this requires an AI. It requires arithmetic and a power meter. Which is exactly the point: cycling hands a coach clean, quantified inputs that most sports cannot.

What your head unit already does, and where it stops

If you ride with a Garmin, the device ecosystem computes a lot on its own. Auto-detected FTP. Load ratios. VO2 max trend. Recovery time after each ride. Daily suggested workouts that shift with your overnight HRV. For a cyclist who rides, looks at the suggestion, and follows it, that free layer is genuinely useful, and the Garmin AI coach guide goes deep on what it does well.

The ceiling is structural, and it has three parts.

It cannot see training it never records. Squats on Monday do not enter the ride-load model. They show up as unexplained stress in your HRV, which the algorithm reads as noise. Three heavy gym sessions plus a long ride registers as one hard day. For a cyclist doing serious strength work alongside the bike, the watch is planning from half a picture.

It cannot ask you anything. The algorithm produces a session type. It does not know your race moved up three weeks, that your left knee complained on the last climb, or that work travel eats Thursday. You interpret the suggestion against your life. The suggestion never interprets your life.

It has no cross-domain view. Ride data, sleep, and HRV live in the model. Your food does not. Your gym log does not. Your last conversation about goals does not exist, because there was no conversation.

Deterministic power math is a solved problem. Context is not. That line is where an AI coach starts.

What an adaptive cycling plan looks like

An adaptive plan is one that gets rewritten when reality diverges from the template. Four situations come up for every cyclist, and they are where the difference shows.

FTP moves. Six weeks into a build, your threshold has crept up. Static plans keep prescribing the old watts, so your "threshold" intervals drift down to sweet spot and the stimulus quietly softens. An adaptive coach catches the signal in your recent rides, prompts a retest or adjusts the estimate, and rewrites the zone targets so hard days stay hard. If you race where the road tilts, watts per kilo matters more than raw watts; the power-to-weight tool puts a number on it.

You miss sessions. Work runs long, a kid gets sick, it rains for four days. A template leaves a hole and moves on. A coach redistributes: the key interval session survives, an endurance ride shrinks, the week's load target gets recalculated instead of abandoned. The skill in coaching missed weeks is knowing which session was the point of the week. Volume is replaceable. The quality stimulus usually is not.

Your body pushes back. HRV trending below baseline for three mornings, resting heart rate up, sleep short. The consensus on morning readiness signals is clear enough to act on: pushing threshold work into a suppressed state buys fatigue, not fitness. An adaptive coach downgrades Tuesday's intervals to zone 2, holds the pattern for a day or two, and reschedules the quality work for when the trend recovers. The framework for reading those signals over weeks is in the HRV-guided training guide.

Indoor and outdoor are different rides. An hour on the trainer has no coasting, no descents, no traffic lights. The same interval set costs more inside. A plan that treats trainer hours and road hours as interchangeable overloads the indoor weeks. The adjustment is small but it compounds across a winter.

The through-line: the numbers stay the same numbers. FTP, normalized power, load. What changes is that something reads them daily, against everything else in your life, and rewrites the week instead of waiting for you to notice.

The honest limits

An AI coach does not improve on the power math. Load scores, normalized power, FTP detection from ride files: this is deterministic arithmetic, and your device ecosystem computes it precisely. An AI reasons about those numbers. It does not calculate them better. Anyone claiming otherwise is selling something.

Bike fit is human territory. Saddle height, cleat position, reach: these need hands, a trained eye, and you on the bike in front of someone. No data stream substitutes.

Pack skills too. Cornering in a group, reading a break, holding a wheel at 45 km/h: learned on the road, in groups, over years. A coach can structure the fitness underneath. The craft is yours to build.

And if you are chasing a national-level result or managing a complicated injury, hire a human coach. The relational accountability of a person who notices you went quiet, and the judgment earned from hundreds of athletes, is worth the money at that level. For the cyclist training 5-12 hours a week around a job, the AI coach is the practical call: available every morning, reads more data than a human has time for, and costs less per month than one coaching consult.

What Movement Rebels does for cyclists

Concrete, so you can judge it against the list above.

Garmin Connect sync, both directions. Rides, power data, HRV, sleep, and training load flow in. The coach pushes structured workouts back to your Garmin: warm-up, intervals with watt targets, cooldown. You press start and the device runs the session. On iOS, the native app also reads Apple Health.

A debrief after every ride. Each completed synced ride triggers an automatic coach analysis in your chat thread. Lap and power breakdown in plain language: where the power faded, how the effort compared to the plan, what it means for tomorrow. One paragraph, not a dashboard.

Weekly plans from the full picture. When the coach writes your week, it reads the last 14 days of ride and recovery data, your strength log, your nutrition entries, and a persistent athlete profile built from every conversation you have had with it. Tell it your knee is sore once, and it remembers when it programs your next block.

The rest of the stack in the same app. A strength library of 3,600+ workouts for the gym days. Rebel Fuel sets macro targets that follow the day's session, so carbs scale up when the ride is hard and settle back on rest days. Power data makes the fueling side of cycling unusually precise too: work in kilojoules converts to calories burned at close to one-to-one, which is why a power file beats any heart-rate estimate for calculating ride calories. Recovery tools round it out, and a morning brief reads your overnight data and tells you what today should look like before you decide anything.

No social feed. No kudos, no segments. Strava sync exists for exactly that reason: your rides land in your friends' feeds automatically. Keep Strava for the social layer, run the training here.

You can ask questions. "My FTP test felt terrible, was it the heat?" "Race moved to five weeks out, what do we cut?" "Should the long ride move to Sunday?" The coach answers from your data, in your thread, with the context of everything above.

If your calendar includes triathlons, the triathlon coaching guide covers the multi-sport version of this. And for the broader comparison against hiring a person, read AI coach vs personal trainer.

Pricing

Movement Rebels is free for 7 days: full coach, full Garmin sync, full strength library, Rebel Fuel, recovery tools, no credit card. After the trial, the subscription is $20/month.