B
K-Football Fan Commerce Hub
2.85
Derivation Chain
Step 1
Korean football players thriving in overseas leagues
→
Step 2
Rising fan content consumption for overseas football
→
Step 3
Fan-based commerce Infrastructure
Problem
Fans of Korean players in overseas leagues—such as Oh Hyeon-gyu (Beşiktaş) and Son Heung-min (Tottenham)—must check match schedules, highlights, and merchandise across separate platforms (Coupang Play, social media, overseas shopping sites). When ordering official goods from abroad, each purchase takes an average of 30+ minutes to research shipping costs, exchange rates, and sizing. The merchandise conversion rate per match among fans in their 20s–30s remains below 2%.
Solution
A unified fan hub organized by Korean player, providing match schedule alerts, real-time stats, and highlight clips in one place, with one-click purchasing of official club merchandise featuring Korean size charts, KRW pricing, and consolidated shipping. Core features: (1) Per-player match calendar + push notifications, (2) Merchandise price comparison + group-buy matching, (3) Fan community polls and prediction games.
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 (69%)
Data Availability
20.0/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]
Data Pipeline [low]