A

Couple's Pension Withdrawal Scenario Planner

4.15

Derivation Chain

Step 1 Spreading AI anxiety and investment uncertainty
→
Step 2 Retirement fund anxiety among couples in their 50s
→
Step 3 Lack of after-tax comparison tools for couple's pension withdrawal timing and sequencing

Competitor references

No usable source links are available for this idea. Its signal notes and scores need independent verification.

Problem

Dual-income couples aged 55-60 each hold National Pension, Retirement Pension, and private pensions, but have no way to simulate which spouse should start withdrawing first, at what age, and from which pension to maximize total after-tax income. They must check the National Pension Service, retirement pension managers, and the National Tax Service separately, and factoring in combined income tax and health insurance premiums requires paying a tax accountant ₩500,000-1,000,000 (~$375-$750). Poor withdrawal sequencing can result in ₩2-4 million (~$1,500-$3,000) in annual tax differences.

Solution

Each spouse enters their pension types, expected payouts, and planned start ages on a web interface, and the system automatically generates a 10-20 year cash flow table reflecting combined income tax, health insurance premiums, and Basic Pension eligibility impacts. Adjusting withdrawal timing via sliders updates after-tax totals in real time. Includes automatic optimal combination recommendations.

Target: Dual-income or single-income couples aged 55-62, within 2-5 years of retirement, holding 2+ pension types (National Pension + Retirement Pension + private pension), seeking self-review before consulting a tax accountant
Revenue Model: Basic simulation free. Couple's optimized report PDF download ₩5,000 (~$3.75) per transaction. Tax accountant referral commission.
Ecosystem Role: Consumer
MVP Estimate: 2_weeks

NUMR-V Scores

N Novelty
3.0/5
U Urgency
5.0/5
M Market
4.0/5
R Realizability
4.0/5
V Validation
5.0/5
NUMR-V Scoring System
N Novelty1-5How uncommon the service is in market context.
U Urgency1-5How urgently users need this problem solved now.
M Market1-5Market size and growth potential from proxy indicators.
R Realizability1-5Buildability for a small team with realistic constraints.
V Validation1-5Validation signal quality from competition and demand data.
Each dimension is scored 1-5 and weighted into grade S/A/B/C/D.
N=.15 U=.20 M=.15 R=.30 V=.20

Feasibility (70%)

Tech Complexity
29.3/40
Data Availability
20.8/25
MVP Timeline
20.0/20
API Bonus
0.0/15
Feasibility Breakdown
Tech Complexity/ 40Difficulty of core implementation stack.
Data Availability/ 25Practical availability and cost of required data.
MVP Timeline/ 20Expected time to ship a usable MVP.
API Bonus/ 15Bonus for viable public API leverage.
Total 100 points; below 50% is filtered out.

Market Validation (61/100)

Competition
8.0/20
Market Demand
9.4/20
Timing
16.0/20
Revenue Signals
10.5/15
Pick-Axe Fit
10.5/15
Solo Buildability
7.0/10
Validation Breakdown
Competition/ 20Signal quality from competitor landscape.
Market Demand/ 20Demand proxies from search and mention patterns.
Timing/ 20Fit with current shifts in tech, behavior, and regulation.
Revenue Signals/ 15Reference evidence for monetization viability.
Pick-Axe Fit/ 15How well the concept serves participants in a trend.
Solo Buildability/ 10Practicality for lean-team implementation.
Total 100 points; below 50 is filtered out.

Technical Requirements

Frontend [medium] Backend [medium] Data Pipeline [low]
Dashboard