Public Subsidy Eligibility Simulator

3.85

Derivation Chain

Step 1 Public subsidy policy controversy

→

Step 2 Confusion over municipality-specific subsidy eligibility

Problem

With the proliferation of central and local government public subsidies, residents struggle to identify which benefits they qualify for. They must check Government24, Bokjiro (welfare portal), and individual municipal websites separately, each with different criteria for income level, household composition, age, and industry. People spend an average of 2-3 hours and still frequently miss eligible programs. Newly created subsidies during election seasons have particularly low awareness, with application rates reaching only 30-40%.

Solution

Users input basic information (address, age, income bracket, household composition, industry) and the system automatically matches cash-equivalent subsidies across the central government + 17 metropolitan + 226 municipal governments, simulating estimated benefit amounts. It provides application deadline notifications, required document checklists, and direct links to Government24/Bokjiro for one-stop access.

Target: Household heads with annual income under ~$37,500 (50 million KRW), ages 30-60, especially Small Business Owners, Freelancers, and non-regular workers with high probability of qualifying for multiple subsidies

Revenue Model: Free basic search + Premium ~$2.20/month (2,900 KRW) for deadline alerts, automatic document checklists, and personalized Reports. B2G municipal contracts ~$2,250/month per municipality (3 million KRW) for resident service outsourcing.

Ecosystem Role: Consumer

MVP Estimate: 2_weeks

NUMR-V Scores

N Novelty

2.0/5

U Urgency

4.0/5

M Market

5.0/5

R Realizability

4.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.8/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

6.2/20

Timing

16.0/20

Revenue Signals

10.5/15

Pick-Axe Fit

10.5/15

Solo Buildability

8.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 [low] Data Pipeline [medium]

Dashboard