Berlin '26 · cohort 03 · invite-only

Know you’re race ready — don’t just hope.

You’re putting in the miles. But are you actually on track for race day? Azimuth reads your runs, sleep, and recovery every morning — then gives you a clear signal, not a guess.

No credit card·Cohort opens March '26
AI-narrated06:14 today
Race readiness003 / 016
81/ 100
Endurance86
Speed72
Recovery84
On track · phase 2Berlin '26 · 146 d
Readiness
81/100
Goal pace
4:55/km
Days to race
146
01 — The real problem

Your data is everywhere. Your readiness is nowhere.

001 / 005

Strava tracks what you ran. Garmin tracks how you slept. But nothing tells you what it adds up to — or whether you’re actually on track for race day. That’s the gap Azimuth closes.

Race readiness16 weeks · scale 0–100
On trackSub 3:30
406080100Today · 81W −16Block 2Race
02 — What you get

Everything a coach sees — synthesised every morning.

Not more data to scroll through. Five clear readings from your actual training, waiting for you at 6am.

002 / 005
01

Race readiness, in one number.

A 0–100 score from fitness, fatigue, and adherence. Measured — never narrated by the model.

81 / 100
Strong · trending up
02

The plan bends. Your goal doesn't.

3am wake-up with the baby? Business travel? The block target holds. The path to it adjusts. You get the week you can actually run.

−9 km mid-week
Recovery weighted
03

A fitness profile, not a vibe.

Threshold pace, easy HR, stride, zone time. Updated every session, never inflated.

vTHR 3:42 /km
28-day rolling
04

A coach's note, every Sunday.

One paragraph on what worked, what slipped, and the week ahead. Generated only when there's enough signal.

AI-written
05

Strava in. Quiet sessions out.

Sync once. Every run flows into the plan, gets categorised, feeds the readings — and the model.

Strava connected·Auto-categorisation·iOS PWA
How this got built & what’s next →
03 — Inside the dashboard

You deserve to know why your plan changed.

003 / 005
Plan delta · narrated

Three bad nights of sleep shouldn't be a mystery.

The narrated card explains the change. The measured card proves it. You’re not left wondering why your threshold session moved — you can see exactly what changed and why.

Plan adjustment · 2d ago

HRV trended low for three days after travel. I rebalanced this week's threshold into easy 12k and held the goal pace untouched.

−9 kmBlock target intact
Plan · measured

Sixteen rows. The current week, anchored.

Past weeks fade. Tap a row to open the session. The long-run column never lies — it's how race day will feel, mostly.

Weekly plan · block 2W 13 / 16
W 11 · Aug 04Threshold builds + long 28k62 km
W 12 · Aug 11Cutback · easy mileage48 km
W 13 · Aug 18MP segments · mid-long70 km
W 14 · Aug 25Hill repeats · 32k long76 km
W 15 · Sep 01Race-pace simulation82 km
Fitness · measured

The numbers behind the paragraph.

Threshold pace, easy HR, zone time, stride. Each updates from your runs — not a self-rated slider.

Fitness profile · 28 daysvTHR 3:42
Z1
Z2
Z3
Z4
Z5
VO₂ proxy58.4
Avg HR · easy142 bpm
Stride1.41 m
04 — How it works

Three steps to running with clarity.

004 / 005
01

Connect Strava

Your runs sync automatically, reconciled against the plan in real time. No manual entry.

02

Read your score

Every morning, 13 evidence-based components produce a 0–100 readiness number with a plain-English explanation.

03

Race knowing

Not hoping. The science has been running alongside you since the first session.

What powers it
01

Numbers from code. Words from a model.

Every score is produced by deterministic code — it doesn't hallucinate, it doesn't round up. The model reads those numbers and explains them. It's a writer, not a decision-maker.

02

Missing data drops out. It doesn't score zero.

You can't score a tune-up race you haven't run. So Azimuth doesn't pretend you scored zero — components with no data drop out of both sides of the calculation. Your score is always paired with an evidence completeness percentage.

03

Two scores answer two questions.

Fitness Level moves fast — it answers “how is training going right now?” Race Readiness moves slowly — it answers “how prepared am I for race day?” Showing both is more honest than blending them into a single number.

Read the full breakdown
05 — Honest answers

What runners actually want to know.

005 / 005
01

Is this a coach replacement?

No. It's the read between the sessions a coach prescribes, or the structure for a self-coached runner. Many beta users use Azimuth alongside their coach as a daily check-in.

02

Where is the AI in the loop?

It writes three things — a daily read, a weekly review, and a plan-adjustment note. It never sets your readiness score, never sets your goal pace, and never decides your plan. It narrates.

03

How does the plan adapt?

It looks at the last seven days — sleep, HRV trend, completed sessions, perceived effort, weather — and rebalances the next three. The block target doesn't move; the path to it does.

04

Is my data used to train models?

No. Your training data stays yours. Inference happens on the seven-day rolling window required for the writeup; raw runs never leave Azimuth.

05

What if I just follow a standard plan?

You can — millions of runners do. But a standard plan doesn't know you've had three nights of poor sleep. It doesn't know your HRV has been trending down for ten days. It doesn't know the threshold session you planned is the one that tips you toward injury. Azimuth knows — and adjusts before the damage is done.

06

What does it cost?

Nothing during the beta. After Berlin '26 we'll publish a fair, single-tier subscription. Beta runners get founding-member pricing, locked.

05 — Cohort 03
005 / 005

Imagine crossing that start line knowing you’re ready.

Not hoping. Knowing. Drop your email — the next cohort opens March '26. Your first week: a readiness baseline, a goal-pace conversation, and a plan built around your actual life.

No spam. One email when your slot opens.