B
Human-Made Certification Seal
3.50
Derivation Chain
Step 1
Surge in value of human-made work amid AI flood
→
Step 2
Certification service for differentiating human-made work
→
Step 3
SaaS for issuing and verifying certification marks
Problem
As AI-generated content surges, freelance designers, writers, and video producers (with annual revenue of 30–100 million KRW, approx. $22,500–$75,000) have no way to prove to clients that their work is 'human-made.' Disputes over AI usage during delivery are increasing, wasting an average of 2–5 hours per transaction on explanation and revision.
Solution
A SaaS that automatically collects work process data (screen timelapses, layer history, commit logs) to issue a 'Human-Made Certification Seal' that clients can verify via QR code. Differentiated by portfolio embed widgets and contract integration features.
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 (69%)
Data Availability
19.4/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
Frontend [medium]
Backend [medium]
Data Pipeline [low]