B
Small Portfolio Rebalancer
2.70
Derivation Chain
Step 1
Small-scale asset rebalancing
→
Step 2
After-tax return-based asset allocation without a private banker
Problem
A 55-year-old pre-retiree holds approximately 280 million won (~$210,000) in combined assets: 150 million won (~$112,500) in severance pay + 50 million won (~$37,500) in private pension + 80 million won (~$60,000) in savings deposits. Private banking services require minimum 500 million won (~$375,000), putting them out of reach. Securities firm robo-advisors only recommend investment products without providing after-tax return-based rebalancing across their entire portfolio including real estate, savings, and pensions. They end up allocating assets by intuition, unnecessarily overpaying millions of won annually in taxes and health insurance premiums.
Solution
Users enter their holdings (Real Estate, savings deposits, Retirement Pension, private pension, stocks/ETFs) on a web interface, and the system diagnoses inefficiencies in their current allocation based on after-tax real returns, then proposes three rebalancing scenarios (conservative/balanced/growth). Each scenario simulates the annual difference in taxes + health insurance premiums, showing concrete amounts like 'reallocating this way saves 1.2 million won (~$900) per year.'
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 (58%)
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 (51/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 [high]
Data Pipeline [low]