A
Trade News Risk Alert Bot
3.85
Derivation Chain
Step 1
Increasing volatility in Korea's import/export trade environment
→
Step 2
Risk monitoring for import/export companies
→
Step 3
Automated supply chain risk alerts based on trade news
Problem
Trade team leaders (2-5 person teams) at SME import/export companies with annual revenue of $7.5M-$75M must monitor 10+ trade news sources daily including KITA, Korea Customs Service, and Ministry of Trade. Out of 200-300 daily news items, they miss 2-3 company-relevant risks per month (tariff rate changes, export regulations, FTA shifts, sudden exchange rate fluctuations). Each missed risk results in an average of $3,750-$15,000 in additional costs.
Solution
Real-time crawling of major trade news sources including KITA, Korea Customs Service, Ministry of Trade, and Ministry of Foreign Affairs. Automatically filters company-relevant risks based on user-registered HS codes, countries, and keywords, then sends instant alerts via Slack or KakaoTalk. AI summarizes each news item's impact (tariff rate change magnitude, effective date, affected product categories).
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 (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
Data Pipeline [medium]
AI/ML [medium]
Backend [low]