S
Gig Worker Contract Risk Scanner
4.50
Derivation Chain
Step 1
Zero-Hour Contracts & Gig Work Expansion
→
Step 2
Gig Worker Rights Protection Services
→
Step 3
Gig Worker Contract Unfavorable Clause Auto-Detection
Problem
Platform workers (delivery, designated driving, translation, and design Freelancers) sign work delegation contracts with platforms that contain unfavorable clauses—such as unilateral commission change rights, non-compete clauses, and liability transfer—but cannot afford legal review costs of 200,000-500,000 KRW (~$150-$375) per contract, so they sign as-is. When disputes arise afterward, average litigation costs reach 3-5 million KRW (~$2,250-$3,750) with 3-6 months of time consumed.
Solution
Gig workers upload contract PDFs/images, and AI automatically scans 15 key checkpoints (commission change rights, non-compete clauses, liability transfer, termination conditions, IP ownership, etc.) to display risk grades (Danger/Caution/Good). Provides suggested revision language and relevant case law summaries for each unfavorable clause.
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 (57/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]