B

Autonomous Driving Safety Scenario Lab

2.85

Derivation Chain

Step 1 Full autonomous driving commercialization imminent
→
Step 2 Surge in autonomous driving software testing demand
→
Step 3 Edge-case scenario auto-generation and simulation verification service

Competitor references

No usable source links are available for this idea. Its signal notes and scores need independent verification.

Problem

Autonomous driving software companies must create and validate tens of thousands of edge-case scenarios (wrong-way vehicles, temporary signals in construction zones, nighttime pedestrians, etc.) for Level 4 certification. Each scenario takes a specialized engineer an average of 2-4 hours to write, and Korea-specific road environment scenarios (narrow alleys, illegal parking on back streets, etc.) are not covered by overseas datasets.

Solution

A SaaS that auto-generates Korea-specific road environment edge-case scenarios using LLM, converts them to OpenSCENARIO format, and outputs test files immediately executable in CARLA/LGSVL simulators. Trained on public traffic accident data to reflect Korean accident patterns.

Target: Test/QA teams at autonomous driving software companies (20-200 employees), autonomous driving Startup CTOs
Revenue Model: Per Transaction: ~$3.75 (~5,000 KRW) per scenario generated; Monthly Subscription: ~$217 (~290,000 KRW) including 100 scenarios/month. Volume contracts (1,000+/month): ~$1.50 (~2,000 KRW) per scenario
Ecosystem Role: Supplier
MVP Estimate: 2_weeks

NUMR-V Scores

N Novelty
4.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.
N=.15 U=.20 M=.15 R=.30 V=.20

Feasibility (68%)

Tech Complexity
29.3/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 (51/100)

Competition
8.0/20
Market Demand
6.2/20
Timing
14.0/20
Revenue Signals
7.5/15
Pick-Axe Fit
12.0/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

Backend [medium] AI/ML [medium] Data Pipeline [low]
Dashboard