B

KBO Spring Camp Analytics Report

2.75

Derivation Chain

Step 1 KBO spring training camp news coverage
Step 2 Baseball fandom demand for player data analysis
Step 3 Auto-generation tool for fan/blogger player stat visualization and camp performance Reports

Problem

Baseball bloggers and YouTubers active in KBO fan communities (FM Korea, DC Inside Baseball Gallery, MLB Park) spend 2-3 hours per article manually collecting and organizing data from official KBO records when producing player camp performance and stat analysis content. Content creators who lack design skills are limited to text-heavy content because they must create visualization charts themselves.

Solution

Automatically collects and organizes KBO player record data to generate infographic-style visualization cards. Auto-analyzes season-over-season changes in key metrics like pitching velocity and batting average during camp, and provides images and embed codes ready for sharing on social media and blogs.

Target: KBO fan bloggers, YouTubers, and community contributors aged 20-40 who produce 4+ baseball analysis content pieces per month
Revenue Model: Premium Subscription at 4,900 KRW (~$3.70)/month per account (Free: 3 cards/month, Premium: unlimited + custom design + watermark removal), 2 months Free on annual billing
Ecosystem Role: Consumer
MVP Estimate: 2_weeks

NUMR-V Scores

N Novelty
3.0/5
U Urgency
2.0/5
M Market
2.0/5
R Realizability
4.0/5
V Validation
2.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.
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.

Market Validation (51/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
8.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.

Technical Requirements

Backend [medium] Frontend [medium] Infrastructure [low]
Dashboard