B

Pre-Retirement Corporate Pension Payout Option Comparator

3.85

Derivation Chain

Step 1 AI boom reshaping semiconductor component industry structure
→
Step 2 Rising early retirement among 50-somethings due to restructuring at large component makers
→
Step 3 Lack of tools to compare after-tax net proceeds across retirement pension (DB/DC/IRP) payout methods

Competitor references

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

Problem

Employees at large and mid-sized companies aged 53-58 cannot determine whether to take their retirement pension as a lump sum, annuity, or IRP transfer to maximize net proceeds after combining taxes and health insurance premiums. Retirement income tax, pension income tax, and health insurance dependent eligibility loss criteria are scattered across different laws, and online calculators only compute taxes without reflecting the surge in health insurance premiums. A wrong choice can result in 2-5 million KRW (approx. $1,500-$3,750) in additional annual burden.

Solution

Users enter total severance amount, years of service, and expected post-retirement income on the web, and the service (1) compares after-tax net proceeds for lump sum vs. 10-year annuity vs. lifetime annuity scenarios in year-by-year tables, (2) reflects whether health insurance dependent status is maintained or lost in each scenario along with estimated regional health insurance premiums, and (3) provides a comprehensive recommendation including the optimal payout method and tax savings from additional IRP contributions.

Target: Ages 53-58, office workers at large/mid-sized companies, retirement pension (DB or DC) balance of 100 million KRW (approx. $75,000) or more, spouse with no income (sensitive to dependent status)
Revenue Model: Basic 3-scenario comparison free; comprehensive design report linked to spouse and real estate income at 7,900 KRW (approx. $5.90) per transaction.
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
3.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 (72%)

Tech Complexity
29.3/40
Data Availability
23.1/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 (56/100)

Competition
8.0/20
Market Demand
6.2/20
Timing
14.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

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