A
Runner Injury Prevention Coaching Lab
3.70
Derivation Chain
Step 1
Marathon running boom
→
Step 2
Surge in running crew and race participation
→
Step 3
Demand for injury prevention among amateur runners
Problem
In 2026, marathon events are held weekly in Korea, and the running population has surged, but over 70% of amateur runners in their 30s-50s train without professional coaching, relying only on YouTube and community information, and suffer knee, ankle, and Achilles tendon injuries. A single injury costs an average of 500,000-1,500,000 KRW (approx. $375-$1,125) for orthopedic treatment and rehabilitation, with a recovery period of 4-12 weeks, making race entry fees and equipment costs sunk costs.
Solution
A mobile web service that automatically calculates overtraining risk when you input weekly training volume (distance, pace, elevation), and pushes daily personalized stretching and strengthening routines based on body type, running experience, and past injury history. It combines a race D-day reverse periodization plan with an injury symptom self-check questionnaire, and when risk signals are detected, it provides one-stop connection to nearby sports medicine clinics for appointments.
NUMR-V Scores
NUMR-V Scoring System
| N Novelty | 1-5 | How uncommon the service is in market context. |
| U Urgency | 1-5 | How urgently users need this problem solved now. |
| M Market | 1-5 | Market size and growth potential from proxy indicators. |
| R Realizability | 1-5 | Buildability for a small team with realistic constraints. |
| V Validation | 1-5 | Validation signal quality from competition and demand data. |
N=.15 U=.20 M=.15 R=.30 V=.20
Feasibility (73%)
Data Availability
23.3/25
Feasibility Breakdown
| Tech Complexity | / 40 | Difficulty of core implementation stack. |
| Data Availability | / 25 | Practical availability and cost of required data. |
| MVP Timeline | / 20 | Expected time to ship a usable MVP. |
| API Bonus | / 15 | Bonus for viable public API leverage. |
Market Validation (70/100)
Validation Breakdown
| Competition | / 20 | Signal quality from competitor landscape. |
| Market Demand | / 20 | Demand proxies from search and mention patterns. |
| Timing | / 20 | Fit with current shifts in tech, behavior, and regulation. |
| Revenue Signals | / 15 | Reference evidence for monetization viability. |
| Pick-Axe Fit | / 15 | How well the concept serves participants in a trend. |
| Solo Buildability | / 10 | Practicality for lean-team implementation. |
Technical Requirements
Frontend [medium]
Backend [medium]
AI/ML [low]