Who built it

I'm Ryan Lee. I've designed and built software for twenty years, and I race hybrid events: 1:30:06 at my last one in Washington, DC, tenth of 171 in my age-group race. Ravns is the coach I wanted and couldn't buy.

Why it exists

My watch knew I had slept badly. My plan didn't care. Every app I tried either handed me a twelve-week PDF that never changed, or a recovery score with no idea what I was training for. Nothing read both and told me what to do on a Tuesday.

So Ravns starts with the morning: what your night and your last week actually did to you, then what today's session should be because of it. Some days that means back off. Some days it means you are fine, stop negotiating, go.

How the coaching is decided

The plan is not a chatbot improvising. The periodization, the readiness score, the load maths and the race build are ordinary code with rules written down and tested, the same way I'd build anything that people depend on. The AI coach explains the decision, asks you questions, and handles the messy parts like reading a plate of food. It does not get to invent your training.

That split is deliberate, and it is the part I'd most like coaches to argue with. If you coach hybrid athletes and the programming is wrong somewhere, tell me and I'll fix it or explain why it's built that way.

Who you're dealing with

One person. No investors, no growth team, no ads. I write every line, answer every support email, and use it myself every morning. That's a weakness on paper and the reason the app is opinionated rather than a pile of settings.

It also means you can reach me. ryan@lastyeti.com goes to me, and I answer.