B
Checkup Alert Follow-Up Coach
3.00
Derivation Chain
Step 1
Post-Health Checkup follow-up management
→
Step 2
Lack of actionable guidance after borderline results
→
Step 3
Inability to sustain lifestyle changes between retests leads to worsening metrics
Problem
When workers aged 52-60 receive borderline results from their national Health Checkup—such as fasting blood sugar in the 'pre-diabetic' range (100-125 mg/dL) or blood pressure in the 'elevated' range (130-139/85-89)—the results sheet only says 'lifestyle improvement recommended' with no specifics on what to change, by how much, when to retest, or which specialist to visit. Even at follow-up appointments, they're told 'come back in 6 months' with no way to track how dietary, exercise, or sleep changes affect their numbers over that period. The result: borderline conditions are neglected until they progress to diabetes or hypertension.
Solution
A web service where (1) users upload their checkup results PDF, which is auto-parsed to visualize each metric as 'normal/borderline/abnormal'; (2) for each borderline item, a '90-Day Action Plan' is generated (retest timing, recommended specialist, dietary and exercise guidelines); and (3) when past checkup results are also uploaded, year-over-year trend lines for key metrics are plotted to enable early detection of worsening trajectories.
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 (69%)
Data Availability
20.0/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 [medium]
Data Pipeline [low]