A
Checkup Action Planner
4.00
Derivation Chain
Step 1
Health Checkup follow-up actions
→
Step 2
Difficulty interpreting checkup result values
→
Step 3
Even after interpretation, unable to prioritize which specialty to visit and by when
Problem
When a 52-year-old office worker receives their comprehensive health checkup results, 15-20 metrics are listed—liver enzymes (GGT/AST/ALT), blood sugar (fasting/HbA1c), blood pressure, cholesterol, etc.—but there's no clear guidance on which values require 'monitoring' versus 'immediate medical attention.' During the 4-6 week average wait for a follow-up, anxiety builds, and visiting a local clinic often yields nothing more than 'go see a bigger hospital.'
Solution
Enter your checkup results and the system classifies each metric into three urgency tiers (Immediate / Within 4 Weeks / Monitor) based on Korean Medical Association standards, showing recommended specialties, test names, and estimated costs for each item. When previous year's results are entered, it visualizes trends and rate of deterioration.
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 (68%)
Data Availability
18.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 (72/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]