50K · 50 mile · 100K · 100 mile · Multi-day

Ultra plans that are compiled, not copied.

UltraCoach builds your macrocycle backwards from race day using an ultra-specific blueprint engine, fits it to the days you actually have, reads your runs straight from Strava, and reshapes the weeks ahead when training doesn't go to plan.

Free to start · Strava-connected · Currently in invite-only beta

Build phase · week 9 of 20

Specificity: climbing volume

8 h 15

  • MonRecovery run40 min · easy
  • TueHill repeats70 min · 620 m up
  • WedEasy + strides50 min
  • ThuHeavy strength45 min · lower body
  • FriRestBlocked — travel
  • SatLong run3 h 20 · 900 m up
  • SunBack-to-back1 h 50 · tired legs

Friday is blocked in your availability, so the engine moved the second quality day rather than dropping it.

Distance families

Everything from your first 50K to a hundred-mile finish — and a different plan architecture for each.

Each family carries its own blueprints, tiered by where you are: developing, established, or chasing a performance. The engine picks the one that matches your race and your history.

50K

The step past the marathon

Time on feet over pace, first real vertical exposure, and a long run that stops being the whole plan.

Developing / Established / Performance

50 mile

Where fuelling becomes training

Longer aerobic blocks, deliberate downhill loading, and a fuelling protocol rehearsed in training rather than guessed on race day.

Developing / Established / Performance

100K

Back-to-backs and night running

Weekend pairs that build durability without a single unsustainable long day, plus terrain-matched climbing volume.

Developing / Established / Performance

100 mile

The long build

A multi-block macrocycle with peak-exposure rules, a staged taper, and specificity that tracks your actual course profile.

Developing / Established / Performance

How a plan is built

Four inputs, one compile, a calendar you can actually run.

  1. 01

    Your race, described properly

    Distance, date, elevation gain and loss, terrain, altitude, likely heat, cut-offs. The demand vector of the race — not just a mileage target.

  2. 02

    Your real capacity and your real week

    Recent training, longest recent week, the days you can train, how many blocks each day holds, and the days that are simply blocked. Declared, not assumed.

  3. 03

    The macrocycle compiles backwards

    The engine picks a blueprint from your distance family and experience tier, then compiles back from race day: taper, peak, specificity, build, base — each phase inside its own envelope.

  4. 04

    Materialised into your calendar

    Every week becomes real sessions on real dates, solved against your availability. Not a PDF you have to translate into your life.

The engine, in the open

Most plans are a spreadsheet with your name on it. This one has rules it can't break.

Phase envelopes, not a mileage curve

Each phase has bounds on volume, intensity distribution and long-run share. The plan can't quietly drift into a training block it was never meant to be.

Peak-exposure rules

Your biggest weeks and longest days are governed by exposure rules for the distance you're racing — not by whatever number looks impressive.

A scheduler that respects your week

Sessions are solved against your available days and blocks, with separation rules between hard days, strength and long runs. A short week gets trimmed sensibly, not broken.

A fixed priority order

Safety, then feasibility, then continuity from your current training, then the priority stimulus, then specificity — and only then session-level optimisation.

Vertical treated as a real load

Climbing and descending are planned and tracked as their own stimulus, because a flat 100K and an alpine 100K are not the same race.

Versioned and reproducible

Plans are compiled by a versioned engine against a pinned catalogue, so the same inputs give the same plan and every change is deliberate.

When training doesn't cooperate

Ultra training isn't linear. Your plan shouldn't pretend it is.

A wedding, a chest infection, a week where everything felt heavy. The plan notices, proposes a change in plain English, and waits for you to say yes.

You tell it how it actually went

Log the session as done, modified or missed — with duration, RPE, how you felt 24 hours later, and any pain or illness flags.

It reads the pattern, not the incident

One easy run cut short is noise. Three overshoot weeks, a run of high RPE, or a niggle that keeps recurring is signal — and the engine treats them differently.

It only rewrites what's ahead

Proposals reshape the weeks in front of you and leave your completed training alone. You see what changes and why, in plain English, and you approve it.

Strava, automatic

You run. It logs itself.

Connect Strava once and new activities arrive on their own. Each run is matched to the session it belongs to, with distance, duration and elevation pre-filled — you just confirm and add how it felt. You can import your history at sign-up too, so your starting capacity is based on what you've really been running rather than a number you guessed.

Every session shows planned against actual, so a 4.5 mile run never shows up as the 2 miles someone once planned for you.

The coach

A coach that has already read your plan.

Chat the way you already do with a general AI — except this one can see your macrocycle, your completed sessions, your Strava, your check-ins and your race brief. Ask why Thursday looks like that, what to do about a tight calf, or how to fuel a 14 hour day.

It answers from a pinned, versioned ultra research corpus rather than free-associating, and it tells you when something needs a physio instead of a training tweak.

Where this comes from

UltraCoach is an independent synthesis of peer-reviewed exercise science, established endurance-training principles and published coaching literature. The corpus is pinned and versioned, so no recommendation drifts away from what it was built on.

No endorsements are claimed. Read the full methodology and the training-priority hierarchy.

Ready when you are

Race longer. Train smarter.

Bring your target race, your recent training and your real week. Get a plan built for the distance you actually run.