A
Solo Biz Regulatory Change Alert
4.30
Derivation Chain
Step 1
Solo Entrepreneur Tax Accounting & Labor automation
→
Step 2
Existing Tax Accounting SaaS lacks mid-senior context
→
Step 3
No channel to receive advance alerts on how Regulation changes impact 'my business'
Problem
A 58-year-old Solo Entrepreneur running a consulting practice after retirement must manually track annual changes to VAT simplified taxation thresholds, income tax deduction items, social insurance coverage rules, and employment subsidy eligibility. Announcements are scattered across the National Tax Service, Ministry of Employment, and National Health Insurance Service, with no contextual filtering for 'does this change apply to my revenue size and industry?' — leading to repeated missed deadlines, penalty taxes, and lost subsidies.
Solution
Users register their business type, revenue range, and years in operation on the web. When relevant Tax Accounting, Labor, or subsidy Regulation changes occur, the system filters for 'only what applies to my business' and sends alerts. Each change is summarized in three lines: what changed, what action is needed, and the deadline.
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 (72%)
Data Availability
23.1/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 (58/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
Data Pipeline [medium]
Backend [medium]
Frontend [low]