B

AI Chatbot Training Scenario Marketplace

2.70

Derivation Chain

Step 1 Full-scale adoption of AI agent-based customer service
→
Step 2 Growing demand for AI chatbot quality improvement
→
Step 3 Domain-specific scenario datasets for chatbot training
→
Step 4 Crowdsourced scenario dataset Marketplace

Problem

E-commerce, aviation, and Legal companies that have deployed AI chatbots need domain-specific training data (conversation scenarios) to improve bot performance, but in-house creation costs $1,500-3,000 (~200-400만원) per 100 scenarios and takes 2-3 weeks. Existing datasets are English-centric and don't fit Korean language and cultural context (honorifics, indirect complaint expressions, etc.), causing rework rates of 40% or more.

Solution

Domain-specific Korean conversation scenarios (E-commerce returns, flight delays, legal consultations, etc.) are crowdsourced, quality-reviewed, and sold on a Marketplace. Scenario writers (former CS agents, domain practitioners) use templates, and AI performs automated quality checks (naturalness, coverage, difficulty distribution).

Target: AI/ML engineers or CS operations leads at E-commerce, aviation, and Insurance companies with 20-100 employees operating AI chatbots
Revenue Model: Scenario pack sales at $29-$149 per pack (100-500 scenarios), 20% Marketplace commission. Monthly Subscription (auto-delivery of new scenarios) at $74/month
Ecosystem Role: Supplier
MVP Estimate: 2_weeks

NUMR-V Scores

N Novelty
3.0/5
U Urgency
3.0/5
M Market
3.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.
Each dimension is scored 1-5 and weighted into grade S/A/B/C/D.
SaaS N=.15 U=.20 M=.15 R=.30 V=.20 Senior N=.25 U=.25 M=.05 R=.30 V=.15

Feasibility (74%)

Tech Complexity
29.3/40
Data Availability
24.4/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.
Total 100 points; below 50% is filtered out.

Market Validation (53/100)

Competition
8.0/20
Market Demand
6.2/20
Timing
14.0/20
Revenue Signals
9.0/15
Pick-Axe Fit
10.5/15
Solo Buildability
5.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.
Total 100 points; below 50 is filtered out.

Technical Requirements

Backend [medium] Frontend [medium] AI/ML [low]
Dashboard