B
Checkup Percentile Compass
3.60
Derivation Chain
Step 1
Chronic disease multi-medication management
→
Step 2
Inability to gauge 'how bad this number actually is' after receiving checkup results
→
Step 3
Without knowing your position relative to peers of the same age, gender, and body type, there is no sense of urgency or motivation
Problem
When adults in their 50s-60s receive annual health checkup results, they only get a 3-tier classification of 'Normal/Borderline/Abnormal' with no contextual information — such as where their blood sugar ranks among 55-year-old males, or whether their year-over-year decline is faster or slower than average. When they receive a borderline result (e.g., fasting glucose of 105), they dismiss it as 'still within normal range,' but in reality it may be significantly above the peer average (95), requiring urgent management. A 3-minute doctor consultation is insufficient to convey this context.
Solution
Users enter key health checkup metrics (blood sugar, blood pressure, cholesterol, BMI, liver enzymes, etc.) on a web interface, which then visualizes their percentile position within the statistical distribution for their age and gender cohort. Year-over-year trends are displayed as graphs, with trajectory analysis such as 'At this rate, there is a ○% chance of entering pre-diabetic stage within 3 years.' For each metric, a specific, actionable lifestyle change is recommended.
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. |
SaaS N=.15 U=.20 M=.15 R=.30 V=.20
Senior N=.25 U=.25 M=.05 R=.30 V=.15
Feasibility (73%)
Data Availability
20.6/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 (53/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 [low]