B
Post-Independence Insurance Portfolio Remodeler
2.95
Derivation Chain
Step 1
Digital asset and account consolidation
→
Step 2
Inability to see scattered insurance portfolio at a glance
→
Step 3
Need to redesign insurance portfolio at children's independence and retirement milestones, but agent advice is biased
Problem
A 55-year-old professional still maintains 5–7 insurance policies purchased in their 30s (whole life, children's insurance, private medical, cancer, driver's insurance, etc.). Now that their children are independent, children's and education insurance are unnecessary, and the whole life insurance premium of 150,000 KRW (~$112) per month will become burdensome after retirement. Consulting an insurance agent results in recommendations to convert or add policies rather than cancel. There is no neutral information source to help decide which policies to keep, reduce, or cancel.
Solution
Enter current insurance details (insurer, product name, monthly premium, coverage, maturity date) and the service will: (1) classify unnecessary vs. essential coverage for the current life stage (children independent / approaching retirement), (2) calculate surrender value and savings for each keep/reduce/cancel scenario, (3) flag coverage gaps (e.g., missing long-term care rider).
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 (64%)
Data Availability
20.0/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 [medium]
Backend [medium]