B
Sports Data Analysis Sandbox
3.50
Derivation Chain
Step 1
Growing interest in professional baseball sabermetrics
→
Step 2
Demand for introductory baseball data analysis Education
→
Step 3
Sports data analysis practice Platform for non-specialists
Problem
When baseball fans interested in sabermetrics — non-specialists like college students and office workers — try to learn data analysis, existing Education Platforms focus on marketing and finance datasets, with few sports datasets or analysis examples available. There's no curriculum that teaches programming fundamentals and baseball data analysis simultaneously, wasting 2–3 months on self-study trial and error.
Solution
An interactive coding lab built on historical KBO (Korean Baseball Organization) record datasets, guiding learners step-by-step from Python data analysis basics to calculating sabermetrics indicators (WAR, OPS+, FIP, etc.). With in-browser code execution, instant visualization, and an AI hint system, even non-specialists can produce their own analysis Report within 4 weeks.
NUMR-V Scores
NUMR-V Scoring System
| N Novelty | 1-5 | How uncommon the service is in market context. |
| U Urgency | 1-5 | How urgently users need this problem solved now. |
| M Market | 1-5 | Market size and growth potential from proxy indicators. |
| R Realizability | 1-5 | Buildability for a small team with realistic constraints. |
| V Validation | 1-5 | Validation 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 (77%)
Data Availability
22.5/25
Feasibility Breakdown
| Tech Complexity | / 40 | Difficulty of core implementation stack. |
| Data Availability | / 25 | Practical availability and cost of required data. |
| MVP Timeline | / 20 | Expected time to ship a usable MVP. |
| API Bonus | / 15 | Bonus for viable public API leverage. |
Market Validation (56/100)
Validation Breakdown
| Competition | / 20 | Signal quality from competitor landscape. |
| Market Demand | / 20 | Demand proxies from search and mention patterns. |
| Timing | / 20 | Fit with current shifts in tech, behavior, and regulation. |
| Revenue Signals | / 15 | Reference evidence for monetization viability. |
| Pick-Axe Fit | / 15 | How well the concept serves participants in a trend. |
| Solo Buildability | / 10 | Practicality for lean-team implementation. |
Technical Requirements
Frontend [medium]
Backend [low]
AI/ML [low]