B
National Petition Outcome Tracker
3.25
Derivation Chain
Step 1
Seo Myeong-ok ethics committee complaint
→
Step 2
Citizen political participation channels
→
Step 3
Tracking actual legislative impact after participating in national e-petitions
→
Step 4
Monitoring National Assembly review progress for petitions I've supported
Problem
Citizens in their 50s who signed a national e-petition have no way to find out how it is actually handled after reaching the 50,000-signature threshold. The petition site only shows the signature count, while tracking whether the petition was referred to the relevant standing committee, reviewed, or discarded requires separate research. The repeated sense of futility — 'I signed and nothing happened' — erodes motivation for civic participation.
Solution
Manage a list of petitions you've supported and automatically track each petition's National Assembly processing status (committee referral, review, incorporation into legislation, or dismissal) with progress notifications. It also provides historical outcome statistics for petitions on similar topics, enabling users to gauge effectiveness in advance.
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 (50/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 [low]
Data Pipeline [medium]