B
Long-Term Care Rating Autopilot
3.75
Derivation Chain
Step 1
Elder care administration delegation
→
Step 2
Fragmented long-term care rating application process
→
Step 3
One-stop management from rating determination through benefit combination optimization
Problem
A 55-year-old office worker applying for a long-term care rating for their 82-year-old mother must navigate: National Health Insurance Service application → doctor's opinion issuance (hospital) → assessment schedule coordination → rating decision wait → post-decision benefit selection (home care/facility/special cash). This involves visiting 4 different agencies over an average of 45 days. Required documents, deadlines, and precautions for each stage are scattered across different websites, and since processing must happen during weekday business hours, workers use up 3-4 vacation days.
Solution
Users enter their parent's age, conditions, and current care status on the web, and the tool: (1) consolidates the document checklist and issuing offices for care rating application on one page, (2) auto-generates a step-by-step progress timeline (D+0 application → D+14 assessment, etc.), (3) provides a comparison table of out-of-pocket costs by home care/facility/special cash benefit combinations after rating determination.
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 (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 [medium]
Data Pipeline [low]