Roen Labs builds a training plan that follows the runner.

Why it exists

Most plans are written once and then followed blindly. Real training doesn't go that way: runs get missed, colds take a week, a calf starts to complain three weeks before the race. A good coach adjusts the next days every time. Most runners don't have one, so the plan is left to absorb it all, and it can't.

Roen is built to make those adjustments: the ones a careful coach makes after a missed week, done every time something changes, with the reason shown.

How it is built

Roen has two parts, and they have different jobs.

• The engine. Builds the plan and re-solves it after every run, from your own history. It runs on fixed rules, not a language model: the same runs and goal always give the same plan, and every change is checked against the same limits on hard running, long runs and weekly growth.
• The coach. Reads what you write, such as a debrief, a missed day or a session of your own, and turns it into a change the engine then checks. If the language model is unavailable, a plain parser reads the sentence instead, so the plan never depends on it.

What we hold to

• Honest numbers. Goal readiness is a model estimate, not a promise, and the plan says when a goal is beyond what the weeks you have can build.
• Restraint. A plan should change what has to change and nothing else. A mild remark in a debrief does not rewrite your week, and a run cut short is not chased.
• Your data stays yours. Strava access is read-only and we never post. You can download your data or delete your account from Settings at any time.
• Not medical advice. Roen protects the days after you report pain, but it is a training tool. For an injury that does not settle, see a professional.

Where it is now

Roen is in private alpha. Invitations go out in small batches while we grow carefully. The site and the app are in English and Italian, and the coach answers in the language you write in.