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.
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 (71%)
Data Availability
21.2/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 (70/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]
Data Pipeline [medium]
Frontend [low]