We kept asking the same question.
Why do training plans still ignore the data we already have?
Why we started
We're a group of students who got curious about something simple: why do most training apps build your week from a short onboarding quiz, and then never look at your actual data again?
Your wearable knows your HRV dropped. Your phone knows you slept four hours. Your watch knows yesterday's run hit you harder than it should have. And yet, the next morning, the app still says "10K at threshold," like nothing happened.
We started digging into the market and kept finding the same gap. Static plans on one side, expensive human coaches on the other, and almost nothing in between that actually uses the data sitting on people's wrists every day. stoke.run is our attempt to close that gap.
What we believe
We think a plan that ignores how you slept, recovered, or felt isn't really a plan, it's a wishlist. Training should adapt to you, not the other way around. And if we change your workout, you deserve to know exactly why, in plain language, without black-box algorithms or "just trust us." We're also convinced that the runners in the middle, the ones with full-time jobs, families, and a marathon goal, deserve better tools than the templates they currently get. Beginners have apps, pros have coaches, and everyone in between gets a generic PDF.
