B
Tax Law Change Asset Impact Alert
3.00
Derivation Chain
Step 1
Real Estate/inheritance simulation
→
Step 2
Tax laws that change every year
→
Step 3
Auto-calculating and alerting how tax law changes impact my assets
Problem
A 58-year-old owner of two properties faces annual changes in capital gains tax, comprehensive real estate tax, and inheritance tax laws, but determining which changes actually affect their situation requires a Tax Accounting consultation costing 100,000–300,000 KRW (~$75–225) per session. Reading tax reform news doesn't help them judge 'does this apply to me?' — leading to unnecessary anxiety, or worse, missing critical changes that result in millions of won in tax differences.
Solution
Users register their number of properties, acquisition dates, approximate market values, and family composition (spouse, number of children) on the web. When tax laws change, the system auto-generates a summary of 'how this change impacts your situation' and sends it via email. Example: '2026 capital gains tax long-term holding special deduction change → estimated 3.5 million KRW (~$2,625) tax increase if you sell Apartment A.'
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 (52%)
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 (54/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 [high]
Data Pipeline [medium]