A
Post-Retirement Health Insurance Shock Calculator
4.25
Derivation Chain
Step 1
Digital administrative delegation
→
Step 2
Missed deadlines and overpayment due to fragmented procedures
→
Step 3
Preparing for premium surge when switching from employer to regional health insurance at retirement
→
Step 4
Integrated total-burden simulation connecting health insurance + pension + tax
Problem
When a 57-year-old employee retires, they switch from employer-based health insurance to regional health insurance, where premiums factor in Real Estate and financial income — causing monthly premiums to triple from 150,000 won (~$112) to 450,000 won (~$337) in many cases. Total burden also varies depending on National Pension start date and comprehensive income tax filing status, but no tool connects these three systems. Each must be checked separately on NHIS, NPS, and HomeTax, and understanding their interactions alone takes days.
Solution
Enter current salary, owned Real Estate (assessed value), financial income, and estimated National Pension amount on the web to see projected regional health insurance premiums post-retirement + premium changes when pension payments begin + income tax bracket — all on one screen. Compare scenarios like 'selling one property,' 'changing pension start date,' and more.
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 (58%)
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 (59/100)
Solo Buildability
10.0/10
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 [high]
Data Pipeline [low]