B
Care System Timeline Builder
3.80
Derivation Chain
Step 1
Parent care cost & program navigation
→
Step 2
Identifying transition points as parent's condition changes
→
Step 3
Auto-mapping available services & costs by health status
Problem
Adults aged 45–55 caring for parents aged 75–85 face a maze of government care programs (Emergency Care SOS, Senior Care Services, Long-Term Care Insurance, Nursing Facility Admission) that change depending on the parent's health stage (independent living → partial assistance → care grade application → facility admission). They don't know these transition points, so when a parent suddenly falls or shows cognitive decline, they scramble to find information. Consolidating fragmented information across the Ministry of Health, National Health Insurance Service, and local governments takes 3–5 days.
Solution
Enter the parent's current status (mobility, cognitive level, chronic conditions) to visualize a timeline of currently available programs and future programs to transition to as conditions change. Each program includes the application agency, required documents, estimated costs, and out-of-pocket amounts. Set alerts for 'When your parent reaches this condition, apply for this program.'
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.8/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 (57/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]