A

GigSettle

4.20

Derivation Chain

Step 1 Trot/audition broadcast trend
→
Step 2 Trot concert industry Infrastructure
→
Step 3 Concert revenue settlement automation SaaS

Problem

Small trot regional concert production companies (1-5 people) manually settle 10-20 line items per show—ticket revenue, sponsor fees, performer fees, equipment rentals, transportation—using spreadsheets. At 4-8 shows per month, settlement alone takes 5-8 hours weekly, and calculation errors in performer/staff payouts cause 2-3 disputes per year. Complexity spikes sharply for joint concerts with multiple performers.

Solution

A SaaS that takes show revenue and expense inputs, automatically calculates per-performer and per-staff payouts, and computes net amounts after tax deductions. Features include contract-based auto-applied split ratios, KakaoPay/Toss payment integration, and a per-show P&L analysis dashboard.

Target: Trot/traditional music regional concert production companies (1-5 people), Freelancer event planners, cultural center/festival performance coordinators
Revenue Model: SaaS monthly flat rate $29.25/account (39K KRW, up to 10 shows/month), Premium $74.25/month (99K KRW, unlimited + payment integration). Pay-per-use option at $1.43/show (1,900 KRW)
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
5.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.
SaaS N=.15 U=.20 M=.15 R=.30 V=.20 Senior N=.25 U=.25 M=.05 R=.30 V=.15

Feasibility (74%)

Tech Complexity
34.7/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 (59/100)

Competition
8.0/20
Market Demand
6.2/20
Timing
14.0/20
Revenue Signals
10.5/15
Pick-Axe Fit
10.5/15
Solo Buildability
10.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 [low] Frontend [medium] Infrastructure [low]
Dashboard