A
Ticket Scam Detection Alert Bot
3.65
Derivation Chain
Step 1
BTS Gwanghwamun concert proxy booking fraud
→
Step 2
Major concert ticket trading platforms
→
Step 3
Automated ticket transaction fraud detection service
Problem
Ticket fraud — including proxy bookings and counterfeit ticket sales — is surging around major concerts like BTS, yet individual buyers have no way to distinguish scam listings from legitimate ones on secondhand platforms (Bungaejangter, Karrot, etc.). With average ticket prices of ~$75–225 (100,000–300,000 KRW), victims lose not only money but also the chance to attend the show, causing significant emotional distress. Police monitor after the fact, but real-time prevention is nonexistent.
Solution
Real-time crawling of ticket listings on secondhand trading platforms to detect fraud patterns (blacklisted bank accounts, price anomalies, new accounts, repeated similar phrasing), delivering risk alerts like 'This listing has an 87% scam probability' via KakaoTalk/Telegram bot. Combines community report data to build a proprietary fraud database.
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 (72%)
Data Availability
23.1/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 (50/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
Backend [medium]
AI/ML [medium]
Frontend [low]