A
Long-Term Care Home Benefit Planner
4.20
Derivation Chain
Step 1
Parent caregiving administration
→
Step 2
Benefit combination planning after receiving a care grade
→
Step 3
Unknown optimal combination within the monthly home care benefit cap
Problem
When parents receive long-term care grade 3-4, adult children in their 50s cannot determine the optimal combination of home-visit care, home-visit bathing, home-visit nursing, day/night care, and assistive devices within the monthly benefit cap (approximately 1,280,000 KRW / ~$960 for grade 3). Care agency recommendations are biased toward their own services, and the National Health Insurance Service simply advises 'the family decides.' As a result, families either use only 60-70% of their benefit cap or exhaust it on services that don't match actual needs.
Solution
On a web interface, users enter their parent's care grade, primary needs (mobility assistance, cognitive training, bathing, meals, etc.), and family caregiving availability by time slot. The service then: (1) simulates 3-5 possible benefit combinations within the monthly cap, (2) compares actual out-of-pocket costs (15% co-pay) and service hours for each combination, (3) matches nearby home care agencies along with their quality ratings.
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 (70%)
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 (60/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]