B
Supply Chain Alert for Security Crises
2.85
Derivation Chain
Step 1
Escalation of military tensions in the Middle East (Iran-US aircraft carrier clash)
→
Step 2
Demand for supply chain impact analysis based on geopolitical risk
→
Step 3
Automatic alerts for geopolitical risk supply chain impact for small and medium-sized export companies
Problem
Purchasing and logistics managers at small and medium-sized export companies with annual revenue of 1-10 billion KRW (approx. $750,000-$7.5 million) take an average of 1-2 days to assess the impact on their supply chain when geopolitical events such as Middle East conflicts, navigation restrictions, or sanction changes occur. They see news about oil price and freight rate surges during Hormuz Strait tensions, but cannot immediately determine 'how many days of delay are expected for our raw material deliveries' or 'what is the freight rate difference for alternative routes,' leading to delayed proactive responses.
Solution
A SaaS that automatically calculates the impact by matching geopolitical events with a company's import items, routes, and partner profiles, and sends Slack/KakaoTalk alerts. (1) Automatic detection of geopolitical events (crawling news, social media, and shipping tracking data), (2) impact scoring based on company profile (import items, major routes, partner countries), (3) automatic generation of alternative route and freight rate fluctuation prediction reports.
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 (66%)
Data Availability
17.1/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 (60/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]
Data Pipeline [medium]
AI/ML [low]