B
EV Subsidy Eligibility Checker
3.50
Derivation Chain
Step 1
Tesla European registration decline / BEV market growth
→
Step 2
Expansion of EV purchase incentive policies
→
Step 3
Increasing subsidy policy complexity
→
Step 4
Automated subsidy eligibility determination
Problem
Korean EV subsidies vary by central government, local government, and manufacturer based on conditions like vehicle model, price, residence, and personal vs. business use — and they change annually. To determine their exact subsidy amount, consumers must cross-reference the Ministry of Environment website, local government announcements, and dealer inquiries, spending an average of 3–5 hours. Tens of thousands of cases per year miss subsidies entirely because they fail to act before local budgets are exhausted.
Solution
A web service where users input vehicle model, residence, intended use, and income to automatically calculate combined national and local subsidies. It tracks each municipality's remaining budget and projected exhaustion date in real time, recommending optimal application timing. Alerts are sent when remaining budget drops below 20%.
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 (50/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]