B
Appearance Fee Settlement Assistant
3.20
Derivation Chain
Step 1
Celebrity broadcast appearances & post-retirement activity trend
→
Step 2
Settlement & contract management demand between talent and production companies
→
Step 3
Appearance fee settlement & Tax Accounting automation SaaS for Freelancer broadcasters/creators
Problem
Freelancer broadcasters, YouTubers, and podcasters who hold simultaneous appearance contracts with multiple production companies/platforms face payment timelines varying from 30–90 days post-filming, with different withholding tax (3.3%) and VAT treatments per engagement—spending 3–5 hours monthly tracking settlements. It's common to discover unreported income during year-end tax filing, resulting in penalty surcharges.
Solution
When appearance contracts are registered, the system auto-generates a calendar of expected payment dates and tax treatment methods, then matches them against bank deposit records to automatically detect unsettled invoices. Provides comprehensive income tax estimation simulations and expense deduction guides.
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 (68%)
Data Availability
18.3/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 (52/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]
Data Pipeline [low]