Public Relief Fund Claim Rate Dashboard

3.20

Derivation Chain

Step 1 Expansion of public relief fund disbursements

→

Step 2 Growing demand for efficient fund execution by local governments

→

Step 3 Claim rate & non-claim analysis dashboard for municipal staff

Problem

When 226 local governments nationwide distribute public relief funds (100,000–300,000 KRW (~$75–$225) per person), claim rates stall at 95–98%, and staff spend over 20 hours per week manually calling and texting the 2–5% of unclaimed residents. Without a dedicated analysis tool to identify non-claim causes (elderly residents, address mismatches, unregistered bank accounts), municipalities repeatedly miss claim rate targets just before deadlines.

Solution

Integrates with municipal relief fund disbursement systems to provide a real-time dashboard segmented by district, age group, and non-claim reason. Automatically generates targeted outreach messages per unclaimed segment. Recommends optimal contact channels (SMS/mail/in-person visit) by non-claim reason, with automated alerts at D-7, D-3, and D-1 before deadlines.

Target: Welfare or economic policy officers at city/county/district offices serving populations of 50,000–300,000

Revenue Model: SaaS Monthly Subscription at 190,000 KRW (~$142)/month per municipality per program. Additional programs at 90,000 KRW (~$67)/month each. Annual contracts include 2 months free.

Ecosystem Role: Supplier

MVP Estimate: 2_weeks

NUMR-V Scores

N Novelty

3.0/5

U Urgency

4.0/5

M Market

3.0/5

R Realizability

3.0/5

V Validation

3.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 (53/100)

Competition

8.0/20

Market Demand

6.2/20

Timing

16.0/20

Revenue Signals

9.0/15

Pick-Axe Fit

9.0/15

Solo Buildability

5.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] AI/ML [low]

Dashboard