What should road cycling YouTubers offer on Patreon?

Road cycling YouTubers should offer power file annotation as their core patron exclusive because it is the analytical layer the video deliberately omits for pacing and accessibility. For each significant training session or race, the annotation covers: the target power zones and why (not just 'zone 2' but what physiological adaptation zone 2 work at this volume produces and how it connects to the goal event six weeks out); the training stimulus intended per interval set (the recovery duration between intervals is a design decision — shortening recovery increases metabolic demand, extending it shifts emphasis toward the neuromuscular quality of each interval); the session RPE compared to the power numbers and what that divergence signals (an RPE-7 session at FTP-minus-eight-percent means accumulated fatigue from earlier in the week is suppressing output — which is expected and acceptable — versus a nutritional deficit or inadequate sleep the night before, which require different responses); the fatigue context from the preceding training week (a threshold session on day five of a load week should feel different than the same session on day two of a recovery week, and the annotation explains what 'different' means quantitatively and qualitatively); and the post-session assessment (what the creator expected to feel by the end of the final interval, whether that signal appeared, and what they are tracking in the next 48 hours to assess whether the session landed as intended). This annotation cannot be derived from the Strava file by the patron — the numbers are visible, but the design intent, the RPE calibration, and the training context are not.

How does the Apple Tax affect cycling creator Patreons?

Cycling audiences have lower iOS rates than most YouTube niches because the sport creates habitual desktop behavior through data analysis. Serious cyclists sync Garmin, Wahoo, or Hammerhead devices to desktop-first training platforms — TrainingPeaks, GoldenCheetah, WKO5, Intervals.icu — and spend significant time analyzing data on a screen that is not a phone. This desktop engagement context lowers the share of patrons who encounter the Patreon subscribe button on an iOS device. Road cycling YouTube: 35–50% iOS. Gravel and adventure cycling YouTube: 45–60% iOS (lifestyle-adjacent, more casual mobile viewing). Cycling coaching content: 30–45% iOS (data analysis is definitionally desktop work). Cycling podcasts: 60–70% iOS (listen-while-riding converts to mobile). Cycling Instagram and Twitter: 70–80% iOS. A road cycling YouTuber at $800/month with 42% iOS faces approximately $100/month ($1,200/year) in Apple fees from November 1, 2026. A gravel creator at $500/month with 52% iOS: approximately $78/month ($936/year). The desktop skew means cycling creators lose a smaller percentage of revenue to Apple than most content categories — but the absolute dollar amount still warrants the free mitigation step of enabling Patreon's web-only billing toggle before October 31, 2026.

What makes gravel cycling Patreon content different from road cycling?

Gravel cycling Patreons work differently from road cycling content because the patron deliverable is a functional pre-trip planning document rather than a training analysis tool. Route documents for a gravel adventure contain the information layer the vlog edit necessarily compresses out: the elevation profile pacing strategy with specific power targets for early climbs (gravel race pacing logic differs from road race logic because the priority in the opening miles is protecting traction and positioning, not power optimization), surface condition sources and their reliability by season (a rider who consulted three sources for a specific stretch of forest road and found conflicting reports documents which source was right and under what conditions), resupply logistics with actual store hours and whether patrons can rely on the listed water sources in dry season, gear selection reasoning with the specific conditions that drove each decision (why a 40mm tire rather than 38mm for this particular course surface), and a section titled 'what I would do differently' covering navigation errors, pacing mistakes, and kit choices the creator regrets. A patron planning to ride the same route has a document that saves twenty hours of personal research. A patron in a different geography has the decision-making framework — how to assess a route's surface variability, how to evaluate resupply options, how to pace opening climbs when the surface creates a power-output ceiling the gradient alone does not.

Explainers · 2026-06-21 · ~3,800 words

Patreon for cycling creators: complete 2026 guide — power file annotation, gravel route documents, cycling coach periodization, and the Apple Tax

Q: How do cycling coaches structure their Patreon differently from general fitness coaches?

Cycling coaches structure Patreon around periodization documentation and athlete case studies rather than workout templates, because cycling physiology is complex enough that the reasoning behind the plan is as valuable as the plan itself. A general fitness coach can offer a twelve-week program and have it work reasonably well for a broad range of patrons. A cycling coach's periodization is event-specific, fitness-specific, and time-of-year-specific in ways that a generic plan cannot address. Three tiers: Rider ($8–12/month, training philosophy posts and Discord with workout Q&A organized by discipline and event type), Training Diary ($15–25/month, the coaching documentation behind each training block: what physiological adaptation the block targets and why at this point in the season, how the training week's structure distributes stress and recovery to produce the intended adaptation without overreaching, what markers the coach is watching to assess whether the adaptation is occurring — power at threshold, lactate profile changes, HRV trends — and what adjustments are triggered if the markers diverge from expectation; plus anonymized athlete case studies showing how the coach responded to a specific challenge: a week of illness during a peak load block, a race that revealed a weakness in the preparation, a plateau in threshold power that required diagnosing the underlying cause), Race Coach ($60–120/month capped 5–8, monthly session where patron submits recent training data, upcoming race schedule, and specific performance challenge, and receives written assessment and training prescription specific to their current fitness profile). The Training Diary tier retains because each block's documentation accumulates into a coaching philosophy archive — a patron who has followed for a full racing season has the reasoning behind every phase of preparation and a growing library of athlete case studies organized by problem type.

Cycling Patreons retain when they deliver the analytical and functional layer the YouTube edit compresses out: the design intent behind each training session, the planning research behind each adventure route, and the periodization reasoning behind each coaching block. The cycling audience's desktop-first engagement habit produces lower iOS rates than most sports niches — which means a structural advantage against the Apple Tax, and a patron base that subscribes through web browsers at above-average rates.

Creator types and tier structure

Road cyclists and training content creators

Tier structure: Rider ($5–8/month, early access to training videos, Discord organized by discipline and goal event type, monthly group Q&A on training methodology), Training Diary ($12–18/month, power file annotation and session documentation for each significant workout or race), Coaching Session ($50–100/month capped 6–10, monthly 45-minute session where patron submits their own power file or race result and receives analysis specific to their physiology and training context).

The Training Diary tier's power file annotation is the core exclusive. For each significant session, the annotation covers five elements. First: the target power zones and physiological rationale. Zone 2 work is not just "aerobic base" — the annotation specifies what adaptation zone 2 at this volume produces (mitochondrial density increase in slow-twitch fibers, fat oxidation capacity at moderate intensity, cardiac stroke volume), how the session duration connects to the minimum effective dose for that adaptation, and how it fits the macrocycle at this specific point in preparation. Second: the training stimulus intent per interval set. The rest interval duration between VO2 max intervals is a design variable, not an afterthought — 3 minutes recovery emphasizes metabolic demand per interval while 5 minutes recovery shifts the emphasis toward the peak neuromuscular quality of each effort. The annotation explains what the designer was optimizing for. Third: RPE vs power divergence notes. A session that produces FTP-minus-eight-percent power at an RPE of seven is normal at the end of a load week — accumulated fatigue suppresses output, and that suppression is the evidence the training load was sufficient to stimulate adaptation. The same numbers the day after rest suggest a different problem: a nutritional deficit, inadequate sleep, or early-stage illness. The annotation records what the creator observed, what they concluded, and what they are watching in the following 48 hours. Fourth: fatigue context from the preceding week. A creator who ran six hours the previous week and is now executing a threshold session on day five documents how that context shaped the session design — shortened warm-up, reduced interval count, lower power target, or decision to extend recovery to the following day. Fifth: post-session assessment signal. What the creator expected to feel by the end of the final interval (respiratory rate, leg heaviness, the specific quality of effort that indicates the target intensity was reached versus exceeded), whether that signal appeared, and what it means for the next session's design.

None of this is derivable from the Strava file. The power numbers are visible; the design intent, the RPE calibration, and the physiological framework are the creator's expertise and cannot be inferred by the patron from the data alone. A patron who follows the Training Diary for a full training block — eight to twelve weeks — accumulates a complete annotated record of how a serious cyclist prepares for a specific event type. That record does not exist in any training textbook because it is specific to this creator's physiology, this year's fitness trajectory, and the specific event being targeted.

Gravel and adventure cyclists

Tier structure: Follower ($5–8/month, early access to adventure content, Discord, weekly training notes), Route Planning Pack ($12–18/month, the complete pre-trip research document for each adventure: elevation profile pacing strategy, surface condition research, resupply logistics, gear selection rationale, GPX file with embedded waypoint notes, and the post-trip revision notes), Adventure Companion ($40–75/month capped 8–12, monthly 30-minute session where patron submits their own planned route and receives a planning review: pacing strategy, logistics gaps, gear questions).

The route planning document is the most retentive content gravel creators can produce because it is genuinely functional for patrons planning similar rides. The document structure: elevation profile analysis and opening-miles pacing strategy (gravel race and long-ride pacing differs from road race pacing because the priority in the first hour is often positioning and traction management rather than power optimization — the annotation explains what the creator was targeting in the opening miles and why, not just what power they rode); surface condition sources (if the creator consulted GPS tracks from previous riders, a local trail association report, and satellite imagery for a specific unmaintained forest road stretch, the document records which source was most reliable and what conditions the sources disagreed about); resupply logistics with operational detail (store name, hours, what it actually carries versus what the website claims, whether the creek crossing at kilometer 87 ran in the creator's ride and at what time of year — information that trip reports typically omit); gear selection reasoning (why 40mm tires rather than 38mm for this specific course surface mix, what the mud percentage in the early miles meant for tire compound selection, why the creator chose not to bring a third bottle despite the resupply gap); and the post-trip revision section covering navigation errors (where the GPX track should be corrected), pacing mistakes (where the creator went harder than planned and what the cost was later in the ride), and kit choices they regret.

A patron planning the same route has a document that replaces twenty hours of personal research. A patron in a different geography — which is most patrons — gets the decision-making framework: how the creator evaluated surface variability, how they planned resupply for a long unsupported stretch, how they approached pacing a course with a late major climb. The framework value is what retains patrons who will never ride the specific routes covered.

Cycling coaches building in public

Tier structure: Athlete ($8–12/month, training philosophy posts, Discord organized by discipline and ability level, monthly group Q&A on periodization methodology), Coaching Diary ($15–25/month, the periodization documentation behind each training block and anonymized athlete case studies), Race Coach ($60–120/month capped 5–8, monthly coaching session with power file or race result submission and individualized written assessment).

The Coaching Diary's periodization documentation goes deeper than what any training book provides because it is specific to real athletes in real training contexts. Each block documentation covers: the physiological target for the block (what adaptation is being sought and why at this point in the season — a base block four months from a peak event has different targets than a sharpening block four weeks out, and the annotation explains the rationale in terms the patron can apply to their own training timeline); the training week structure rationale (how the sessions are distributed across the week to produce the intended adaptation — why Tuesday is threshold and Thursday is a recovery ride rather than the reverse, what the rest day placement is optimizing for, how the long ride fits the accumulated fatigue pattern of the preceding days); the monitoring markers (what the coach is tracking to assess whether the adaptation is occurring — power at a specific heart rate, morning HRV trends, RPE calibration during standard sessions — and what values signal the block is working versus the athlete is accumulating fatigue faster than they are adapting); and the adjustment protocol (what triggers an unplanned rest day, what triggers a session reduction, what triggers a block extension versus moving to the next phase).

The anonymized athlete case studies are separately valuable because they show the coaching decision process in response to the kinds of disruptions every athlete experiences. A case study covering how the coach responded to a training week lost to illness during a peak load block — whether to attempt to compress the missed load, shift the peak event preparation timeline, or write off the block and trust the prior fitness — gives patrons a decision framework they can apply when the same situation occurs for them. A case study covering a plateau in threshold power that persisted for six weeks documents the diagnostic process: what the coach checked first (sleep quality, nutrition adequacy, training monotony), what the intervention was, and whether it worked. This kind of operational coaching knowledge is not available in any published training guide because it requires real athlete data and real decision-making under uncertainty.

Cycling vloggers and storytelling creators

Tier structure: Follower ($5–8/month, early access to vlog episodes, Discord), Behind the Ride ($12–18/month, the production and planning layer the vlog edit removes: pre-ride research document, gear list with selection reasoning, mechanical preparation notes, budget breakdown, and the post-ride honest assessment), Ride Partner ($35–60/month capped 10–15, monthly 30-minute route planning session where patron submits their own planned trip and receives planning review and gear discussion).

The Behind the Ride package accumulates into something different from any individual episode: a library of documented decisions across a range of conditions, distances, terrain types, and budgets. The pre-ride research document covers what the creator was planning before they rode — not the romanticized version in the vlog opening, but the actual logistics: how they found the route, what alternatives they considered and rejected, what they were worried about, what contingency plans existed. The gear list with selection reasoning is operational rather than promotional — why this specific saddle bag for this specific trip (volume vs packability vs mounting security), why this rain jacket rather than the one that looks better on camera, what the creator has stopped carrying after learning it is not worth the weight. The mechanical preparation notes document what the creator checked before departure, what they found, and what they fixed — the pre-adventure bike check that viewers never see because it is not cinematic. The honest post-ride assessment covers the gap between what the creator said in the vlog and what they actually experienced: the sections they found harder than expected, the gear choices they regret, the moment where the narrative arc of the vlog required glossing over a logistical frustration that was real and significant. The budget breakdown is the most-requested item cycling creators report from patrons — the actual cost of a trip, broken down by category, with notes on what was unavoidable versus what was an upgrade choice.

Power file annotation: what makes it retentive

The question for any cycling creator building a Patreon is not whether to share power files — Strava is public, and the numbers are not the exclusive. The question is what to annotate and at what depth. Annotations that retain patrons have three structural properties.

First: they are specific to the creator's physiology and training context. A 45-minute threshold session at 285 watts means something different for a creator with a current FTP of 310 than for one with a current FTP of 280. The annotation is only useful if it tells the patron what 285 watts represents relative to the creator's current capacity and why that specific intensity was targeted rather than a different one. Generic descriptions ("I kept it in zone 3 and felt good") are table stakes; specific calibration ("this was 91% of last month's 20-minute test, which is the upper end of sweet spot for me — above this intensity the fatigue cost increases faster than the training stimulus for this block's target adaptation") is what retains.

Second: they document the decision-making process, not just the outcome. The most valuable moment in a training week is when the creator deviated from the plan and why. An unplanned rest day, a session cut short, a power target revised downward mid-interval — these moments are invisible in the Strava file but are where the training methodology is actually visible. A patron who sees the creator recognize early lactate accumulation signs at minute 8 of a 20-minute interval, make a decision to reduce power by 5% for the final 12 minutes rather than bail on the session entirely, and explain the reasoning in a post-session note has learned more about how a disciplined athlete manages fatigue than any explainer video can provide.

Third: they accumulate into a coherent training narrative. A single annotated session is interesting. Twelve consecutive weeks of annotated sessions across a full training block — with the periodization rationale at the start, the mid-block adjustments documented in real time, and the post-block assessment at the end — is a complete coaching case study in which the patron was present for every decision. This is the structural retention advantage of the Training Diary tier: the archive grows with each session, making cancellation increasingly costly because the patron would lose access to the complete record of a preparation they have followed from start to finish.

Gravel route documents: what distinguishes functional from generic

Generic route documents are lists of waypoints with elevation profiles and surface type descriptions. These are available from Komoot, Strava, RideWithGPS, and every cycling media outlet that publishes route features. What is not available anywhere else is the operational research layer: the specific information the creator gathered, assessed, and acted on in planning this particular ride.

Surface condition reliability by source is the most underproduced element of gravel route documentation. A creator who rode a specific section of unmaintained forest road in early October and found it rideable notes the source they relied on (a GPS track from a rider who completed the route in September), the discrepancy between that source and the actual condition (the track showed the road as rideable but did not document the mud depth in the shaded sections after three days of rain), and what conditions they would require before attempting the same section again. This is information that does not exist in any route database and that takes twenty minutes to produce but saves future riders hours of uncertainty.

Resupply logistics with operational accuracy is the second underproduced element. Published route descriptions list gas stations and convenience stores with addresses. What they do not document is the store's actual hours on Sunday, whether the small market at kilometer 95 was open when the creator passed at 2:00 PM on a Saturday, or whether the creek crossing the route description mentions as a water source was running in mid-August. A route document that includes the creator's actual resupply stops with the specific information they gathered — the store that was closed despite being listed as open, the water source that ran dry, the town where the single gas station had the best pre-made food selection of the entire route — is a functional planning tool.

Gear selection reasoning in operational detail is the third element. Cycling media route features describe the route; they do not explain why the creator chose 40mm tires over 38mm for this specific surface mix, or why they carried a derailleur hanger spare but not a chain tool, or why they chose not to bring a bivouac despite the route having an optional overnight extension. Each gear decision for a gravel adventure route involves a calculation that is specific to the conditions, the rider's mechanical competence, and the risk tolerance for a specific day. The reasoning behind each decision is where the creator's expertise is actually located, and it is the part that generalizes to other routes the patron might plan.

Apple Tax for cycling audiences

Cycling content has a structural iOS-rate advantage over most YouTube niches because the sport creates desktop behavior through data analysis. A road cyclist who trains with power spends time every week inside TrainingPeaks, GoldenCheetah, WKO5, or Intervals.icu — all of which are primarily desktop applications. The habitual desktop engagement context means that when a cyclist encounters a Patreon subscribe link in a YouTube video description, they are more likely to be on a computer than a phone. This is a structural difference from lifestyle and entertainment niches where mobile is the primary consumption context.

iOS rates by cycling content subtype: road cycling YouTube with training content, 35–50% iOS (analysis-heavy content attracts desktop-dominant viewers); gravel and adventure cycling YouTube, 45–60% iOS (lifestyle-adjacent, more casual mobile viewing mixed with desktop trip planning); cycling coaching content, 30–45% iOS (data analysis is definitionally desktop work); cycling podcasts, 60–70% iOS (listen-while-riding on iPhone, listen-while-commuting); cycling Instagram and Twitter, 70–80% iOS.

Apple Tax exposure by scenario: a road cycling creator at $800/month with 42% iOS faces approximately $100/month ($1,200/year) in Apple fees beginning November 1, 2026. A gravel adventure creator at $500/month with 52% iOS: approximately $78/month ($936/year). A cycling coach at $600/month with 38% iOS: approximately $68/month ($816/year). A cycling podcast with $400/month and 65% iOS: approximately $78/month ($936/year).

The lower iOS rates in training-heavy cycling content mean a smaller proportion of the patron base is billed through Apple — which means a smaller proportion of revenue subject to the November 1 fee change. This is a structural advantage compared to general lifestyle and entertainment creators. It does not eliminate the mitigation step: enable Patreon's web-only billing toggle before October 31, 2026, and direct YouTube description links and any training platform cross-links to the Patreon web URL rather than app links. A cycling patron discovering a Patreon through a TrainingPeaks integration or a Garmin Connect segment is likely on a computer — meeting them with a web URL captures that desktop traffic and keeps it outside Apple's billing path.

Retention mechanics across cycling subtypes

The structural retention question for cycling Patreons is what makes cancellation feel costly. In most content categories, cancellation costs access to future content — which is a low friction barrier because the patron can always re-subscribe later when a new piece of interesting content appears. What makes cycling Patreon retention stronger than average is when the archive accumulates in a way that makes earlier content more valuable over time, not less.

Power file archives work this way. A patron who has twelve months of annotated sessions from a creator who went from 240W FTP to 290W FTP during that period has a longitudinal record of what that physiological development looked like month by month — what the creator changed, what sessions produced the biggest jumps, what training experiments failed. A new subscriber can access the same archive, but the patron who was present for each entry in real time has a relationship with the material that is structurally different from a new subscriber reading the archive retrospectively. This is an unusual retention property in creator content because it means long-tenured patrons get proportionally more value from the same archive than new patrons do.

Route planning archives work similarly. A patron who has followed a gravel adventure creator for eighteen months and has the complete route planning documents for twenty-three different rides has a planning library organized by terrain type, distance, season, and region. The value of the library is not any individual document — it is the corpus. A creator who produces a new route document each month builds a compounding asset that is harder to replicate by a new subscriber who accesses the same documents.

Coaching periodization archives work the same way. A patron who has followed a cycling coach's training block documentation for a full racing season has accompanied the planning and execution of an entire annual periodization cycle. The archive documents how the base phase connected to the build phase, how the build phase connected to the peak event preparation, how the post-season recovery was structured, and what the coach concluded from the season's results about the following year's preparation adjustments. No individual block document contains this — it only exists in the longitudinal record that accumulates with each passing month of patronage.

What not to put behind the paywall

Free content drives discovery; exclusive content drives retention. Cycling creators who misallocate their best material to the paywall before building an audience find the paywall empty of subscribers because there is no free content to drive discovery. The general principle is that content which is best understood by people who already follow the creator closely belongs behind the paywall; content that stands on its own for a new viewer should be free.

For road cycling creators: training philosophy essays, workout structure explainers, and general periodization concepts belong free. These are the content that surfaces the creator's expertise to new viewers and gives potential patrons enough context to understand why the paywall content is valuable. The specific session annotations, the RPE calibration notes, and the longitudinal tracking of adaptation belong behind the paywall — they require the context of following the creator's training to interpret correctly.

For gravel creators: the vlog of the adventure belongs free. The route planning document, the gear selection reasoning, and the honest post-trip assessment belong behind the paywall. The vlog surfaces the creator's storytelling and judgment to new viewers; the planning documents are only useful to patrons who trust the creator's judgment enough to want to replicate or learn from their decisions.

For cycling coaches: training philosophy posts, periodization concept explainers, and general guidance on training structure belong free. Individual athlete case studies, the specific coaching diary entries documenting block-by-block decisions, and the protocols for specific situations (illness during a load block, a plateau in FTP that requires diagnosis) belong behind the paywall — they are the expertise that distinguishes this coach from anyone publishing a training plan, and they require the trust context of a patron relationship to be fully useful.

KeepTier is a self-hosted membership page for creators who want 100% of their tier revenue and zero Apple tax. Plans start at $9/month.