B

Fandom Commerce Dashboard

3.55

Derivation Chain

Step 1 Pro baseball fandom spending expansion
→
Step 2 Fan merchandise & F&B sales channel diversification
→
Step 3 Sales analytics tool for fan-targeting E-commerce sellers
→
Step 4 Fandom trend intelligence for sellers

Problem

Sports fan merchandise sellers (on platforms like Naver SmartStore and Idus) rely on intuition to determine which player-, team-, or event-related products sell well. They only realize demand shifts from mid-season events—popular player changes, trades, record milestones—after the fact, causing trending product launches to lag by 1–2 weeks and missing $375–$1,500 (~50–200만원) in monthly sales opportunities.

Solution

Collects social media buzz volume, community mention frequency, and search trends in real time to calculate a 'fandom heat index' per player, team, and event. Provides surge keyword alerts, trending product planning recommendations, and competitive seller new-listing monitoring in a unified dashboard.

Target: Sports fan merchandise sellers (on SmartStore/Idus with $750–$15,000 monthly revenue), solo sellers to small teams (3 or fewer)
Revenue Model: SaaS monthly flat rate at $29/mo (~39,000 KRW) for 3 teams tracked, Pro at $59/mo (~79,000 KRW) for all teams + unlimited alerts. 20% discount for annual billing
Ecosystem Role: Supplier
MVP Estimate: 2_weeks

NUMR-V Scores

N Novelty
3.0/5
U Urgency
4.0/5
M Market
4.0/5
R Realizability
3.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 (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 (56/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
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 [medium] Frontend [low]
Dashboard