B
Our Couple's Health Insurance Premium Tax-Saving Navigator
3.55
Derivation Chain
Step 1
Increase in early retirement due to AI paradox
→
Step 2
Health insurance transition after retirement
→
Step 3
Annual difference of several million KRW in health insurance premiums depending on which spouse is registered as a dependent
Problem
When one spouse in a 55-60 year old couple retires, they transition from workplace subscriber to regional subscriber. At this point, depending on the couple's assets (real estate, financial) and income structure, calculating which combination—'husband as dependent' vs 'wife as dependent' vs 'both as regional subscribers'—minimizes health insurance premiums is extremely complex. The National Health Insurance Service consultation only provides one scenario, and tax accountant consultations cost 150,000-200,000 KRW per case (approx. $112.50-$150). Depending on the combination of real estate official assessed value, financial income, and pension income, the difference can be 1,000,000-3,000,000 KRW per year (approx. $750-$2,250). Most couples in their 50s are unaware of this difference and switch in an unfavorable way, overpaying for years.
Solution
On the web, users input each spouse's income (employment, business, pension, financial), assets (real estate official assessed value, car, financial assets), and whether they meet dependent requirements. The system automatically calculates monthly health insurance premiums for all possible combinations and recommends the optimal one. It also provides a 3-year simulation reflecting future variables such as pension start date and real estate sale plans, showing the most advantageous long-term strategy.
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 (56%)
Data Availability
19.2/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 [high]
Data Pipeline [low]