Hi everyone,
I’ve been working on a project called DunMove – a browser-based tool to generate structured cycling training plans that are based on weekly time budget, goal events, and desired training rhythm.
I built it because I was never quite happy with existing platforms (too rigid, too black-boxy, too app-centric).
So I wrote my own system to:
- plan backwards from the goal event
- distribute weekly load based on training phases
- match workouts by duration, target TSS, and workout type
- keep things transparent and editable
Key Features:
- FTP-based planning → all sessions use %FTP structure
- Load progression toward main event (including deload weeks)
- Session types adapt to training phase (base, build, peak, taper)
- Structured export: .zwo, .erg, and ICS calendar feed (fully works with Intervals.icu)
- Supports 6 languages: EN, DE, FR, ES, IT, NL
- Workout database: >5,000 structured entries, categorized by intensity, style, time & TSS
- Test user included → you can walk through the full process and preview a complete plan
- Designed for powermeter users – not HR or estimated effort
- Browser-based, no app or subscription required
Here’s a sample use case:
You want to train 10–12h per week for an event in 16 weeks.
You set your training days, pick a peak event, and DunMove generates a progressive plan that builds load intelligently and matches your available time each day. You can then export sessions or sync them via ICS to Intervals.icu.
I’d really appreciate feedback from anyone here who works with structured plans, TSS logic, or just wants to see something a bit different from the big players.
If you have suggestions, feature wishes or just critical thoughts – please hit me with them!
Thanks,
Sven

