S
US Stock Downturn Pension Defense Coach
4.15
Derivation Chain
Step 1
S&P 500 crash and AI layoff fears
→
Step 2
Pension asset defense issues for 50s overseas stock investors
→
Step 3
Decision-making on adjusting overseas ETF allocation in DC-type retirement pensions
Problem
Among office workers around age 55, the number of people who have allocated 30-50% of their DC-type retirement pension to S&P 500 ETFs has surged. During market crashes, they must decide alone whether to sell now or hold. Securities apps only show returns, not the reasoning linked to remaining years until retirement, expected payout, and tax implications. Fear-driven selling at the bottom repeatedly leads to losses of millions of won in retirement funds.
Solution
On the web, users input their DC-type retirement pension management status (ETF ratio, balance) and expected retirement date. The service visually compares 'probability of recovery by retirement', 'difference in final payout if switching to safe assets now', and 'three after-tax net income scenarios' against the current drawdown. It explains based on historical similar downturns (2020, 2022).
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. |
N=.15 U=.20 M=.15 R=.30 V=.20
Feasibility (70%)
Data Availability
20.6/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 (74/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]