A

Ticket War Alert Bot

3.90

Derivation Chain

Step 1 Intensifying Ticketlink ticketing competition
→
Step 2 Ticketing proxy/macro demand
→
Step 3 Ticket release schedule & seat availability real-time alerts

Problem

K-POP and musical fans miss ticket release times or don't notice when cancellation seats become available, causing them to miss desired performances. Popular show tickets typically sell out within 30 seconds to 2 minutes of release. Office workers and students can't be on standby at release time, forcing them to pay 2-5x markup to resellers.

Solution

Automatically aggregates ticket release schedules from major platforms (Ticketlink, Interpark, YES24). When users register interest in a show, the system sends KakaoTalk/push notifications 10 minutes before release. After sellout, real-time cancellation seat alerts are provided, along with seat grade price comparison to support optimal purchasing.

Target: Ages 20-30, K-POP and musical fans, office workers who attend 1+ performances per month
Revenue Model: Premium Subscription $3/month per account (Free: 3 show alerts/month; Premium: unlimited + cancellation seat alerts); 20% discount on Annual Subscription
Ecosystem Role: Infrastructure
MVP Estimate: 2_weeks

NUMR-V Scores

N Novelty
2.0/5
U Urgency
5.0/5
M Market
4.0/5
R Realizability
4.0/5
V Validation
4.0/5
NUMR-V Scoring System
N Novelty1-5How uncommon the service is in market context.
U Urgency1-5How urgently users need this problem solved now.
M Market1-5Market size and growth potential from proxy indicators.
R Realizability1-5Buildability for a small team with realistic constraints.
V Validation1-5Validation signal quality from competition and demand data.
Each dimension is scored 1-5 and weighted into grade S/A/B/C/D.
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
34.7/40
Data Availability
17.5/25
MVP Timeline
20.0/20
API Bonus
0.0/15
Feasibility Breakdown
Tech Complexity/ 40Difficulty of core implementation stack.
Data Availability/ 25Practical availability and cost of required data.
MVP Timeline/ 20Expected time to ship a usable MVP.
API Bonus/ 15Bonus for viable public API leverage.
Total 100 points; below 50% is filtered out.

Market Validation (57/100)

Competition
8.0/20
Market Demand
6.2/20
Timing
14.0/20
Revenue Signals
10.5/15
Pick-Axe Fit
10.5/15
Solo Buildability
8.0/10
Validation Breakdown
Competition/ 20Signal quality from competitor landscape.
Market Demand/ 20Demand proxies from search and mention patterns.
Timing/ 20Fit with current shifts in tech, behavior, and regulation.
Revenue Signals/ 15Reference evidence for monetization viability.
Pick-Axe Fit/ 15How well the concept serves participants in a trend.
Solo Buildability/ 10Practicality for lean-team implementation.
Total 100 points; below 50 is filtered out.

Technical Requirements

Backend [medium] Infrastructure [low] Frontend [low]
Dashboard