K-Pop Reunion Merch Drop Alert

3.15

Derivation Chain

Step 1 Idol group reunion trend

→

Step 2 Fandom consumption infrastructure

→

Step 3 Limited-edition merch drop integrated alert & auto-purchase service

Problem

K-pop fans (ages 20-30) trying to purchase limited-edition merchandise and tickets from reunion/comeback groups must constantly check 5+ platforms including Weverse, Interpark, YES24, and official fan cafes. While release announcements spread across social media within minutes, over 60% of working fans experience sellouts due to delayed awareness.

Solution

Subscribe to artists → automatic monitoring of official channels and commerce platforms → instant KakaoTalk/push notification on merch and ticket drops → price and platform comparison → one-click purchase link. Integrated reunion/comeback schedule calendar. Duplicate purchase prevention feature.

Target: Working K-pop fans ages 20-30, fandom community managers

Revenue Model: Premium Subscription at KRW 2,900 (~$2.20)/month per account (5 artist groups, instant alerts). Free plan (1 group, 1-hour delayed alerts). Commerce affiliate commission 1-3%.

Ecosystem Role: Infrastructure

MVP Estimate: 2_weeks

NUMR-V Scores

N Novelty

3.0/5

U Urgency

3.0/5

M Market

4.0/5

R Realizability

3.0/5

V Validation

3.0/5

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 (72%)

Tech Complexity

29.3/40

Data Availability

22.5/25

MVP Timeline

20.0/20

API Bonus

0.0/15

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 (54/100)

Competition

8.0/20

Market Demand

6.2/20

Timing

14.0/20

Revenue Signals

7.5/15

Pick-Axe Fit

10.5/15

Solo Buildability

8.0/10

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]

Dashboard