B
Middle East Exposure Check for My Funds & ETFs
2.95
Derivation Chain
Step 1
Iran airstrikes and Middle East war tensions
→
Step 2
50-something investors concerned about asset protection
→
Step 3
War risk → not knowing how much my funds/ETFs are exposed to the Middle East
Problem
After seeing news of Iran's airstrikes and the Israel war, a 50-something investor wants to check how much their funds and ETFs are exposed to the Middle East, but they have to manually review each holding. Especially global ETFs, oil-related funds, and emerging market funds have hidden Middle East exposure, making it impossible to get a comprehensive view of 'my portfolio's Middle East exposure.' Securities apps show individual fund holdings but don't calculate the total 'Middle East-related weight.'
Solution
Users enter their fund/ETF names on the web (or upload a screenshot of their securities holdings), and the system extracts Middle East-related allocation weights from each fund's prospectus to calculate the overall 'Middle East exposure' as a percentage. It also includes indirect exposure to oil-linked assets and companies with high Middle East revenue (construction, plant). If exposure is high, rebalancing scenarios are suggested.
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 (48%)
Data Availability
22.5/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 [high]