A
Actor Fandom Power Index
3.50
Derivation Chain
Step 1
K-drama actor buzz
→
Step 2
Advertisers' model selection decision-making
→
Step 3
Quantified per-actor fandom size and loyalty index
Problem
Marketing teams at brands spending $375K–$3.75M annually on advertising rely on ad agencies' subjective recommendations when selecting celebrity endorsers because there is no objective data to compare actors' actual fandom size, loyalty, or purchase conversion power. Brands commit $75K–$750K on talent contracts without data-driven verification of whether a given actor matches their target audience.
Solution
A SaaS platform that automatically collects each actor's SNS followers, real-time search volume, fan community activity, online mentions, and ad response rates to calculate a 'Fandom Power Index,' then provides a matching score against the brand's target segments. Core features: (1) Per-actor Fandom Power Index across reach, engagement, and conversion axes, (2) Brand target–fan base overlap analysis, (3) Competitor brand endorsement benchmarking.
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 (71%)
Data Availability
21.2/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 (58/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
Data Pipeline [medium]
Backend [medium]
Frontend [low]