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 300W. 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 → 300W 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
300 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 October 18, 2026. Updated here whenever the numbers change in the app.

From Strava

Latest training sessions real, public activities

  • Oct 25

    Low Z2

    31.6 km · 60 min · avg 172W / weighted 174W

    View on Strava →
  • Oct 24

    Three public rides on the same day

    Polkadot Gravel, endurance and a Zwift race · shown without a calculated combined power figure

    Polkadot Gravel · Endurance · Zwift race →
  • Oct 23

    Short race activation

    17.1 km · 30 min · avg 163W / weighted 171W

    View on Strava →
  • Oct 21

    Varied Z2

    14.6 km · 60 min · avg 177W / weighted 180W

    View on Strava →
  • Oct 20

    Threshold with over-unders and short sprints

    29.2 km · 76 min · avg 197W / weighted 227W

    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. The day after threshold was changed to varied Z2

Original plan
October 21 was planned as 25 min of very easy cycling followed by 30 min of core work.
Event
The day followed a threshold session, and the plan was adjusted to provide a more coherent aerobic session.
PBE change
The session was changed to 60 min of varied Z2 followed by 15 min of light core work.
Result
The cycling part was completed as 60 min of varied Z2 — 14.6 km, avg 177W / weighted 180W. Verified on Strava → The core portion cannot be publicly verified.

3. The week was eased after the gravel race

Original plan
Tuesday was planned as a 2 × 20-minute threshold session, with another threshold session on Friday.
Event
The 50 km gravel race on October 4 added a hard race effort immediately before the new training week.
PBE change
After the gravel race, Tuesday’s 2 × 20 min threshold session was changed to 85 min easy Z2, leaving Friday as the week’s only threshold workout.
Result
Completed on October 6 as “Easy Z2 after the gravel race” — 28.3 km, 79 min, avg 175W / weighted 176W. Verified on Strava →

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