B
Legislative Risk Early Warning Service
3.50
Derivation Chain
Step 1
Accelerating legislative reform including the Judicial Reform Bills
→
Step 2
Growing uncertainty around how legal changes affect business operations
→
Step 3
Automated legislative impact analysis service for corporate legal teams
Problem
Legal teams at SMEs (50-200 employees) spend 5-10 hours per week tracking how proposed bills and judicial system changes affect their business. During major institutional reforms like the Judicial Reform Bills, 20-30 related bills are introduced simultaneously, making tracking impossible. Missed risks expose companies to regulatory violation fines ranging from millions to tens of millions of won (~$3,750-$37,500).
Solution
Collects proposed bills in real-time from the National Assembly's legislative information system, matches them against user-configured industry categories and keywords, and uses an LLM to summarize each bill's potential business impact. Classifies risk as high/medium/low and delivers recommended action items via Slack or email.
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.4/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 (56/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]