No usable source links are available for this idea. Its signal notes and scores need independent verification.
When a 56-year-old retiree registers as a dependent on their spouse's national Health Insurance, their premium is 0 KRW. However, if annual income (financial income, Rental income, Pension income, etc.) exceeds 20,000,000 KRW (~$15,000) or property tax assessed value exceeds 540,000,000 KRW (~$405,000), they lose dependent status. The problem is that it is extremely difficult to calculate in advance how Retirement Pension withdrawals, real estate sales, and financial income affect dependent eligibility. Upon losing status, regional subscriber premiums surge to 200,000–500,000 KRW/month ($150–$375), adding 2,400,000–6,000,000 KRW ($1,800–$4,500) in annual costs. Disqualification notices arrive after the fact, making prevention impossible.
Users input their current income sources (financial income, Rental income, National Pension, Retirement Pension, etc.) and property information for an instant dependent status eligibility diagnosis. By entering future plans (starting Retirement Pension withdrawals, selling Real Estate, financial product maturity dates, etc.), the service generates a monthly dependent status change prediction timeline. When disqualification risk is detected, it suggests defensive strategies for redistributing income (adjusting withdrawal timing, utilizing separate taxation, etc.).
| 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. |
| 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. |
| 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. |