Inside Flow Momentum: Performance Health for Athletes and Coaches

Endurance athletes already have plenty of data.

The harder problem is continuity: knowing which record to trust, how today's recovery fits the previous month, and what a coach or athlete should do next without pretending that one score contains the whole answer.

That is the problem Flow Momentum is being built to address.

One product, two clear paths

Flow Momentum now has separate journeys for athletes and human coaches.

The athlete experience is organised around a longitudinal record, sport-specific analysis and private coaching conversations. The coach experience is organised around a roster, one selected athlete at a time, reports, notes and an athlete-locked assistant.

Both use the same underlying principle: source records, calculated indicators and AI-supported interpretation should remain distinguishable.

The athlete record

An athlete may arrive with an automatic connection, a manually uploaded training file or a mixture of sources. Flow Momentum is designed to organise supported records into a persistent athlete history.

That matters because a six-month event build cannot be understood from a seven-day snapshot.

The record can support:

• activity history and activity-level detail;
• training load and progression;
• recovery and health-adjacent wearable context;
• planned versus completed work;
• sport-specific Performance Health dashboards;
• questions to the Performance or Nutrition Coach.

Availability depends on the connected source and file quality. Missing values should remain missing rather than being guessed.

Cycling, running and triathlon are not the same dashboard

A cyclist may care about power, FTP context, elevation and ride demands. A runner needs pace, durability, long-run balance and volume progression. A triathlete must understand discipline balance and combined fatigue across swim, bike and run.

Flow Momentum therefore adapts the analysis to the athlete's selected sport focus.

The aim is not to produce more charts. It is to make the chart answer a relevant coaching question.

The coach workspace

The Coach Founding Pilot adds a professional workspace for managing several athletes.

Synthetic test data. Pilot interface may evolve.

An approved coach can create a managed athlete, invite an athlete to claim their record, upload authorised training files and open an athlete-specific cockpit.

Synthetic test data. Empty states are intentionally shown rather than populated with invented metrics.

Inside that workspace, the coach can inspect available data, keep private notes, prepare reports and share selected outputs with the athlete.

The Coach Assistant

Dashboards are useful until the coach has a question the dashboard did not anticipate.

The Coach Assistant pilot is designed for that gap. The coach selects an athlete first, then asks questions against the authorised athlete record, confirmed athlete-specific context and the Performance Coach knowledge base.

Examples include:

• "What explains the change in this athlete's load over the last four weeks?"
• "Which evidence supports an easier session today?"
• "What is missing before I update the threshold?"
• "Draft a weekly review that distinguishes facts from recommendations."

Context that may become persistent learning requires explicit confirmation. The assistant should not silently turn every chat statement into athlete memory.

Knowledge that remains useful

The product separates three kinds of knowledge that are often blurred together in AI products:

• maintained specialist knowledge bases for Performance, Nutrition, Communications and Team coaching;
• the athlete's own longitudinal data record;
• confirmed athlete-specific memory, including goals, preferences, constraints and useful coaching learnings.

That distinction matters. A scientific source is not an athlete fact. A wearable value is not automatically a recommendation. A statement in a chat should not silently become permanent memory.

Flow Momentum's individual learning layer is designed as a controlled, living coaching wiki. Relevant context can persist when it is confirmed, remain scoped to the selected athlete and be reviewed or corrected later. It is not presented as a shared AI model retraining itself on every conversation.

Privacy is part of the product shape

A human coach does not automatically receive the athlete's entire digital life.

Performance and nutrition context can be shared within the permissions of the relationship. Private Communications and Team coaching remain separate. Relationships can be revoked, and coach access should be auditable.

This is not an extra compliance screen. It is part of building trust between athlete, coach and system.

What Performance Health adds

Performance Health is the strategic frame around the product. It connects training, recovery, nutrition, resilience and human judgement without turning Flow Momentum into a medical service.

The product supports performance and wellness decisions. It does not diagnose illness or injury, prescribe treatment or replace a clinician.

The founding phase

Athlete and coach access is currently application-based. Coach accounts are manually approved because the workspace handles other people's training data and is still being tested with professional users.

The most useful founding members are not people looking for a perfect finished product. They are athletes and coaches who can judge whether the system makes the right evidence visible and whether the workflow improves a real decision.

Closing thought

The future of endurance coaching is unlikely to be a choice between software and humans.

It will be built by systems that help athletes understand themselves and help coaches spend more of their time on judgement, communication and trust.