B
Royal Palace Filming Permit One-Stop Agency
3.15
Derivation Chain
Step 1
Korean historical drama and period content production boom
→
Step 2
Surging demand for royal palace and cultural heritage filming locations
→
Step 3
Filming permit administrative process agency and scheduling service
Problem
Demand for filming permits at royal palaces and cultural heritage sites is surging due to historical K-dramas, YouTube content, and wedding photography. However, the Cultural Heritage Administration's permit process is fragmented across departments (Gyeongbokgung, Changdeokgung, and Jongmyo each require separate applications), with differing document formats and submission deadlines. Small production companies and solo creators spend an average of 5-10 business days and $225-$375 in administrative costs per permit application. Rejection reasons are often unclear, causing additional 2-3 week delays for resubmission.
Solution
A one-stop SaaS that auto-generates filming permit applications for royal palaces and cultural heritage sites, tracks application status, and provides rejection reason analysis with revision guidance. Core features: (1) Location-specific required document auto-checklist + form auto-fill, (2) Application-review-approval status dashboard, (3) Rejection reason pattern analysis and revision suggestions.
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 (76%)
Data Availability
20.8/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 (54/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
Backend [medium]
Frontend [low]
AI/ML [low]