B
Geopolitical Risk Supply Chain Checker
3.55
Derivation Chain
Step 1
Iran risk and Strait of Hormuz crisis
→
Step 2
Supply chain risk management for SMEs
→
Step 3
Automatic diagnosis of supply chain vulnerabilities by geopolitical event and alternative suggestions
Problem
SMEs with 10-50 employees in manufacturing take 3-7 days to identify which raw materials and components in their supply chain pass through the affected region when a geopolitical event like the Middle East crisis occurs. The purchasing manager must individually check with dozens of suppliers, and during this period, they miss the timing for alternative sourcing, incurring late delivery penalties (several million KRW per incident).
Solution
When a company registers its supplier list and raw material origin/transit information, the service automatically identifies affected items and suppliers when a geopolitical event occurs and recommends alternative sourcing options. Key features: (1) automatic supply chain impact report upon detection of geopolitical events, (2) alternative sourcing recommendations by item (based on Korea Customs Service import statistics), (3) risk heatmap dashboard.
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.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 (58/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]