B

Trot Fandom Data Room

3.00

Derivation Chain

Step 1 Miss Trot Season 4 Audition Trend
→
Step 2 Trot Fandom Community Activation
→
Step 3 Fandom Size & Activity Data Analytics SaaS

Problem

Agencies managing trot singers (1-5 person teams) must manually monitor fan cafes, social media, and music platforms to gauge fandom size, fan age/region demographics, and engagement metrics (voting, streaming, merchandise purchases). A single staff member spends over 5 hours per week yet cannot calculate quantitative fandom growth or churn rates, making data-driven decisions on comeback timing, concert scale, and merchandise production volumes impossible—relying on gut feeling instead.

Solution

Automatically collects daily data from Naver Cafe membership and post counts, YouTube channel subscribers and views, Melon fan counts, and social media follower changes, visualizing them on a per-artist fandom dashboard. Provides fandom growth rate, engagement participation rate, and churn alerts, along with benchmarks against comparable artists.

Target: Management staff at small trot/K-POP agencies (1-5 employees), self-managing emerging trot artists
Revenue Model: 39,000 KRW (~$29)/month per artist, bundle pricing at 29,000 KRW (~$22)/artist/month for 3+ artists. Competitor artist benchmark Report at 10,000 KRW (~$7.50) per report
Ecosystem Role: Supplier
MVP Estimate: 2_weeks

NUMR-V Scores

N Novelty
3.0/5
U Urgency
3.0/5
M Market
3.0/5
R Realizability
3.0/5
V Validation
3.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 (67%)

Tech Complexity
29.3/40
Data Availability
17.5/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 (50/100)

Competition
8.0/20
Market Demand
6.2/20
Timing
14.0/20
Revenue Signals
7.5/15
Pick-Axe Fit
7.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

Data Pipeline [medium] Backend [low] Frontend [medium]
Dashboard