B
Policy Benefit Eligibility Change Tracking Service
4.00
Derivation Chain
Step 1
Mass issuance of government policy briefings
→
Step 2
Eligibility changes due to policy updates
→
Step 3
Tracking the impact of eligibility changes on my welfare benefits
Problem
A late-50s office worker faces frequent changes in eligibility for government benefits due to monthly policy updates (health insurance premium criteria, employment support eligibility, pension-related schemes, etc.). To check eligibility, they must visit 6-7 different ministry websites and review individual conditions, spending 2-3 hours per month while still missing out on benefits. In particular, changes in income brackets and asset criteria are not automatically reflected, leading to missed benefits worth 500,000 to 2,000,000 KRW (approximately $375–$1,500) annually.
Solution
On the web, users input age, income bracket, asset size, and family composition, and the service automatically extracts and displays items among recently changed government policies that affect their benefit eligibility. Key features: (1) automatic crawling of policy changes and parsing of eligibility conditions, (2) profile-based eligibility change matching and notifications, (3) a change history timeline that retroactively identifies missed benefits.
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. |
N=.15 U=.20 M=.15 R=.30 V=.20
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 (61/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
Backend [medium]
Frontend [low]
Data Pipeline [medium]