No usable source links are available for this idea. Its signal notes and scores need independent verification.
The tax structure in the first year after retirement is completely different from during employment. Retirement income tax settlement, mid-year year-end tax adjustment, comprehensive income tax filing (May), health insurance dependent status determination (November), and property tax/comprehensive real estate tax payments all overlap — and the company HR team no longer handles them. In particular, the method of receiving retirement pay (lump sum vs. Retirement Pension) changes the following May's comprehensive income tax filing requirements, and failure to account for this results in penalty taxes. Cases of missing 500,000-2,000,000 KRW (~$375-$1,500) in refunds or paying penalty taxes in the first year of retirement are common.
On a web interface, users enter their retirement date, retirement pay receipt method, and other income sources (Rental, interest, dividends). The service then: (1) auto-generates a month-by-month tax and insurance event calendar for the 12 months post-retirement, (2) provides filing/payment deadlines and document preparation checklists for each event, (3) calculates estimated mid-year year-end tax adjustment refund, (4) sends D-30 and D-7 deadline reminders.
| 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. |