You still have 10 searches left today - give it a try!LoginRegister
Back to blog
Blog · ShortsMonkey in action
9 min read · 2026/01/05
Blueprint9 min read
Shows how cache-backed presets replace guesswork, how the queue refreshes data mid-sprint, and how teams build templates directly from exports.2026/01/05

Use our stack to go from 0 to 10K subscribers in 90 days

The exact cadence we tested: research with cache presets, publish with guardrails, and let monitors dictate the next sprint.

We ran an internal channel on top of the exact infrastructure in this repo, letting presets dictate scripts and letting monitor alerts dictate the follow-up content. No secret tools, only our own code.

Because presets are cached, a strategist can sketch a script, click the preset for proof, paste the results into a doc, and stay aligned with SEO language in minutes.

Whenever a video beat the baseline, we tagged the run, exported the data, and cloned the structure. That loop repeated until the channel crossed 10K subs in under 90 days.

Week 1–2 · Research and calibration

Run presets, log virality ratios, and decide which angles belong in the first sprint. This step proves demand before scripts exist.

Week 3–6 · Production

Batch record 10 scripts, keep runtimes consistent, and rely on exports to brief editors. Cache hits keep the workflow instant.

Week 7–9 · Review and monitor

Check analytics every 48 hours, set monitors on outperformers, and dig into search_cache_usage to see which presets keep winning.

Week 10–12 · Scale

Clone the proven structures, test variants, and take sponsors through the exact dataset that justified the pitch.

Stay inside the loop: presets for research, exports for proof, monitors for follow-up. That is the entire growth plan.