B

Traditional Culture IP License Tracker

3.00

Derivation Chain

Step 1 K-POP × cultural heritage collaboration trend
→
Step 2 Commercial use service for cultural heritage/traditional IP
→
Step 3 License contract management and tracking for traditional culture IP

Problem

Brands wanting to use cultural heritage IP (national museums, palaces, traditional patterns) for goods, albums, and packaging are increasing, but IP usage permission conditions (scope, period, royalty settlement) differ by institution, and contracts are scattered in PDF/Hangul files, so small brand managers take 3-5 days per contract to assess violation risk.

Solution

Upload cultural heritage/traditional IP license contracts, and OCR+LLM automatically extract key conditions (usage scope, period, prohibitions), providing calendar-based expiration and settlement alerts. Also auto-generate a Cultural Heritage Administration permission requirements checklist.

Target: IP license managers at fashion/goods/F&B brands with annual revenue of 100 million to 1 billion KRW (approx. $75,000 to $750,000), and legal teams at small and medium entertainment agencies.
Revenue Model: SaaS monthly subscription: 59,000 KRW per month per account (up to 10 contracts) (approx. $44.25), additional contracts at 3,000 KRW each (approx. $2.25). 15% discount for annual payment.
Ecosystem Role: Regulation
MVP Estimate: 2_weeks

NUMR-V Scores

N Novelty
3.0/5
U Urgency
3.0/5
M Market
3.0/5
R Realizability
3.0/5
V Validation
3.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 (70%)

Tech Complexity
29.3/40
Data Availability
20.6/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 (51/100)

Competition
8.0/20
Market Demand
6.2/20
Timing
14.0/20
Revenue Signals
7.5/15
Pick-Axe Fit
10.5/15
Solo Buildability
5.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] Frontend [low] AI/ML [medium]
Dashboard