B
Tax Relief Self-Guide
3.60
Derivation Chain
Step 1
Digital government services delegation
→
Step 2
Giving up on complex reduction/appeal procedures
→
Step 3
Step-by-step screenshot guide for each reduction type + automatic document assembly
Problem
People in their 50s–60s know how to use government tax and benefits portals, but the process for claiming 'apply-to-receive' benefits — property tax reductions, health insurance premium adjustments, National Pension catch-up contributions, etc. — involves 5–10 complex steps. They either pay a Tax Accounting professional $75–225 per case or simply give up. In reality, most of these can be done independently with just screenshot-based instructions. An estimated 30%+ of households in their 50s miss $375–1,500 in annual relief benefits.
Solution
Users enter their situation (age, income bracket, assets, family composition), and the system automatically scans for eligible reductions and benefits. For each item, it provides step-by-step guides with actual portal screenshots showing exactly where to click and what to enter. Required documents and issuance links are organized on a single screen, with deadline reminders.
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 (64%)
Data Availability
20.4/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 (57/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 [medium]