B
Chinese EV Recall & Defect Monitor
3.30
Derivation Chain
Step 1
BYD/Chinese EV sudden braking issues
→
Step 2
Chinese EV brand safety issue tracking service
Problem
Korean consumers who own or are considering purchasing Chinese-made EVs (BYD, NIO, XPeng, etc.) must manually search China's SAMR, the US NHTSA, and Korea's Automobile Recall Center separately to check for overseas recalls and defect reports. Chinese-language source documents are difficult to interpret, and it's impossible for buyers to determine whether defects in models not yet sold in Korea also affect domestic variants — delaying purchase decisions by an average of 2–3 weeks.
Solution
Daily crawling of recall/defect data from China's SAMR, US NHTSA, and Korea's Recall Center, consolidated and organized by vehicle model and component, with automatic matching to Korean-market models and Korean-language alert notifications. Core features: (1) model-specific defect timeline, (2) push notifications for registered vehicles when related recalls appear, (3) AI translation and summarization of Chinese-language defect reports.
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 (75%)
Data Availability
20.4/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
Data Pipeline [medium]
Backend [low]
Frontend [low]