B
National Health Checkup Cancellation Alert
2.70
Derivation Chain
Step 1
Aging society and growing health management interest
→
Step 2
Stagnant checkup completion rates among ages 40–60
→
Step 3
Preferred hospitals and dates fully booked, leading to year-end rush or skipped checkups
Problem
Workers and regional subscribers aged 40–60 trying to book their national Health Checkup find that preferred clinics are booked 2–3 months out, with Saturday and weekday morning slots especially competitive. There are no real-time notifications when cancellations occur, forcing people to call or check websites daily. They end up procrastinating until December's year-end rush or skipping the checkup entirely, missing early detection of health issues.
Solution
Users register 3–5 preferred checkup facilities and desired dates/time slots on the web. When a cancellation opens up, they receive an instant KakaoTalk or SMS alert. One-click navigation to the booking page. Also provides a preparation checklist by checkup item.
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 (57%)
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 (54/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
Data Pipeline [high]
Backend [medium]
Infrastructure [low]