Creator Competitor Radar — Discover What Others Are Doing

Comparison scope

Topic alignment is supplied, but audience match and channel scale are unverified. Evidence window: 28 days. Public counts and video descriptions are user-supplied observations, not independently refreshed.

Normalization caution

Simple average views/day are approximately 142.9 for A’s example and 214.3 for B’s example. These are crude elapsed-time ratios, not growth trajectories or proof B performs better. View accumulation is nonlinear; audience size, traffic source, posting date and other factors are unknown. Do not extrapolate revenue, CTR, retention or algorithm preference.

Strategic hypotheses

A may emphasize accessible procedural learning; B’s observed example may serve users diagnosing a specific problem. Each inference needs a broader sample and consistent evidence window. Neither observation establishes why a video attracted views.

Original experiment

Create a tutorial for a problem our own audience has actually supplied, combining a clear diagnosis checklist with a worked example. Use our own structure, script, visuals and product evidence. Compare comprehension and qualified engagement against a relevant existing piece while documenting changed topic, length and packaging; avoid labeling it a controlled A/B test without a suitable design.

Research gaps and next actions

Collect multiple content samples per creator, publish dates, age-matched visible outcomes, audience-value descriptions and repeated packaging observations. Distinguish aspirational references from direct competitors. Search for unmet audience jobs using legitimate evidence rather than assuming empty topic space equals demand.

Private analytics, revenue, sponsor rates, team size and strategy remain unknown. No competitor monitoring, scraping, alerts or outreach were performed.