Kestivo is moving from separate planning features toward one coherent flow, from athlete context to Roadmap, weekly training and completed activity evidence.
Starting with the athlete, not a generic plan.
Before Kestivo creates training, it needs to understand the athlete: sports, race goals, training experience, weekly availability, preferred training days, thresholds and zones, equipment, and recent training history.
The important part is that this is not just profile information sitting somewhere in Settings. It becomes context for the planning system.
From your goal to your Roadmap.
Kestivo does not jump directly from "I have a race" to filling a calendar with workouts. It first creates a Roadmap toward the main goal.
The Roadmap divides the available time into training phases and makes the current phase visible. If you do not have a race planned, that is fine too. You can choose a goal such as improving endurance or general fitness, and Kestivo will build training around that instead.
Then Kestivo builds the training week.
The next level is much more practical. Kestivo combines the Roadmap with availability, recent completed training, training load, thresholds and other athlete context to propose the training week.
You can review the proposed week before it becomes your actual training calendar. Athlete control is an important part of Kestivo. The AI proposes the training, Kestivo validates it, and you decide whether to use it.
And then there is Garmin.
Direct Garmin integration would eventually be the ideal route, but the developer-program situation makes that timing uncertain. Rather than make the beta depend on that timeline, I have been working with Intervals.icu as a bridge.
Completed Garmin activities can already reach Kestivo through the bridge, including the detailed activity data needed for training analysis. I have also verified that Intervals.icu can deliver structured workouts to Garmin devices. The remaining step is connecting Kestivo's planned workouts to that outbound route.
For the first beta, Garmin athletes will therefore probably need a free Intervals.icu account. A short setup guide will come before beta access begins.
The goal is the complete coaching loop.
The objective is not simply to get Kestivo into TestFlight as quickly as possible. I want the first beta to contain the complete loop:
Several pieces already work. The current job is connecting and stabilising them so the first external beta feels like one product rather than a collection of unfinished features.
AI-first endurance coaching for athletes who still want control.
Want the next Kestivo Weekly in your inbox?
Join the private beta waitlist for development updates and future beta access invitations.