Hendrick Hogie
Co-founder
The one who kept getting injured, and got tired enough of it to start building the engine that watches for it.
LinkedInTrailwise started with two runners in Belgium, one injury that would not go away, and years of training history locked inside somebody else's app.
We are Hendrick and Bob. We run trails, and learning from experience, we conceptualized Trailwise, because we each had a problem the running community kept telling us was normal.
Not dramatically. In the ordinary way. A niggle becomes a week off. A week off becomes a rebuild. The rebuild ends in the same niggle, a few months later, and you start again slightly slower than last time.
Every plan Hendrick tried was good at saying what to run and useless at saying when to stop. They all reacted at the same moment: after the injury, when the only remaining option was rest. None of them said anything in the ten days beforehand, when the signs were already there and there was still a week worth saving.
He did not want a plan that noticed injuries. He wanted one that noticed the week before.
Bob had wanted to change watches for years. He never did. Not because the new one was worse, but because switching meant walking away from everything behind it: years of runs, sleep, resting heart rate, the slow honest record of getting fitter and getting older.
The data was his. Getting it out in a form that still meant anything was somebody else's decision. So he stayed on hardware he had stopped enjoying, which is a strange place to end up in a sport that is supposed to be about freedom.
These look like different complaints. They are the same one wearing different clothes.
Both come from a world where your training history belongs to a platform instead of to you. If the record is scattered across apps and broken every time you change brand, nothing can look across years and notice the drift that arrives before an injury. And if nothing can look across years, you are stuck with whichever brand you happened to buy first.
Fix the record and both problems become solvable. That is the entire idea, and it is why the first thing we built was not a coach. It was the place the history lives.
Bring any device, and keep the history when you leave it. Treat staying healthy as the foundation the plan is built on rather than a warning that arrives too late. And show the reasoning, every time, so a change to today's session comes with the inputs behind it instead of a number and a shrug.
None of that is exotic. It is mostly a refusal to do the convenient thing, which is to hold your data hostage and call it an ecosystem.
If you are the runner who keeps rebuilding, or the one still on a watch you have outgrown, you are who this is for.
The one who kept getting injured, and got tired enough of it to start building the engine that watches for it.
LinkedIn
The one who spent years wanting to switch watches and never could, which turned out to be the other half of the same problem.
LinkedInThese optional details help us understand who is joining and what matters most to them.
Thanks for joining the Trailwise private beta waitlist. We’ll share more information about beta access in September.
We’ve sent a confirmation to . Click the link in it to confirm your address and keep your place.
We’ll use your email to manage your beta waitlist registration. See our Privacy Policy.
We’ll share more information in September. If your address was still unconfirmed, we’ve sent a fresh confirmation link.