runwritten Sign in

A coach who knows the whole runner.

Runwritten writes a plan for your season from your whole history, your races and your real week, and rewrites it with you as training and life happen.

Join the waitlist Private beta, invite only. Invitations come from this list.
Today, on a synthetic runner. Planned is outlined, recorded is filled. Below: the season this week belongs to.

A season, not a template

One calendar, several races, each with a job.

Runwritten starts from everything you've done, not the last four weeks: old peaks, race results, how you absorbed earlier blocks. It writes the current block in detail and the rest of the season in outline, and names the point where the plan is revisited with evidence.

Synthetic runnerabout 35 miles a week · club track Tuesday · club long run Saturday

The Thursday session, weeks 5–10

Tuesday is club track, counted as the second quality day. Sessions change shape, not just size.

  1. 55 × 5′ sub-threshold, 90″ jog
  2. 6Benchmark 5K on Saturday · Thursday: 6 × 1′ hills, easy
  3. 73 × 8′ sub-threshold, 2′ jog · paces rewritten from the 5K
  4. 8Down week · Moneghetti fartlek, 20′
  5. 94 × 6′ at threshold, 90″ jog
  6. 103 × 10′ sub-threshold

The checkpoint

"We'll decide the half-marathon goal time around weeks 8–10 of the build, from your workouts." The December 5K sets the winter's paces; nothing is promised before the evidence exists.

Synthetic season. Recorded weeks are filled, planned weeks outlined; lower bars are down weeks; the pins are races with their roles.
Guidelines, not rules.
Runwritten's training logic is a set of defaults with stated reasons. The Coach applies them to your history; when your evidence justifies a departure, it explains why and you decide.
Intensity in your language.
Effort, pace ranges or heart rate: concrete targets if you run everything in one gear, effort first if you stare at your watch.

It changes with you

Training and life rewrite the plan. You approve each change.

Nothing moves silently. The Coach proposes, gives its reason, and you keep the plan or apply it, once, everywhere: Today, the plan and your calendar.

Coach proposal · You're travelling Wed–Fri in week 10

Tempo moves to Tuesday and replaces club track this week. Saturday's long run stays. Friday's easy run is dropped, not squeezed in.

Leave my planMake this change
A Coach with real judgement.
It weighs advice from friends and other apps against your context, changes its view when you bring real knowledge, and checks facts such as race dates before it plans around them.
How it works.
The Coach is a language model with your whole file in front of it, and every proposal is checked against the guidelines before you see it.

Start from where you are

Bring the plan you already have, or the history behind it.

Club runners, self-coached runners and people coming back with limited time: one system, the same care. Three ways in, all open at once.

Bring your plan
The plan you or your coach wrote, as a spreadsheet, CSV, PDF or chat. Kept whole, never condensed, with a review that shows what was understood and what wasn't.
Bring your history
Your races, your past peaks and your watch data. The Coach writes the season around them, in conversation, asking only what would change the plan.
Start from your week
Nothing but the days you can run and the time you have. A credible start that fits, and a calm answer to a missed day.

How the private beta works

Small groups, six weeks each, the founders reading along.

Invitations
Go out in small groups, chosen from the waitlist. The optional questions after you join are how we choose.
Six weeks
Each group trains on Runwritten with a real plan and a real week, on the watch they already own.
Reading along
We read every proposal you accept or decline, and the product changes because of it.

Private beta · invite only

Join the waitlist

Invitations are chosen from this list. Your email is all it takes; a few optional questions after that help us pick the first group and decide which watches and plan sources come first.