Subsidy Settlement Automation SaaS

2.90

Derivation Chain

Step 1 Public subsidy policy controversy

→

Step 2 Surge in municipal subsidy disbursement & settlement workload

→

Step 3 Automated settlement document verification & Report generation

Problem

As municipalities rapidly create new cash-equivalent subsidies every election season, local government finance officers face enormous workloads for recipient eligibility verification, duplicate benefit prevention, and disbursement performance reporting. Each program requires an average of 2-3 staff members spending 3-4 weeks on manual Excel-based settlement, with constant audit risk from the Board of Audit and Inspection.

Solution

Integrates with the municipal finance system (e-Hojo) disbursement data to provide automated cross-verification of recipient eligibility (against National Tax Service, health insurance, and resident registration records), duplicate benefit detection, and automatic generation of disbursement performance Reports. Audit-ready evidence materials are automatically archived with timestamps.

Target: Welfare policy and finance division officials at 226 municipal governments, especially mid-sized cities with populations of 100,000-500,000

Revenue Model: B2G SaaS annual contract ~$9,000-$27,000/municipality (12-36 million KRW, 3 tiers by population size). Initial implementation consulting billed separately.

Ecosystem Role: Infrastructure

MVP Estimate: 2_weeks

NUMR-V Scores

N Novelty

3.0/5

U Urgency

3.0/5

M Market

3.0/5

R Realizability

2.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 (70%)

Tech Complexity

29.3/40

Data Availability

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

Competition

8.0/20

Market Demand

9.4/20

Timing

16.0/20

Revenue Signals

10.5/15

Pick-Axe Fit

12.0/15

Solo Buildability

3.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 [low]

Dashboard