B
Brokerage API Unified Dashboard
2.55
Derivation Chain
Step 1
KOSPI surge & retail investor trading volume explosion
→
Step 2
Need for multi-brokerage account management
→
Step 3
Cross-brokerage data integration Infrastructure
→
Step 4
Unified asset dashboard for individual investors
Problem
68% of stock investors hold accounts at 2+ brokerages, but must check balances, returns, and trade history separately in each brokerage app, spending 15–30 minutes daily to get a full portfolio overview. During KOSPI surges, the inefficiency is amplified as cross-account information checks become frequent for rebalancing positions across stocks.
Solution
Integrates open APIs (OpenAPI, xing-API, etc.) from major Korean brokerages — Korea Investment, Kiwoom, Samsung, Mirae Asset, NH Investment — to display balances, holdings, returns, and dividend history from multiple accounts in a single dashboard. Provides cross-account average purchase prices per stock, sector allocation breakdowns, return rankings, and rebalancing recommendations.
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 (52%)
Data Availability
15.0/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 (54/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
Backend [high]
Frontend [medium]
Data Pipeline [low]