B
My District Legislator Report Card
3.20
Derivation Chain
Step 1
Seo Myung-ok ethics committee referral
→
Step 2
Difficulty accessing legislator activity information
→
Step 3
At-a-glance view of my district representative's actual performance
Problem
Working professionals in their 50s who want to check their district representative's actual bill sponsorship record, plenary session attendance, and ethics disciplinary history must search across 5+ separate sites including the National Assembly Bill Information System, session minutes, and news outlets, taking over 2 hours. They briefly pay attention during elections but face a 4-year information gap for the rest of the term.
Solution
Select a district or proportional representative to automatically collect and display a monthly report card covering bills sponsored and passage rate, plenary attendance rate, standing committee speaking frequency, ethics committee referrals/disciplinary history, and budget review participation. Includes comparison with the previous term's representative.
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 (62%)
Data Availability
17.9/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 (54/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 [medium]
Data Pipeline [medium]