B
Trot Performance Settlement Manager
3.70
Derivation Chain
Step 1
Revitalization of trot performance culture such as 'National Singing Contest'
→
Step 2
Operational tool for local event agencies
→
Step 3
Automated performance settlement and performer fee management service
Problem
With the revival of 'National Singing Contest' and similar shows, the number of trot and pop music performances by local small-scale event agencies (1-3 employees) is surging. However, manually processing performer fees, local government subsidies, sponsor distributions, and ticket revenue settlements in Excel takes 3-5 days per performance, and settlement errors lead to disputes 2-3 times a year. Only the labor cost for settlement per performance wastes 300,000-500,000 KRW (approx. $225-$375).
Solution
(1) Enter income (tickets, sponsors, subsidies) and expenses (performer fees, equipment, venue) items per performance using templates to automatically generate settlement statements for each performer and staff member; (2) automatically calculate withholding tax (3.3%) and integrate with tax invoices; (3) automatically send settlement details to performers via KakaoTalk/SMS. The differentiation is performance-specific settlement templates and withholding tax automation compared to general accounting software.
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 (74%)
Data Availability
19.4/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 (71/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 [low]
Infrastructure [low]