A
Retirement Health Insurance Premium Shock Defense Simulator
4.10
Derivation Chain
Step 1
Strengthened public data center security standards → Strengthened sensitive data protection policies
→
Step 2
Government digital policies also affect personal data and social insurance systems
→
Step 3
Simulation to prepare for the surge in premiums based on owned assets when converting from workplace to regional health insurance after retirement
Problem
When employees aged 55-60 retire, their workplace health insurance converts to regional health insurance, and at that time all owned real estate, financial assets, and vehicles are reflected in the premium calculation, causing monthly premiums to surge from the previous 100,000-150,000 KRW (approx. $75-$112.50) to 300,000-800,000 KRW (approx. $225-$600). The National Health Insurance Service website allows mock calculations, but users must separately check and input real estate official prices, financial income, and pension income, and there is no scenario comparison feature to show 'which assets should be adjusted before retirement to reduce premiums.' Most people are shocked only after receiving the first bill post-retirement, missing the opportunity for advance preparation.
Solution
By inputting real estate holdings (official prices), financial assets, vehicles, and expected pension income, the service automatically calculates the expected monthly premium after retirement when converting to regional health insurance. It shows 3-5 cost-saving scenarios in a comparison table, such as 'when selling real estate,' 'when using voluntary continued enrollment (maintaining workplace health insurance for 36 months after retirement),' and 'when diversifying financial income,' along with the legal requirements and precautions for each scenario.
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 (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]