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.
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
22.1/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
Data Pipeline [medium]
Backend [medium]
Frontend [low]