Kestivo Weekly #2

Your plan isn't set in stone.

A lot changed in a few days: athlete feedback now has a real place in planning, workouts are becoming executable prescriptions, Planned vs Actual is visible, and structured Apple Watch delivery is working end to end.

Sorry, another slightly longer update.

I implemented a lot since Tuesday, and several parts of Kestivo moved from simply working to feeling much more like a real coaching product.

Athlete control

Your plan isn't set in stone.

Last week I mentioned that Kestivo can build a Roadmap around a race or around goals such as improving endurance or general fitness. That is now much more complete. Race-free goals can use a 12, 16 or 24-week Roadmap without Kestivo inventing a race, taper or race week.

More importantly, you no longer have to accept the first proposal. You can give Kestivo feedback on a Roadmap or weekly plan and generate a new version. Kestivo still protects the important constraints. Feedback can influence the coaching proposal, but it cannot casually move your race date or override hard training rules.

Kestivo Review Week screen with athlete feedback saying Saturday's bike is too long and a Regenerate with my feedback button.
The athlete can ask for a different version of the week before accepting it.
Workout prescription

More precise workouts.

The weekly planner also became considerably more specific this week. Kestivo can create structured workouts using actual athlete training data and thresholds, with targets such as Bike power, Run pace, Swim CSS pace and Strength RPE.

Kestivo also calculates the estimated training load itself instead of trusting a number generated by the AI. The result is that a planned workout is becoming a real training prescription rather than simply something like "Bike intervals for 60 minutes".

Kestivo Workout Details showing controlled bike tempo, three by eight minute tempo intervals, 175 to 185 watt target and an execution map.
A structured bike workout now carries a clear Main Set, athlete-specific target, purpose and execution steps.
Closing the loop

What was planned vs what actually happened.

Another important part of the coaching loop moved forward this week. Kestivo can now put the planned workout and completed activity together and show factual differences in things such as duration, distance and training load.

So instead of only knowing that you "completed" a workout, Kestivo starts to understand what actually happened compared with the prescription. That is an important foundation for using real completed training to make better decisions about what should happen next.

Structured workout delivery to Apple Watch is also now working end to end, so supported approved Kestivo workouts can move from the app onto the device used for training.

Kestivo Workout Details showing Add to Apple Watch and Planned vs Actual duration and load comparison.
The same workout detail surface now connects execution and factual post-workout comparison.
Beta readiness

A lot of smaller work happened too.

I also spent quite a bit of time improving onboarding, authentication, TestFlight readiness, training-history import and the Garmin/Intervals connection. Those changes are less exciting to show in a newsletter, but they matter a lot before I put the app in somebody else's hands.

What's next

Garmin delivery and a new Dashboard.

Garmin workout delivery, so an approved Kestivo workout can get from the app onto the device you actually train with. This already works with Apple Watch, as you can see above. Garmin is next on the list.

I am also moving on to a revamped Dashboard, designed to give a much clearer picture of current training state without making the athlete hunt through the app for it.

I'll show both as they take shape.

Alex Founder, Kestivo
AI-first endurance coaching for athletes who still want control.
Private beta

Want the next Kestivo Weekly in your inbox?

Join the private beta waitlist for development updates and future beta access invitations.