When office workers around age 55 at large companies need to decide whether to transfer their Retirement Pension from DC to IRP or take a lump sum, they must look up retirement income tax, pension income tax, and health insurance premium changes across different websites, spending half a day or more on comparisons. A wrong choice can mean a difference of millions of won (~thousands of USD), yet bank counters only recommend their own products.
Solution
Enter total retirement benefit, years of service, and expected withdrawal timing on the web to compare after-tax net proceeds across three paths — DC retention, IRP transfer, and lump-sum withdrawal — in a year-by-year table that aggregates retirement income tax, pension income tax, and health insurance premium changes. A 10-year cumulative net-flow graph including fee differences is also provided.
Target: Office workers aged 52–58 at large corporations or public enterprises, 1–3 years before retirement, enrolled in DC-type Retirement Pension
Revenue Model: Basic comparison free; detailed PDF Report (itemized fee and tax breakdown) at 5,000 KRW (~$3.75) Per Transaction. Future IRP referral commission possible.
Ecosystem Role: Supplier
MVP Estimate: 2_weeks
NUMR-V Scores
N Novelty
3.0/5
U Urgency
5.0/5
M Market
4.0/5
R Realizability
5.0/5
V Validation
5.0/5
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.
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
/ 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 (75/100)
Competition
10.0/20
Market Demand
20.0/20
Timing
16.0/20
Revenue Signals
10.5/15
Pick-Axe Fit
10.5/15
Solo Buildability
8.0/10
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.