AI for cycling performance data

Cycling produces the cleanest performance data in sport. AI is how you finally use all of it.

What we’re actually working with

Power-meter data (FTP, TSS, IF, NP), HR, and HRV across multiple seasons — usually fragmented across Strava, TrainingPeaks, and Garmin.

Why doing this without a method fails

FTP tests come and go. Most riders never read why their best season was their best.

How the method handles cycling

Layer 01

Research

Have sourced AI summarise current evidence on polarized vs threshold training, recovery, and durability.

Layer 02

Ledger

Combine multi-year power, HR, and HRV exports. AI finds the patterns behind your best blocks.

Layer 03

Protocol

Build a focused 12-week block grounded in your own response to volume and intensity.

Three prompts you can use today

Paste any of these into the AI chat tool you already use. No setup.

FTP history

Here are 4 years of FTP test results plus weekly TSS. Find the training pattern that produced my biggest FTP gains.

Durability check

Across 12 weeks of long rides, calculate fatigue resistance (power drop after 2h vs fresh) and tell me whether it's improving.

Race build

Design a 10-week build to a target gran fondo using my real CTL/ATL/TSB pattern, not a generic plan.

How AI tools make cycling easier to live with — and understand.

You don’t need another app. These are the tools most people already have or can use for free, and the specific job each one does when you point it at cycling.

Research the literature

A sourced-search AI (e.g. Perplexity, ChatGPT search, Gemini)

Replaces an afternoon of tab-juggling on cycling with a cited summary in minutes. Ask it to mark every claim as primary study, review, or opinion — that one habit removes most of the noise.

Read your own data

A long-memory chat AI (e.g. Claude, ChatGPT, Gemini)

Paste weeks of notes, exports, or symptom logs about cycling in a single window. The AI spots patterns your seven separate apps hide from you, and remembers them next week.

Capture without friction

Apple Health + Notes (or Google Fit + Keep)

Already on your phone. Pulls cycling-relevant signals into one export and lets you jot context in seconds — no new subscription, no new dashboard to maintain.

Stream the raw signal

Your wearable (Oura, Whoop, Garmin, Apple Watch)

Stop reading the marketing score. Export the raw stream behind your cycling number and feed it to a chat AI — that's where the actual insight lives.

Build your own reference

NotebookLM (or any source-grounded notebook)

Drop in your lab PDFs, saved articles, and personal notes on cycling. Ask questions; the answers cite back into your own sources. Becomes a second brain you actually trust.

Turn data into a plan

A weekly review prompt

One scheduled prompt every Sunday: "Given this week's cycling data and notes, what changed, what's noise, what's the smallest experiment for next week?" Replaces three productivity apps and an anxiety spiral.

Common questions

Does it work without a power meter?+

Yes — HR and pace data work too, with the limits the course explains.

Can I use it with TrainingPeaks?+

Yes. The course shows the exact export.

Will it write my season?+

It can draft one. You verify against your own history.

The evidence — and where it breaks down

Six short briefs on what the literature, the devices, and the AI tools actually do when you point them at cycling. Read them before you change anything.

What the current research actually says about cycling+

Power-meter data (FTP, TSS, IF, NP), HR, and HRV across multiple seasons — usually fragmented across Strava, TrainingPeaks, and Garmin. Most peer-reviewed work on cycling sits in three buckets: mechanistic studies (small samples, tightly controlled), observational cohorts (large samples, noisy variables), and consumer-device validation papers (mixed quality, often vendor-funded). When you read AI-generated summaries on AI for cycling, treat the first two as signal and the third as buyer-beware. The 3-Layer method makes you triage these before they enter your personal ledger.

What your wearable or app is really measuring (and what it isn't)+

Consumer devices that surface a "Cycling" score almost always combine a small set of raw signals — accelerometry, optical heart rate, skin temperature, sometimes ECG — into a proprietary index. The score is opinionated, the raw stream is not. The Ledger layer of the method exports the raw stream so AI can analyze the underlying variables instead of the marketing score. That is where most insight lives.

Where consumer-grade cycling data is reliable vs noisy+

Cross-validation studies (Stanford, ETH Zürich, and several EU centres in 2023–2025) consistently show that wearables are most reliable for trend direction and least reliable for absolute values — especially night-to-night cycling. Use the data the way it is actually accurate: deltas over weeks, not single-night verdicts. AI is well-suited to this kind of rolling-window analysis; humans staring at one number are not.

Common confounders that distort cycling signals+

FTP tests come and go. Most riders never read why their best season was their best. The most under-discussed confounders are time-of-month variation, recent travel, alcohol with a 48–72 hour tail, ambient temperature, and any acute infection — all of which shift baseline values by more than most behaviour changes do. A good AI ledger tags these as covariates before drawing conclusions; a bad one quietly attributes the swing to whatever supplement you started that week.

What "good evidence" looks like — and what's hype+

Good evidence on cycling: pre-registered protocols, declared funding, raw data available, effect sizes reported with confidence intervals, replication in an independent cohort. Hype: single n-of-1 anecdotes generalised on social media, supplement-funded reviews, AI summaries that cite nothing. Have sourced AI summarise current evidence on polarized vs threshold training, recovery, and durability. Asking AI to mark every claim with "primary study", "review", or "opinion" before you act on it is one of the most useful prompts you can run.

How AI changes the picture for cycling in 2026+

Three shifts matter. First, long-context models can now read 60–90 days of your raw export in a single pass and find correlations no app dashboard surfaces. Second, sourced-search models (with citations) collapse the literature-review step from days to minutes — provided you verify the citations. Third, agentic workflows can run the same daily check-in you would otherwise skip. Build a focused 12-week block grounded in your own response to volume and intensity. The judgement layer — what to test, what to ignore, when to stop — is the part that stays with you.

Educational summaries — not medical advice. Cross-check claims against primary sources before changing anything material.

More on cycling

Everything we’ve published that touches this topic — refreshed automatically as new entries ship.

Case studies

Start with 10 free days.

The free 10-day email challenge teaches the same method on whatever data you already collect. No credit card.

More for people exploring cycling

Based on what you've been reading — always learning.

See all →