B
K-Football Player Stats Widget
3.40
Derivation Chain
Step 1
Oh Hyeon-gyu's consecutive goals at Beşiktaş go viral
→
Step 2
Growing fandom around Korean football players abroad
→
Step 3
Real-time player stats embed widget for fan communities/media
Problem
As more Korean football players move abroad (Oh Hyeon-gyu, Kim Min-jae, Lee Kang-in, etc.), sports media creators (YouTubers, bloggers, fan community admins) want to embed up-to-date match statistics (goals, assists, heatmaps, ratings) into their articles and videos, but manually capturing and formatting data takes 30–60 minutes per match. Official stats sites either lack embed functionality or require expensive licenses (millions of KRW/~thousands of USD per year).
Solution
Collects Korean player data in real-time from football statistics APIs (football-data.org, API-Football) and provides customizable embeddable widgets via iframe for blogs, YouTube, and fan communities. Includes player season stats cards, per-match highlight stats, and league ranking comparison widgets.
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 (67%)
Data Availability
17.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 (51/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 [medium]
Infrastructure [low]