B

Local Government Press Release Performance Tracking

4.20

Derivation Chain

Step 1 Strengthening digital PR for local governments
→
Step 2 Diversification of press release distribution channels
→
Step 3 Automatic measurement of actual press performance (publication rate, reach) per press release

Problem

Public relations officers at 226 basic local governments nationwide distribute 300-500 press releases annually, but manually search Naver News to verify actual media coverage, spending 30 minutes per release and over 200 hours per year. Without performance measurement, effective PR strategy development is impossible.

Solution

Automatically crawl major media outlets and portals at 24/48/72 hours after distribution to provide publication rate and estimated reach on a dashboard. Accumulate journalist-specific publication history to recommend target journalists for press releases and support automatic generation of monthly PR performance reports.

Target: Public relations officers at basic local governments (grades 6-9), and spokesperson offices of metropolitan governments
Revenue Model: SaaS monthly subscription: 49,000 KRW (approximately $37) per institution (up to 50 press releases per month), additional releases 500 KRW (approximately $0.38) per transaction. 2 months free with annual contract.
Ecosystem Role: Infrastructure
MVP Estimate: 2_weeks

NUMR-V Scores

N Novelty
4.0/5
U Urgency
5.0/5
M Market
4.0/5
R Realizability
4.0/5
V Validation
4.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.
Each dimension is scored 1-5 and weighted into grade S/A/B/C/D.
N=.15 U=.20 M=.15 R=.30 V=.20

Feasibility (76%)

Tech Complexity
34.7/40
Data Availability
20.8/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.
Total 100 points; below 50% is filtered out.

Market Validation (59/100)

Competition
8.0/20
Market Demand
9.4/20
Timing
14.0/20
Revenue Signals
10.5/15
Pick-Axe Fit
10.5/15
Solo Buildability
7.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.
Total 100 points; below 50 is filtered out.

Technical Requirements

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