B

Inbound Tourism Real-Time Demand Board

2.70

Derivation Chain

Step 1 30 million foreign tourists policy era
Step 2 Tourism data-driven business opportunity discovery

Problem

With the goal of attracting 30 million foreign tourists, regional tourist spots, accommodations, and restaurants want to boost marketing, but they cannot access real-time data on which nationalities are arriving when and where. Korea Tourism Organization statistics are delayed by 2-3 months, and Small Business Owners lack the capability to analyze data themselves, causing them to miss optimal marketing timing.

Solution

Aggregates flight booking trends (Skyscanner/Google Flights crawling), social media hashtag trends (Instagram/Xiaohongshu), and Naver/Google Maps tourist attraction search volumes to calculate a weekly 'Nationality × Region Inbound Demand Index.' Provides foreign visitor inflow predictions within a 5km radius of your business and marketing timing alerts.

Target: Accommodation, restaurant, and experience business owners in tourist zones and regional destinations (annual revenue $75K-$750K), local government tourism department officers
Revenue Model: SaaS Monthly Subscription: $29/mo (1 region, weekly Report), Pro $67/mo (nationwide + daily Report + alerts).
Ecosystem Role: Consumer
MVP Estimate: 2_weeks

NUMR-V Scores

N Novelty
2.0/5
U Urgency
3.0/5
M Market
4.0/5
R Realizability
2.0/5
V Validation
3.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 (73%)

Tech Complexity
34.7/40
Data Availability
18.8/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 (56/100)

Competition
8.0/20
Market Demand
9.4/20
Timing
18.0/20
Revenue Signals
7.5/15
Pick-Axe Fit
10.5/15
Solo Buildability
3.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

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