A
Pension Payout Scenario Planner
3.85
Derivation Chain
Step 1
Integrated Retirement Pension and private Pension simulation
→
Step 2
Inability to project across fragmented Pension accounts
→
Step 3
Need to compare after-tax net payouts based on timing and withdrawal method
Problem
Workers approaching age 55 face tens of thousands of dollars in after-tax payout differences depending on when they start National Pension, whether they take Retirement Pension as a lump sum or annuity, and the IRP withdrawal sequence—but have no tool to compare scenarios. Each financial institution's app only shows its own products, and no service exists that integrates taxes (retirement income tax, Pension income tax, and health Insurance premium linkage).
Solution
Manual entry of National Pension, Retirement Pension, IRP, and private Pension balances for scenario-by-scenario after-tax monthly payout comparison / break-even visualization with a payout start-age slider / health Insurance dependent disqualification timing alert
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 (53%)
Data Availability
21.7/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 (63/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
Backend [high]
Frontend [medium]
Backend [medium]