Parliamentary Speech Monitoring SaaS

3.70

Derivation Chain

Step 1 National Assembly physical altercation and ethics committee complaint issues

→

Step 2 Demand for legislative activity monitoring

→

Step 3 Automated per-legislator speech and behavior tracking service

Problem

Civic organizations, political media outlets, and lobbying consultancies spend 15–20 hours per week manually tracking plenary and committee speeches, disciplinary actions, and ethics committee complaints across 300 National Assembly members. Assembly transcript PDFs are unstructured, making keyword search impossible, and it takes an average of 2–3 days to establish context from past statements when an issue breaks.

Solution

Combines the National Assembly transcript API with news crawling to automatically collect and organize each legislator's speeches, disciplinary records, and ethics committee complaint history. Provides keyword alerts and legislator profile dashboards. Differentiates with instant timeline generation of a legislator's past statements when a specific issue (e.g., assault, protest banners) occurs.

Target: Political newsletter operators, civic organization policy officers (20–50 person organizations), National Assembly press corps journalists

Revenue Model: SaaS Monthly Subscription at $37/account/month (49,000 KRW), includes 10 alert keywords. Additional 10 keywords for $7.50 (10,000 KRW). 20% discount for Annual Subscription.

Ecosystem Role: Infrastructure

MVP Estimate: 2_weeks

NUMR-V Scores

N Novelty

3.0/5

U Urgency

4.0/5

M Market

3.0/5

R Realizability

4.0/5

V Validation

4.0/5

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 (63%)

Tech Complexity

24.0/40

Data Availability

18.8/25

MVP Timeline

20.0/20

API Bonus

0.0/15

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 (72/100)

Competition

10.0/20

Market Demand

20.0/20

Timing

14.0/20

Revenue Signals

10.5/15

Pick-Axe Fit

10.5/15

Solo Buildability

7.0/10

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]

Dashboard