B
EV Mechanic ADAS Training Bot
3.15
Derivation Chain
Step 1
BYD/Chinese EV sudden braking issues
→
Step 2
Surging EV ADAS repair demand
→
Step 3
ADAS training service for mechanics
→
Step 4
ADAS diagnostic code interpretation learning chatbot
Problem
ADAS-related faults (emergency braking, lane keeping, etc.) are increasing across EVs including Chinese-made models, yet over 90% of Korean auto mechanics have only received internal combustion engine training. ADAS diagnostic trouble codes (DTCs) differ by manufacturer, and Chinese vehicle manuals are available only in English or Chinese. Offline training costs $375–$750 per session over 2–3 days — prohibitive for small independent repair shops.
Solution
(1) Enter an OBD-II trouble code to get instant Korean-language explanations of the ADAS module's root cause and repair procedures, (2) an interactive chatbot for learning manufacturer-specific ADAS system architecture (Hyundai, Kia, BYD, Tesla, etc.), (3) competency certification through quizzes and simulations based on real repair cases. Differentiator: first-ever Korean-language DTC explanations for Chinese vehicles.
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 (78%)
Data Availability
23.3/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 (53/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
AI/ML [medium]
Backend [low]
Frontend [low]