B
Post-Retirement Health Insurance Transition Simulator
3.65
Derivation Chain
Step 1
Interest in senior workers and EITC
→
Step 2
Confusion about changes in four major insurance statuses before and after retirement
→
Step 3
Lack of strategies to prepare for premium surges when transitioning from workplace to regional health insurance
Problem
One of the biggest fears for employees aged 53-58 approaching retirement is a surge in health insurance premiums. When transitioning from workplace subscriber to regional subscriber after retirement, premiums that were 150,000 KRW (approx. $112.50) per month can jump 3-5 times to 400,000-800,000 KRW (approx. $300-$600) per month, as real estate, vehicles, and financial income are all factored in. However, accurately calculating post-transition premiums in advance requires visiting or calling the National Health Insurance Service, and most people are unaware of cost-saving options like voluntary continued enrollment (maintaining workplace premiums for 36 months after retirement).
Solution
Users input current workplace insurance premium, publicly assessed value of owned real estate, vehicle, and financial income on the web, and the service automatically calculates the estimated regional health insurance premium after retirement. It compares monthly premiums under three scenarios: voluntary continued enrollment, regional transition, and registration as a dependent of a spouse. It also checks whether each option's eligibility requirements are met, and automatically determines if income/asset thresholds are exceeded for dependent registration.
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 (70%)
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 (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]
Data Pipeline [low]