Define the coaching OS
Map how coaches actually work — clients, plans, nutrition, progress — into a system that scales.
Diby · 2026 - Current
Building a fitness coaching OS.
Product and design shaped in the field with Founding Coaches.
Diby
AI sports coach
I built the research system before the feature backlog.
I designed the Founding Coaches program as a standing field research loop: real sessions, real clients, real feedback deciding what ships next. For an early-stage coaching product, the right method is the field, not the lab. AI connects the high-volume data coaches cannot track manually.
Ownership
Product + design
Roadmap, priorities, and the coaching OS — athlete app and coach platform in one role.
Process
Founding Coaches in the loop
Each feature tested in the field, shipped on feedback, iterated fast.
My edge
AI across high-volume data
Training, nutrition, and progress signals connected — explainable, not a black box.
My contribution
I run research as a live loop — every feature earns its place in the field.
I don't design in a vacuum. I put each feature in front of Founding Coaches, watch it survive real sessions, and iterate on what the field says. AI handles the data volume; coaches stay in control of what matters.
Ship on Founding Coach feedback
Each feature validated in the field, refined fast — not quarterly roadmap guesses.
AI for high-volume data
Connect training, nutrition, and progress signals coaches cannot track manually — explainable and actionable.
Core product loops
Goals, plans, workouts, progress.
A sports coach product only works if the experience keeps users moving. The product model is built around a simple loop: set a goal, receive a plan, execute workouts, and understand progress.
That loop guides prioritization, interaction design, AI prompts, and the way the product explains the next best action.
01Goal-setting
Turn athlete intent into coaching context coaches can act on at scale.
02Planning
Connect goals to training paths that coaches can manage across clients.
03Execution
Guide workouts without cognitive overload — the product carries the complexity.
04Progress
Make change visible and adapt the next step from real training signals.
Web platform screens
Coach operations, workspaces, pricing, and workout libraries.
Diby is not only the athlete app. The web platform gives coaches and teams the operational layer for clients, payments, libraries, workouts, workspaces, and plan management.
Mobile app screens
Native iOS and Android, designed for quick daily actions.
I ship native on both platforms because coaching lives in small daily moments: checking the dashboard, tracking macros, managing workouts, switching workspaces. Fast, familiar, lightweight — that is what keeps athletes coming back every day.
The charts
I measured design against the numbers a coaching business runs on.
I set two commercial tests for the pilot: do coaches stay on the product, and do their clients actually progress across training, nutrition, and activity signals. Retention and client outcomes had to move together — one without the other is not a business.
Impact
In a 156-coach pilot, I moved coach retention from 32% to 79%.
Retention is the commercial engine of a coaching product — coaches who stay are the business. I attacked it directly with a connected view of clients, progress, workouts, nutrition, and daily activity.
Based on coach feedback, client success metrics such as weight loss, training volume, muscle mass, and related progress indicators improved by an average of 62%.
156
Coaches testing the product
32% → 79%
Retention improvement in coach testing
+62%
Average improvement in client success metrics
360°
Client view across training, nutrition, progress, and activity