S
Health Checkup Numbers Life Coach
4.05
Derivation Chain
Step 1
Health Checkup result interpretation & tracking
→
Step 2
Year-over-year value change tracking
→
Step 3
Connecting value changes to specific lifestyle behavioral prescriptions
Problem
Working professionals aged 45–60 receive annual national Health Checkups but don't understand what changes like 'fasting glucose 105→112' actually mean or what to change. Doctor consultations last 3 minutes and yield only vague advice like 'adjust your diet.' As a result, patients miss the 2–3 year golden window between borderline numbers and disease onset. Once diabetes or hypertension develops, ₩100,000–300,000/month (~$75–225) in lifetime Medical expenses follow.
Solution
Upload a Health Checkup results PDF; OCR auto-extracts values and displays year-over-year trend graphs. For each change, the system provides specific, actionable behavioral prescriptions — e.g., 'Fasting glucose up 7% → walk 30 minutes 3x/week after dinner, switch white rice to multigrain.' A 3-month reminder sets target numbers before the next checkup.
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 (74%)
Data Availability
24.4/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 (56/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
AI/ML [medium]
Frontend [medium]
Backend [low]