B
Webtoon IP Derivative Revenue Tracker
3.45
Derivation Chain
Step 1
Growth of webtoon-to-film/drama IP business
→
Step 2
Increasing complexity of IP licensing revenue settlement
→
Step 3
Automated revenue tracking and settlement per derivative product
Problem
Webtoon creators and small IP management firms (1-5 people) tracking derivative licensing revenue from film adaptations, merchandise, games, etc. face partner companies sending settlement statements in different formats and on different schedules, with contract terms (MG, royalty rates, settlement periods) varying per deal. Managing 10+ derivative contracts consumes 15-20 hours monthly on statement reconciliation, and under-settlement discovery is delayed by an average of 3-6 months.
Solution
After registering derivative licensing contract terms, automatically parses each partner's settlement statements (PDF/Excel) and verifies settlement accuracy against contract conditions. Provides per-product and per-partner revenue dashboards with automatic flagging of suspected under-settlements.
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 (74%)
Data Availability
24.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
AI/ML [medium]
Backend [medium]
Frontend [low]