B
Eldercare Document Auto-Assembler
3.75
Derivation Chain
Step 1
Eldercare administrative assistance
→
Step 2
Care facility admission document preparation
→
Step 3
Facility-specific document differences + auto-checklist + issuing authority mapping
Problem
When adults in their 50s prepare to admit an elderly parent (80+) to a care facility, each facility requires different documents (Health Checkup certificate, long-term care certification, diagnosis, guardianship papers, etc. — 8 to 15 types). They must call each facility to confirm which documents are needed, where to get them, and their validity periods. A single missing document delays admission by 2-4 weeks.
Solution
Users select 3 preferred care facilities on the web, and the system auto-compares required documents across facilities to generate a unified checklist. It displays each document's issuing authority, method (online/in-person), validity period, and processing time, then auto-calculates a reverse schedule (what to do by D-minus-how-many-days based on the target admission date).
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 (55/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]