B
Caregiving + Retirement Dual Calendar
3.50
Derivation Chain
Step 1
Simultaneous parent caregiving + personal retirement planning
→
Step 2
Caregiving programs and retirement programs are completely separated, making priority decisions impossible
Problem
Mid-50s workers must simultaneously manage long-term care grade applications and care costs for their 80+ parents while handling their own retirement pension rollovers and health insurance transitions. Parent caregiving info (Ministry of Health, National Health Insurance, local government) and personal retirement info (National Pension, retirement pension, HomeTax) are completely siloed across separate systems. Managing both in parallel consumes 5-10 vacation days per year, and missing application deadlines frequently results in lost benefits worth hundreds of dollars.
Solution
A web calendar that integrates parent caregiving administration (care grade renewal dates, assistive device replacement cycles, co-payment settlement dates) with personal retirement administration (pension rollover deadlines, health insurance transition filing dates, year-end tax settlement). Each event includes required documents, application links, and estimated time needed — showing 'what needs to be done this month' at a glance.
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 (73%)
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 (54/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 [low]
Data Pipeline [low]