B
Retirement Pension DC/IRP Auto-Rebalance Designer
3.55
Derivation Chain
Step 1
Retirement Pension optimization
→
Step 2
DC-type/IRP neglect problem
→
Step 3
Post-neglect rebalancing timing & ratio decision problem
Problem
Workers in their 50s who opened a DC-type Retirement Pension or IRP often leave funds parked in the default option (principal-guaranteed products). Even when aware, they cannot compare options because product names differ across brokerages. Designing a rebalance plan that accounts for years until retirement, risk tolerance, and tax benefit limits takes 3–4 hours, so most give up and continue missing 2–3% annual returns.
Solution
Enter your expected retirement date, current DC/IRP balance, and risk profile (3 questions) on the web to receive an auto-generated allocation plan mapped to representative product categories (TDF, bond-mixed, deposit) by brokerage. Simulates year-by-year tax deduction optimization (pension savings vs. IRP allocation) and provides a rebalance timing alert calendar.
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 (70%)
Data Availability
20.8/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 (57/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
Frontend [medium]
Backend [medium]
Data Pipeline [low]