A

Game Streamer Tax Auto-Settlement

3.90

Derivation Chain

Step 1 Game streaming expansion
→
Step 2 Game creator revenue diversification
→
Step 3 Creator Tax Accounting/settlement automation

Competitor references

No usable source links are available for this idea. Its signal notes and scores need independent verification.

Problem

Solo creator streamers earning income from games like PUBG receive donations, ad revenue, and sponsorships across 3-5 platforms (AfreecaTV, YouTube, Chzzk), but each platform has different settlement cycles and tax withholding methods, wasting 50-100 hours annually on manual reconciliation. During comprehensive income tax filing, the inability to cross-reference earnings across platforms leads to additional Tax Accounting costs of $750-$1,500 (100-200만원) per year.

Solution

Automatically collects and consolidates settlement data from each streaming platform via API/PDF, providing a monthly revenue dashboard. Calculates 3.3% withholding tax and estimated VAT/income tax payments in real time, generating one-click tax returns during filing season. Differentiator: auto-categorization of gaming-specific expenses (equipment, internet, game purchases).

Target: Game-specialized streamers/BJs with monthly revenue of $750-$7,500 (100-1,000만원), ages 20-30, Solo Entrepreneurs or Freelancers
Revenue Model: SaaS Monthly Subscription $22/account, 20% discount for Annual Subscription. Additional $37 Per Transaction for linked income tax filing service
Ecosystem Role: Infrastructure
MVP Estimate: 2_weeks

NUMR-V Scores

N Novelty
2.0/5
U Urgency
5.0/5
M Market
4.0/5
R Realizability
4.0/5
V Validation
4.0/5
NUMR-V Scoring System
N Novelty1-5How uncommon the service is in market context.
U Urgency1-5How urgently users need this problem solved now.
M Market1-5Market size and growth potential from proxy indicators.
R Realizability1-5Buildability for a small team with realistic constraints.
V Validation1-5Validation signal quality from competition and demand data.
Each dimension is scored 1-5 and weighted into grade S/A/B/C/D.
N=.15 U=.20 M=.15 R=.30 V=.20

Feasibility (69%)

Tech Complexity
29.3/40
Data Availability
19.4/25
MVP Timeline
20.0/20
API Bonus
0.0/15
Feasibility Breakdown
Tech Complexity/ 40Difficulty of core implementation stack.
Data Availability/ 25Practical availability and cost of required data.
MVP Timeline/ 20Expected time to ship a usable MVP.
API Bonus/ 15Bonus for viable public API leverage.
Total 100 points; below 50% is filtered out.

Market Validation (54/100)

Competition
8.0/20
Market Demand
3.8/20
Timing
14.0/20
Revenue Signals
10.5/15
Pick-Axe Fit
10.5/15
Solo Buildability
7.0/10
Validation Breakdown
Competition/ 20Signal quality from competitor landscape.
Market Demand/ 20Demand proxies from search and mention patterns.
Timing/ 20Fit with current shifts in tech, behavior, and regulation.
Revenue Signals/ 15Reference evidence for monetization viability.
Pick-Axe Fit/ 15How well the concept serves participants in a trend.
Solo Buildability/ 10Practicality for lean-team implementation.
Total 100 points; below 50 is filtered out.

Technical Requirements

Backend [medium] Frontend [medium] AI/ML [low]
Dashboard