B
Traffic Accident Insurance Claim Self-Assessment Tool
3.35
Derivation Chain
Step 1
Expansion of public traffic accident big data
→
Step 2
Increase in insurance claim disputes among traffic accident victims
→
Step 3
Pre-verification tool for insurance claim adequacy
Problem
Among approximately 300,000 traffic accident victims annually, the majority do not know whether the settlement amount offered by insurance companies is fair. Relying on insurance agents creates conflicts of interest, and lawyer consultations cost 100,000-300,000 KRW per case (approx. $75-$225). Due to lack of knowledge about appropriate compensation, victims frequently settle for amounts 15-30% lower than average.
Solution
By entering accident type (rear-end/side/pedestrian), injury area, treatment duration, and fault ratio, it calculates a fair settlement range based on past case law DB and insurance company payment cases. Differentiation: specialized in Korean traffic accident precedents, comparison of settlement patterns by insurer, and guidance on missing documents.
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. |
N=.15 U=.20 M=.15 R=.30 V=.20
Feasibility (70%)
Data Availability
20.8/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 (55/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
Backend [medium]
Frontend [low]
Data Pipeline [medium]