I build software from problems I know first-hand.

Paggered is my current bet: a training companion that turns recorded workouts, progress, recovery and nutrition into coaching that shows its working.

Public web app · preparing for controlled acquisition

Paggered dashboard showing recorded evidence, a proposed next step, and explicit user control
A synthetic local fixture · Pags shows the reasoning before anything changes

Paggered

The flagship product

Training advice should start with what you actually did. Paggered connects workouts, progress, recovery and nutrition, then lets Pags propose a next step that points back to the evidence.

Recorded

The advice starts with the athlete's own training history.

Explained

The proposed change comes with its reasoning, not just a number.

Approved

Consequential changes stay with the person doing the training.

The product is public and paid pricing is published. The next work is the unglamorous bit: completing the operational, legal, payment and monitoring checks needed before controlled acquisition.

Other work

The projects that explain the range around the main bet.

Build the thing. Then make it safe to sell.

Paggered is public. I'm treating the path from a good product to a supportable commercial product as part of the build, not a victory lap after it.

Explore Paggered