B

Populism Watch Newsletter

2.80

Derivation Chain

Step 1 Public subsidy populism controversy
Step 2 Demand for policy monitoring by civic organizations & media fact-checking
Step 3 Automated fiscal impact analysis tool for election pledges

Problem

Ahead of local and general elections, civic organizations, regional media, and policy researchers want to analyze the fiscal sustainability impact of proliferating cash-welfare campaign pledges, but collecting and comparing municipality-level fiscal independence ratios, revenue structures, and existing welfare budget data takes 3-5 days per pledge. During election seasons, dozens of pledges are announced simultaneously, making timely analysis impossible.

Solution

Automatically collects municipal fiscal disclosure data (from Jaejung365) and election pledge texts, then generates a 'Fiscal Impact Scorecard' for each pledge by cross-referencing estimated budget requirements against the municipality's fiscal independence ratio and revenue structure. Distributed via weekly newsletter and real-time alerts.

Target: Policy analysts at civic organizations, fact-check journalists at regional media outlets, researchers at policy institutes (ages 20-40, policy-engaged demographic)
Revenue Model: Free basic newsletter + Pro ~$37/month (49,000 KRW) for full municipality comparisons, raw data downloads, and custom Reports. Media B2B ~$142/month per account (190,000 KRW).
Ecosystem Role: Regulation
MVP Estimate: 2_weeks

NUMR-V Scores

N Novelty
4.0/5
U Urgency
2.0/5
M Market
2.0/5
R Realizability
3.0/5
V Validation
3.0/5
NUMR-V Scoring System
N Novelty1-5How uncommon the service is in market context.
U Urgency1-5How urgently users need this problem solved now.
M Market1-5Market size and growth potential from proxy indicators.
R Realizability1-5Buildability for a small team with realistic constraints.
V Validation1-5Validation 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%)

Tech Complexity
29.3/40
Data Availability
22.1/25
MVP Timeline
20.0/20
API Bonus
0.0/15
Feasibility Breakdown
Tech Complexity/ 40Difficulty of core implementation stack.
Data Availability/ 25Practical availability and cost of required data.
MVP Timeline/ 20Expected time to ship a usable MVP.
API Bonus/ 15Bonus for viable public API leverage.

Market Validation (54/100)

Competition
8.0/20
Market Demand
9.4/20
Timing
14.0/20
Revenue Signals
7.5/15
Pick-Axe Fit
7.5/15
Solo Buildability
8.0/10
Validation Breakdown
Competition/ 20Signal quality from competitor landscape.
Market Demand/ 20Demand proxies from search and mention patterns.
Timing/ 20Fit with current shifts in tech, behavior, and regulation.
Revenue Signals/ 15Reference evidence for monetization viability.
Pick-Axe Fit/ 15How well the concept serves participants in a trend.
Solo Buildability/ 10Practicality for lean-team implementation.

Technical Requirements

Data Pipeline [medium] Backend [medium] Frontend [low]
Dashboard