S
Solo Business Tax Code Simulator
4.30
Derivation Chain
Step 1
Career-based Solo Entrepreneur tax & business registration onboarding
→
Step 2
Tax differences based on business category code selection
Problem
When registering as a Freelancer or consultant after retirement, the chosen business category code determines simplified tax eligibility, VAT rates, and expense ratios (standard vs. simplified). The same 'consulting' work can result in $750–$2,250 in annual tax differences depending on the category code. However, there are over 1,000 category codes and the National Tax Service search tool is notoriously unfriendly, so retirees either pay a tax accountant $82+/month or choose a code by guesswork.
Solution
Users describe their career and work activities in natural language. The tool recommends 3–5 suitable business category codes and shows a comparison table for each code covering VAT (simplified vs. standard taxpayer), comprehensive income tax (simplified vs. standard expense ratio), and health insurance premium impact across estimated revenue brackets. It clearly shows 'if you register under this category code, your annual taxes will be X.'
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 (78%)
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 (61/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 [low]
Backend [medium]
Data Pipeline [low]