Every serious athlete generates the data. Nobody connects it into a decision. P247 does.
The average serious endurance athlete (Hyrox, Ironman, marathon, cycling) wears 1.7 devices and uses 3+ apps to track their training, recovery, sleep, and nutrition. Each app reports its own metrics. None of them talk to each other.
The result: an athlete wakes up, sees a green recovery score on Whoop, checks Garmin which says yellow, glances at their sleep score, remembers they did heavy deadlifts yesterday, and has to make a training decision with conflicting, siloed information.
The gap is not data collection. It's data interpretation. Every wearable tells you what happened. None of them tell you what it means for today.
P247 reads your Garmin, Whoop, Apple Health, Strava, and nutrition data overnight and sends you one clear signal each morning: what your body is actually saying, and what today should look like based on it.
Not a dashboard. Not a training plan. Not a replacement for your coach. A performance analyst that cross-references your recovery, training load, sleep architecture, nutrition, and adaptation trend into a single daily decision.
The analogy: Your wearable is the blood test. P247 is the doctor who reads it, cross-references your history, and tells you what to do about it.
| Step | What happens |
|---|---|
| Connect | Athlete links Garmin/Whoop/Apple Health + Strava + optional nutrition app. Takes 2 minutes. |
| Sleep | Overnight, P247 ingests biometric data, cross-references training history, and runs contextual analysis. |
| Wake | Before the athlete's session, they receive a brief: readiness score + reasoning + what today should look like. |
| Learn | Over weeks, P247 builds a personalised model of the athlete's recovery patterns, stress responses, and adaptation rate. |
| Segment | Size | Why P247 |
|---|---|---|
| Hyrox athletes | 300K+ registered globally, fastest-growing fitness race format | Mixed-modality training (run + functional) breaks every existing load model. No wearable handles it. |
| Ironman / triathlon | 2M+ active globally | Swim/bike/run load differently. Recovery is the competitive edge, not more training. |
| Marathon runners | 6.4M finishers/yr (US alone) | Overtraining and taper errors cost race results. HRV trend + load context prevents both. |
| Serious gym + endurance | 12M+ dual-training athletes | Strength training fatigue is invisible to every wearable. P247 fills the gap. |
Initial focus: Australia, UK, US, Canada. These athletes are data-literate, already spend on wearables and apps, and compete in events with clear periodisation windows (which drive subscription retention).
Serviceable Obtainable Market (SOM): 50,000 athletes in Year 1 at $15/month = $9M ARR potential. Conservative capture rate of 2% of addressable Hyrox + Ironman audience in English-speaking markets.
Before writing a single line of product code, we ran a structured community validation campaign across Reddit (9 subreddits) and Facebook groups (6 groups) to test whether the problem is real, urgent, and worth paying to solve.
A response qualified only if the athlete described a specific moment where wearable data failed to drive a training decision. Not "yeah same" agreement. Specific, personal frustration with context.
| Pain theme | # signals | Example |
|---|---|---|
| Score ≠ how I feel | 8 | "Green recovery, legs destroyed. Ignored the score." |
| Data as noise, not signal | 6 | "Mostly I just get the noise but don't do anything about it." |
| Abandoned device entirely | 4 | "Threw the toys away, listen to my body." |
| Built own system (spreadsheet/manual) | 3 | "I manually correlate InBody + Strava + Apple HRV in a Google Sheet every Sunday." |
| Overhead too high to sustain | 2 | "Too much work for me to do year round" (Ironman athlete) |
Key insight: One Reddit user (r/whoop) described building exactly what P247 does — "getting generic sensors to upload data to the cloud and get an LLM to crunch it based on my requirements." The market isn't just ready. It's trying to build this itself.
| Player | What they do | What they miss |
|---|---|---|
| Whoop ($288/yr) | Recovery + strain scoring via HRV/RHR | No training context, no nutrition, no strength load, generic rolling baseline, opaque algorithm |
| Garmin (free w/ device) | Training readiness, body battery, load focus | Doesn't factor gym work, no nutrition, can't distinguish fatigue types, no multi-device synthesis |
| Oura ($72/yr) | Sleep + readiness scoring | No training load integration, no sport-specific context, passive reporting only |
| TrainingPeaks ($120/yr) | CTL/ATL/TSB load model | No recovery data, no sleep, no nutrition, TSS conflates all load types, no life context |
| Athlytic ($36/yr) | Apple Health visualisation | Basic recovery scoring (just HRV+RHR), no synthesis, no coaching, no periodisation |
| athletedata.health | AI coach via Telegram | Early stage competitor, limited device integration, unproven retention |
P247's positioning: We don't compete with wearables. We sit on top of all of them. The more devices an athlete owns, the more valuable P247 becomes. Our competitors are each other's blind spots.
Apple could build coaching into Health (iOS 20+). However: Apple's strength is hardware + ecosystem lock-in, not personalised AI coaching for niche sports. Apple will optimise for the median user. P247 optimises for the serious athlete. Apple entering validates the market and drives wearable adoption (which grows our addressable base). Our 12-18 month window is real, but our niche positioning survives even if Apple ships a generic coaching layer.
| Tier | Price | Includes |
|---|---|---|
| Core | $15/month (or $144/year) | Daily morning brief, multi-device sync, readiness scoring with reasoning, adaptation tracking, basic periodisation |
| Pro | $25/month (or $240/year) | Everything in Core + event-specific periodisation, nutrition integration, advanced sleep analysis, exportable reports, InBody integration |
| Team (future) | $20/athlete/month | Coach dashboard, team-wide readiness view, group periodisation for training squads |
| Milestone | Subscribers | MRR | ARR |
|---|---|---|---|
| Month 6 (beta) | 200 | $3,600 | $43K |
| Month 12 | 1,500 | $27,000 | $324K |
| Month 24 | 8,000 | $144,000 | $1.7M |
| Month 36 | 25,000 | $450,000 | $5.4M |
| Channel | Target CAC | Notes |
|---|---|---|
| Organic content (SEO + social) | $0-5 | Primary channel. Content is the product's top-of-funnel. |
| Community referral | $8-12 | Athletes tell training partners. Event-driven virality. |
| Paid social (Phase 3) | $25-40 | Targeted: Whoop/Garmin owners + Hyrox/Ironman interest. |
| Coach partnerships | $15-20 | Coach recommends to 10-50 athletes. Low CAC, high LTV. |
Target LTV:CAC ratio: 8:1+ via organic content channels. The blog and community engagement are not marketing activities. They ARE the growth engine.
Why this founder for this problem: The intersection of professional observability engineering (making sense of complex multi-source data) and serious athlete training (living the wearable frustration daily) is rare. Myles doesn't just understand the market. He is the market.
| Role | When | Why |
|---|---|---|
| Full-stack engineer | Month 1 | Build integrations (Garmin/Whoop/Apple Health APIs) and morning brief delivery pipeline |
| Sports science advisor | Month 2 | Validate interpretation framework, ensure recommendations are evidence-based |
| Growth marketer | Month 4 | Scale content engine, manage community, optimise conversion |
| Use of funds | Allocation | Purpose |
|---|---|---|
| Engineering | $120K (48%) | Full-stack hire + API integrations + morning brief engine |
| Product validation | $40K (16%) | 50-athlete concierge beta, sports science advisory, interpretation framework validation |
| Growth | $50K (20%) | Content production, SEO infrastructure, community management, event activations |
| Operations | $40K (16%) | Infrastructure (hosting, APIs, LLM costs), legal, accounting |
P247 is building the analyst layer that serious athletes are already trying to build themselves in spreadsheets. The market is validated. The timing is right. The founder lives the problem every day.
p247.io