Proxy Booking Detection Shield

3.05

Derivation Chain

Step 1 BTS Gwanghwamun concert proxy booking controversy

→

Step 2 Concert ticketing platform operators

→

Step 3 Proxy booking/macro detection module

Problem

During major concert ticket releases (e.g., BTS Gwanghwamun), proxy booking agents and macro bots seize seats, blocking legitimate buyers. Ticketing platform operators (Interpark, Melon Ticket, etc.) lack the resources to develop in-house bot detection, incurring tens of thousands of dollars in CS surge and brand damage response costs per event.

Solution

An SDK embedded in ticketing pages that analyzes click patterns, session speed, and device fingerprints in real time to flag and block suspected bot/proxy booking sessions via API. A dashboard displays detection rates, false positive rates, and block logs, with pre-event risk score calculation. Core features: (1) Real-time bot/proxy detection via behavioral analysis, (2) Block API with configurable thresholds, (3) Per-event risk scoring and post-event analytics.

Target: Small-to-mid-size online ticketing platform operators (5-30 employees), concert promoter IT/operations teams

Revenue Model: SaaS Monthly Subscription base ~$217/domain (290,000 KRW) + excess event traffic at ~$0.004/request (5 KRW), 15% discount for Annual Subscription.

Ecosystem Role: Infrastructure

MVP Estimate: 2_weeks

NUMR-V Scores

N Novelty

3.0/5

U Urgency

4.0/5

M Market

4.0/5

R Realizability

2.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 (69%)

Tech Complexity

29.3/40

Data Availability

19.4/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 (52/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

3.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

Backend [medium] Frontend [low] Data Pipeline [medium]

Dashboard