A
Consumer Dispute Evidence Assembler
3.95
Derivation Chain
Step 1
Coupang data breach + sharp decline in operating profit
→
Step 2
Growing number of consumers harmed by major platforms
→
Step 3
Consumer dispute filing automation
Problem
When consumers who have suffered damages from major platforms—such as Coupang's personal data breaches, delivery incidents, or refund denials—file a complaint with the Korea Consumer Agency, it takes an average of 3-5 hours to collect and organize evidence (screenshots, transaction records, call recordings) and fill out the application. About 40% of cases are dismissed due to unfamiliarity with procedures or insufficient evidence.
Solution
Users select the type of damage (data breach, refund denial, delivery incident, etc.) and an evidence checklist is auto-generated. Upon uploading screenshots and transaction records, the system auto-fills the Korea Consumer Agency application form. Similar past dispute resolution cases and outcomes are provided as references.
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.1/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 (56/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 [low]
AI/ML [medium]
Frontend [low]