A

AI Output Contract Clause Review

4.05

Derivation Chain

Step 1 Surge in value of human-made work amid AI flood
→
Step 2 AI/human-made distinction becomes a contractual condition
→
Step 3 Automated review service for AI output contract clauses

Problem

Marketing agencies and content studios (5–30 employees) face a surge in contract clauses that must specify AI usage scope, copyright ownership, and secondary processing rights when signing delivery contracts with clients. Without a legal team, they either pay 300,000–500,000 KRW per transaction (approx. $225–$375) for external legal advice or are exposed to post-disputes due to ambiguous clauses, incurring unnecessary costs of 2–5 million KRW annually (approx. $1,500–$3,750).

Solution

Upload a delivery contract, and the system automatically identifies AI-related clauses (copyright ownership, AI usage disclosure obligations, secondary work rights), compares them against industry-standard clause templates, and highlights risk factors. It also provides revision suggestions and links to industry-specific case law.

Target: Marketing agencies with 5–30 employees, content production studios, freelance PDs (producers/directors)
Revenue Model: SaaS monthly subscription: 49,000 KRW/month per account (approx. $37, 20 reviews per month); additional 3,000 KRW per transaction (approx. $2); 20% discount for annual billing.
Ecosystem Role: Regulation
MVP Estimate: 2_weeks

NUMR-V Scores

N Novelty
3.0/5
U Urgency
5.0/5
M Market
4.0/5
R Realizability
4.0/5
V Validation
4.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.
Each dimension is scored 1-5 and weighted into grade S/A/B/C/D.
N=.15 U=.20 M=.15 R=.30 V=.20

Feasibility (73%)

Tech Complexity
29.3/40
Data Availability
23.3/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.
Total 100 points; below 50% is filtered out.

Market Validation (58/100)

Competition
8.0/20
Market Demand
6.2/20
Timing
16.0/20
Revenue Signals
10.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.
Total 100 points; below 50 is filtered out.

Technical Requirements

Backend [medium] AI/ML [medium] Frontend [low]
Dashboard