B

OTT Original IP Fandom Thermometer

2.70

Derivation Chain

Step 1 K-OTT content hits (e.g., The Man Living with the King, Weak Hero)
→
Step 2 OTT content planning and investment decision-making
→
Step 3 Real-time source IP fandom size and temperature tracking dashboard

Problem

Small OTT content production companies (5 or fewer staff) rely on gut feeling when selecting source material (web novels/webtoons) for drama adaptation because they cannot quantitatively assess fandom size and engagement. With fan communities scattered across platforms (Naver Series, KakaoPage, Ridi, DC Inside, Twitter/X), manual research takes 8-16 hours per title.

Solution

Enter a source title to automatically collect multi-Platform fandom data and calculate a Fandom Temperature Index (size × activity × growth rate). Features: (1) Automated aggregation of comments, reviews, and fan works across platforms, (2) Fandom growth trend graphs, (3) Benchmarking against comparable hit titles.

Target: PDs at OTT content production companies with 5 or fewer staff, web novel and webtoon IP investment analysts
Revenue Model: SaaS Monthly Subscription $60/mo (20 title analyses/month). Additional analysis $3.75 per title. Production company Plan $143/mo (unlimited).
Ecosystem Role: Infrastructure
MVP Estimate: 2_weeks

NUMR-V Scores

N Novelty
3.0/5
U Urgency
3.0/5
M Market
3.0/5
R Realizability
2.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 (71%)

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

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