A
Earned Income Tax Credit (EITC) Amount Preview
4.05
Derivation Chain
Step 1
Surge in interest in EITC applications
→
Step 2
Difficulty for seniors in verifying EITC eligibility
→
Step 3
Checking whether receiving EITC reduces other welfare benefits
Problem
When senior workers aged 55-65 try to apply for the Earned Income Tax Credit (EITC), they need to manually cross-check income and asset requirements on the National Tax Service's HomeTax system to verify eligibility and estimated payout. Additionally, to understand the cascading effects of receiving EITC on Basic Pension, National Pension, and health insurance premiums, they must separately check four different agency websites, taking an average of 3-4 hours. Many seniors give up applying despite being eligible due to the complexity, missing out on up to 3.3 million KRW (approx. $2,475) per year.
Solution
Users input age, number of household members, annual income, and total assets on the web, and the service automatically calculates the estimated EITC payout and simulates on one screen the potential reduction in Basic Pension, changes in health insurance premiums, and impact on comprehensive income tax. It also provides reminder notifications aligned with the March/September application periods and a step-by-step application guide.
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 (70/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
Frontend [medium]
Backend [medium]
Data Pipeline [low]