B
Youth Subsidy Eligibility Checker
3.80
Derivation Chain
Step 1
Expansion of youth employment support policies
→
Step 2
Aggregation of youth support program information
→
Step 3
Automated eligibility assessment engine for support programs
Problem
Over 200 youth support programs are operated annually by local and central government agencies across South Korea, but each program has different eligibility criteria (age, income, residence, employment status), causing young job seekers to spend an average of 8-12 hours finding programs they qualify for. It is common to miss application deadlines and lose out on $375-$1,500 (50-200만원) in subsidies per year.
Solution
Users enter their profile once (age, residence, income level, employment status, education), and the system automatically filters eligible youth support programs across central, metropolitan, and local governments, sorting by deadline and sending notifications. It provides a one-click application document checklist and direct application links for each program.
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 (70%)
Data Availability
20.8/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 (53/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]