S
Solo Household Transition 72-Hour Plan
4.20
Derivation Chain
Step 1
Solo household transition planning
→
Step 2
Simultaneous administrative and lifestyle changes during sudden solo transition
→
Step 3
First 3 months post-transition fixed cost optimization simulation
Problem
When people in their late 50s to early 60s suddenly become single-person households due to children moving out or spousal bereavement, they must simultaneously handle housing downsizing, utility name transfers, national health insurance status changes, and food budget restructuring — without knowing the proper sequence or priorities for visiting each agency. The bigger problem is that for the first 3 months after transition, fixed costs (maintenance fees, health insurance premiums, food expenses) run 30-40% less efficiently per capita compared to when they were a two-person household.
Solution
Users enter their transition reason (independence/divorce/bereavement) along with current housing type and income on the web, and the service generates a 3-phase roadmap: 'administrative tasks within 72 hours → lifestyle changes within 1 week → fixed cost optimization within 1 month.' Each phase includes agency visit sequences, required documents, and estimated time needed. A post-transition monthly fixed cost simulation quantifies the downsizing savings.
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 (56/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]