A
Trot Fandom Commerce Builder
3.70
Derivation Chain
Step 1
Trot audition show popularity
→
Step 2
Trot fandom-based merchandise/performance commerce
Problem
The popularity of trot audition shows like 'Current Singers' has fueled rapid fandom growth among the 40-60 age demographic, but this group is unfamiliar with existing K-pop fandom platforms (Weverse, Bubble). They rely on fan cafes (Daum Cafe) to manually coordinate group purchases of merchandise, support wreaths, and fan meeting attendance, leading to frequent settlement errors and fraud. Fan cafe admins spend 20-30 hours per month on settlement and shipping management.
Solution
Provide a fandom commerce builder optimized for 40-60 age group UX (large fonts, phone ordering support, bank transfer payments). It handles the full workflow from group purchase creation to payment confirmation, settlement, and delivery tracking in one place, with built-in support wreath and ad group purchase features. Fan cafe board integration enables participation without separate registration.
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
19.4/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 (59/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]