B
Subsidy Eligibility Pre-Screener
3.50
Derivation Chain
Step 1
Livelihood subsidy policy expansion
→
Step 2
Subsidy application brokerage by municipality
→
Step 3
Automated pre-screening of subsidy eligibility before application
Problem
Small Business Owners with annual revenue under ~$225,000 and Freelancers trying to compare eligibility requirements across livelihood subsidies and small business support programs announced separately by central government, metropolitan, and municipal authorities spend an average of 3-5 hours per application. Misinterpreting requirements leads to ineligible applications or missed eligible subsidies in roughly 20-30% of all applicants. This results in losing ~$375-$2,250 in annual subsidies per person, or wasting an additional 2-3 hours on resubmission after rejection.
Solution
A SaaS that auto-matches currently available subsidies when users input their business registration number, income information, and region, and predicts eligibility probability for each subsidy. (1) Crawls public data portal subsidy announcements + LLM-based structured parsing of eligibility requirements, (2) Automatic eligibility determination against user profile, (3) Application document checklist and deadline alerts.
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 (68%)
Data Availability
18.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 (56/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]
AI/ML [medium]
Frontend [low]