A
Broadcast Replay Clip SEO Bot
3.95
Derivation Chain
Step 1
Surge in catch-up/replay search trends
→
Step 2
Intensifying competition among broadcast replay platforms
→
Step 3
Search visibility optimization tools for replay content
Problem
Regional broadcasters (local MBC, KBS affiliates, etc.) operate their own replay/catch-up services, but search visibility is extremely low compared to major platforms like YouTube and Naver TV. Without dedicated SEO staff, optimizing titles, descriptions, tags, and thumbnails takes 30–60 minutes per video, and most content is left unoptimized — resulting in only a few hundred monthly views.
Solution
(1) Automatically analyzes subtitles/audio upon video upload to generate SEO-optimized Korean titles, descriptions, and tags, (2) auto-detects highlight segments and recommends thumbnail candidates, (3) integrates with Naver and Google search trends to apply timely keywords to tags. Differentiator: specialized for Korean regional broadcasters (Naver SEO standards, Korean subtitle processing).
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 (79%)
Data Availability
23.3/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 (51/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 [low]
Data Pipeline [low]
Frontend [low]