No usable source links are available for this idea. Its signal notes and scores need independent verification.
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.
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.
| 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. |
| 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. |
| 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. |