B
Parent Care Facility Checklist
3.70
Derivation Chain
Step 1
Parent care coordination
→
Step 2
Post-care-grade service selection
→
Step 3
Information asymmetry in facility selection after deciding between home care vs. facility transition
Problem
After a parent in their 80s receives a confirmed long-term care grade, adult children aged 50-58 who have decided on facility admission face a problem: the National Health Insurance Service's 'Find Long-Term Care Facility' tool only filters by address and care grade. Critical information—whether night nurses are on-site, availability of dementia-specific programs, detailed out-of-pocket costs, and wait times—requires calling each facility directly. On average, families call 5-8 facilities and visit 3-4, taking 2-3 weeks, during which they must continue providing unpaid caregiving.
Solution
Users input their parent's care grade, conditions, and preferred residential area. The tool lists matching care facilities and auto-generates a must-ask checklist for each (night staffing, meal plans, programs, actual costs, contract considerations). It provides a facility comparison table for on-site visits, and when users record post-visit evaluations, it calculates a final recommendation ranking.
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 (65%)
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 (58/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 [medium]