B
Parent's Care Grade Pre-Diagnosis
4.25
Derivation Chain
Step 1
Employment changes/economic insecurity in the AI era
→
Step 2
Increasing caregiving burden for the 50s sandwich generation
→
Step 3
Difficulty in determining the timing and preparation for elderly parents' long-term care grade application
Problem
A 52-year-old office worker with parents in their 80s misses out on benefits for months to years because they cannot determine the right time to apply for long-term care grade. The assessment criteria (52 items) are public, but difficult for the general public to understand, and there is no way to estimate in advance what grade their mother might receive. If the application is rejected, they must wait 6 months to reapply, so the loss from applying unprepared is significant. Currently, the only way is to informally ask a care worker or social worker.
Solution
On the web, (1) input the parent's daily living abilities through a simplified 15-question survey based on the 52 assessment items, (2) it presents the expected care grade and score range, (3) guides on items that must be included in the doctor's opinion to increase the likelihood of grade approval, and (4) compares available home-based and facility services and out-of-pocket costs by grade.
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. |
N=.15 U=.20 M=.15 R=.30 V=.20
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 (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 [low]
Backend [medium]