A
K-POP Comeback Merch Demand Forecaster
3.85
Derivation Chain
Step 1
I.O.I 10th anniversary reunion comeback
→
Step 2
K-POP comeback fandom merch market explosion
→
Step 3
Merch manufacturer demand forecasting tool
Problem
When K-POP groups make comebacks, merch manufacturers (photocards, banners, lightstick accessories, etc.) struggle to predict demand, resulting in repeated overproduction (30-50% inventory loss) or underproduction (missed revenue). Reunion comebacks like I.O.I are especially volatile, making predictions based on existing fandom size data alone unreliable. Small-scale merch creators (solo sellers) spend an average of 5-7 days deliberating production quantities.
Solution
A SaaS that aggregates K-POP group comeback schedules, social media buzz volume, fan community activity, and historical merch sales data to forecast demand by merch category. Core features: (1) Comeback schedule-based demand forecast dashboard, (2) Real-time SNS/fan community buzz tracking, (3) Category-specific (photocards/banners/keyrings, etc.) production quantity recommendations.
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 (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
Data Pipeline [medium]
Backend [medium]
Frontend [low]