A

Airline Promo Alert Bot

3.70

Derivation Chain

Step 1 LCC route expansion and promotional competition
Step 2 Flight price tracking services
Step 3 Promotion condition-based auto-filtering/alert services

Problem

LCCs like Eastar Jet and T'way release various promotions weekly, but travelers must check each airline's app/website individually. Complex conditions (dates, routes, payment methods) cause frequent misses of actual lowest fares. Working professionals planning 1-2 international trips per month spend an average of 2-3 hours comparing promotions and end up paying 10-30% more due to missed timing.

Solution

Real-time crawling of promotions from 6 domestic LCCs, delivering automatic alerts via KakaoTalk/Telegram only for deals matching the user's preset route/date/budget criteria. The key differentiator is auto-parsing promotion conditions (card discounts, early bird, group rates, etc.) to calculate the true lowest price.

Target: Working professionals aged 25-40 who travel internationally 3+ times per year, especially price-sensitive independent travelers
Revenue Model: Premium Subscription ~$2.20/month per account (Free: 1 route alert, Premium: unlimited routes + real-time alerts + price history), 20% discount for annual billing
Ecosystem Role: Consumer
MVP Estimate: 2_weeks

NUMR-V Scores

N Novelty
2.0/5
U Urgency
4.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.
SaaS N=.15 U=.20 M=.15 R=.30 V=.20 Senior N=.25 U=.25 M=.05 R=.30 V=.15

Feasibility (71%)

Tech Complexity
29.3/40
Data Availability
21.2/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.

Market Validation (70/100)

Competition
10.0/20
Market Demand
20.0/20
Timing
14.0/20
Revenue Signals
10.5/15
Pick-Axe Fit
7.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.

Technical Requirements

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