A
Long-Term Care Grade Document Assembly Coach
4.20
Derivation Chain
Step 1
Parent care administration automation
→
Step 2
The problem of complex document preparation for long-term care grade applications
→
Step 3
Connecting to doctor's opinion letter and assessment-day response coaching
Problem
Working professionals aged 45-55 applying for their parents' (aged 70-80) long-term care grade must prepare documents (doctor's opinion letter, long-term care recognition application, functional status evidence) from three separate agencies: the National Health Insurance Service, their primary physician, and the local community center. A frequent issue is that parents answer 'I'm fine' during the in-person assessment, resulting in a lower-than-actual grade. Without pre-assessment coaching information, families waste 3-6 months on reapplication.
Solution
On a web platform, users input their parent's current status (mobility, cognition, daily living activities) via a checklist, which auto-generates the expected care grade and required document list. It provides situation-specific tips for assessment day — including a 'guide for accurately communicating actual conditions' — and generates a key-items memo to hand to the primary physician when requesting the doctor's opinion letter.
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 (68%)
Data Availability
18.3/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 (61/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]