Performance By Eliving
DanskStart free

Founder case · updated as it progresses

I'm building the app. I'm also training with it.

My name is Ole Engholm Rask Møller, and I'm the founder of Performance By Eliving. I use my own app to raise my FTP towards 320W. Here are my real numbers, my latest Strava sessions and concrete examples of how my own plan has changed along the way — including what worked and what can only be partially documented.

Goal: FTP 285W → 320W 8–10 h/week Polarized / sweet-spot hybrid

Right now

Current key numbers

These are my current, real numbers from my own profile in the app — not the block's starting figures.

285 W
Current FTP
320 W
Target FTP
74 kg
Body weight
3.85
W/kg

Source: my own production profile in the Performance app (coach setup + profile), last updated September 27, 2026. Updated here whenever the numbers change in the app.

From Strava

Latest training sessions real, public activities

  • Oct 4

    50 km gravel race · RAAW

    50.5 km · 107 min · avg 188W / weighted 206W

    View on Strava →
  • Oct 3

    Easy activation before gravel race · PBE Build 05

    30.2 km · 68 min · avg 142W / weighted 156W

    View on Strava →
  • Oct 2

    Easy Z2 without strength · PBE Build 05

    35.6 km · 75 min · avg 168W / weighted 175W

    View on Strava →
  • Sep 29

    VO2max key session: 5 x 4 min · PBE Build 05

    37.8 km · 89 min · avg 189W / weighted 226W

    View on Strava →
  • Sep 27

    Easy aerobic endurance + light strength · PBE Recovery 04

    38.9 km · 95 min · avg 205W / weighted 221W

    View on Strava →

Real plan history

Documented plan changes

Three concrete examples from my own coach chat and weekly reviews — shown as original plan → event → PBE change → result. Where the result can't be directly verified, we say so honestly.

1. A VO2max session replaced an extra threshold session ahead of a gravel race

Original plan
The week of Sep 21–27 had two threshold sessions (Tuesday and Thursday) as the quality days.
Event
I asked my own coach: "Wouldn't it make sense to add some VO2max before the gravel race?"
PBE change
The coach replaced the second threshold session with a controlled VO2max session (4 × 4 min at roughly 110–115% FTP), placed on Thursday after further discussion.
Result
Completed on September 24 as "Controlled VO2max: 4 x 4 min" — 27.3 km, 54 min, avg 194W / weighted 223W. Verified on Strava →

2. Monday strength removed to avoid two strength sessions in a row

Original plan
Monday, September 14 was set as a strength session in the approved weekly plan.
Event
I pointed out I had already done strength the day before (Sunday): "I did strength training today, why is Monday also a strength day?"
PBE change
The coach removed Monday's strength: "Monday is now cycling-only so you are not stacking strength sessions… Light maintenance strength moves to Sunday."
Result
Monday, September 14 became an easy recovery ride (61 min) instead of strength, confirmed in the activity log.

3. A scheduled FTP retest replaced with a normal week

Original plan
The weekly review on September 20 proposed a 60-minute FTP test on Wednesday, following the normal 4-week retest protocol.
Event
I wrote: "I can't do an FTP test next week, so build a normal training week instead."
PBE change
The test was removed and replaced with a normal threshold key session on Tuesday, based on my then-current FTP of 285W.
Result
Not fully documented The week was completed without interruption (see the activity log for the period), but the exact wattage execution of the replacement session can't be unambiguously documented from this data extract alone.

The product

What the app looks like

A few examples of the product surfaces I use every week to plan, complete and adjust training.

Overview of the Performance app screens: dashboard, training plan, workout detail, coach, history, setup, profile and administration
The full product flow — from today's session to long-term progression.
Example Performance dashboard with today's session, recovery score and weekly overview
Example dashboard: today's adjusted session, recovery and weekly progress.

In the open

Honest lessons so far

This is not only a sunshine story. Some things have taken more than one attempt.

  • When I asked for a plain list of "strength sessions" in a weekly summary, it was technically correct but gave a misleading picture of the whole week's load — I had to push back before the coach corrected it.
  • Keeping weekday sessions under 75 minutes is a hard but necessary constraint as a founder — it has forced the plan to be more efficient per minute instead of just adding more time.
  • Strength and cycling intensity have to be planned together, not separately — a strength day placed wrong can steal freshness from the next day's key session, even if both days look fine in isolation.
  • Data only becomes useful when it leads to one concrete decision for today — not another number on a screen.

Performance By Eliving

Want to try the same kind of plan?

Start free, set your goal and available time, and get a plan that adapts to your week — not the other way around.

Start freeSign in