B
Foreign Stock ETF Currency Hedge Simulator
3.15
Derivation Chain
Step 1
KOSPI breaking 6000 drives growing interest in overseas diversification
→
Step 2
Currency risk in foreign stock ETFs becomes prominent
→
Step 3
Currency hedging strategy simulation tool
Problem
As KOSPI breaks through 6000, investors with overweighted domestic assets are attempting to diversify into foreign ETFs, but there's no intuitive way to compare the real return differences between currency-hedged (H) and currency-exposed ETFs across various KRW/USD exchange rate scenarios. Calculating real returns factoring in hedging costs (1-3% annually) requires 2-3 hours of Excel work, and most investors end up making decisions while ignoring currency fluctuations entirely.
Solution
(1) Select a foreign ETF to view comparison charts of historical returns for hedged vs. unhedged versions including currency fluctuations, (2) simulate projected returns across future exchange rate scenarios (appreciation/depreciation/sideways), and (3) visualize the overall portfolio's currency exposure by individual currency.
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 (64%)
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 (50/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 [medium]
Frontend [medium]
Data Pipeline [low]