Kestivo Guides

Training decisions, explained without pretending triathlon is simple.

I started writing these guides because the interesting questions are rarely "what is Zone 2?" They are things like: what do I do after missing Thursday, how much of the plan should survive a chaotic week, and why does every app seem to know only half of my training story?

Published

Start with the questions I kept running into myself.

These are not generic training articles written to fill a content calendar. They come from the same planning problems I am trying to solve in Kestivo.

Coming next

More topics, when there is something useful to say.

I would rather publish three useful guides than thirty versions of '10 tips for better training'. The next ones are already on the list.

Planned guide

How Kestivo builds a training week

A transparent look at Roadmap context, completed training, physiology, weekly generation and athlete review.

Planned guide

Training plan for 70.3

How a middle-distance plan should balance durability, bike strength, run resilience and race-specific preparation.

Planned guide

AI triathlon coach

Where AI adds value, where deterministic rules remain necessary and why athlete control still matters.

Editorial principle

Explain the decision, not just the workout.

A training article should leave you understanding why a choice makes sense. If the entire conclusion is 'listen to your body', it probably did not need 1,500 words.

1. Athlete context before generic recommendations.
2. Race direction before isolated workouts.
3. Real training before assumed compliance.
4. Athlete approval before generated training becomes authoritative.
Private beta

Help test Kestivo with the kind of weeks real athletes actually have.

The private beta starts when the planning loop is stable enough for external athletes, not when the feature list looks longest.

Join the waitlist