A
Local Ordinance Change Impact Alert
4.00
Derivation Chain
Step 1
Seo Myeong-ok ethics committee complaint
→
Step 2
Tracking legislative and ordinance changes
→
Step 3
Specific impact of local ordinance changes on daily life
Problem
Small Business Owners in their 50s miss local ordinance changes (parking regulations, business hour restrictions, signage standards, waste sorting rules, etc.) and end up paying fines or suffering business disruptions. While local ordinances are published on the 'Local Law Information System,' thousands of entries are posted and there is no way to filter only those relevant to one's industry or situation. By the time business owners become aware of relevant ordinances, they have usually already taken effect.
Solution
Users register their location, industry, and areas of interest, and the service filters relevant ordinance enactments and amendments from their local government, sending pre-enforcement alerts. Each ordinance change is summarized in 2–3 lines explaining 'how it affects me,' along with guidance on required actions (reporting, modifications, compliance measures).
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 (71%)
Data Availability
21.7/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]
Backend [medium]
Frontend [low]