B
50s Freelancer Comprehensive Income Tax Preview
3.30
Derivation Chain
Step 1
Rise in middle-aged freelancers and side hustlers in the AI era
→
Step 2
Unexpected tax shock at first comprehensive income tax filing after freelancer transition
→
Step 3
Lack of tools to pre-simulate tax differences based on expense recognition scope and industry code selection
Problem
People in their 50s who transitioned to freelancing or solo entrepreneurship after retirement are shocked at their first May comprehensive income tax filing — 'Do I really have to pay this much?' Accustomed to withholding as employees, they don't understand how expense ratios and industry codes can cause taxes to differ by 2-3x. Hiring a tax accountant for bookkeeping costs 500,000-1,200,000 KRW (approx. $375-$900) per year, while HomeTax self-filing has a complex interface that frequently leads to missed expense entries and overpayment.
Solution
Users enter expected annual revenue, industry, and major expense items on the web, and the service (1) compares estimated taxes across 4 scenarios — simple expense ratio vs. standard expense ratio vs. simplified books vs. double-entry bookkeeping, (2) presents a checklist of easily missed expense items (communication, vehicle maintenance, education, etc.), and (3) shows the numerical difference between 'tax accountant bookkeeping cost vs. self-filing tax savings' to support rational decision-making.
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 (67%)
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 (56/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
Backend [medium]
Frontend [medium]