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

Competitor references

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

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.

Target: Individual vehicle owners aged 30–50 who own or are considering Chinese-made EVs; used car dealers
Revenue Model: Premium Subscription at $3/month per account (basic search free; push alerts, AI translation, and detailed reports are Paid)
Ecosystem Role: Consumer
MVP Estimate: 2_weeks

NUMR-V Scores

N Novelty
3.0/5
U Urgency
3.0/5
M Market
3.0/5
R Realizability
4.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 (75%)

Tech Complexity
34.7/40
Data Availability
20.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.

Market Validation (53/100)

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