Rewrite Strategy 8 around scraped Runify ground-truth#12
Merged
Conversation
Scraped @runifyyy (646 reels over 282 days) via Apify and found the actual playbook materially differs from what Caleb Dean narrated on the Superwall Podcast. This commit preserves the findings so Strategy 8 can be rewritten against reality rather than the sanitized interview version. Key differences between podcast story and scraped data: - 9 reels/day claim → actual peak cadence ~5/day (May-Jul 2025) - "5M views in month one" → actual 16.1M over 9 months; the real algorithmic lift came in month 6 (October 2025), not month 1 - "Parameterized ranking graphics with ChatGPT icons" → actual content is cheap movie/animation clip remixes (5-10 second reaction videos with tiny emotional captions like "WTF!", "are we cooked???") - "1 in 10 videos above 500k plays" → actual hit rate 1 in ~92 - Top single reel 4.1M plays (Oct 2 2025); top 7 reels carry 61% of cumulative views — the distribution is extremely asymmetric This commit adds: - research/runify-content-engine-analysis.md — full writeup with monthly timeline, top-reel table, content-style analysis, and implications for rewriting Strategy 8 - research/runify-top-reels.csv — top 30 reels by play count, dated - .gitignore additions for the raw 20MB scrape dataset and Windows Zone.Identifier sidecars Pending: a second scrape of @runifyy.app (sibling account) is in progress. Findings will be combined before the Strategy 8 rewrite. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Scraped @runifyy.app — bio explicitly labels it "Runifyyy second account." 255 reels over 101 days (Aug 7 – Nov 16, 2025). Combined with the primary account, the dataset now covers 901 reels and 22.7M cumulative plays. Key revision from the first-pass analysis: with both accounts in view and day-level cadence computed properly, Caleb's podcast claims turn out to be much more defensible than my initial read suggested. - "9 reels/day for a while" — true for burst weeks. Peak 7-day window hit 11.3 posts/day (Jun 28 – Jul 4, 2025). Single-day peak: 19 posts on 2025-06-28, still on the primary account alone. - "5 million views in month one" — true if you read "month one" as the first 30 days of @runifyy.app after it launched Aug 7, 2025. That secondary-account launch burst produced ~5.2M plays on 60 posts, with a 3.8M-play single hit on Aug 23. - "10,000 parameterized variations" — still unverified and likely a rhetorical flourish. 901 total posts over 9 months is the actual scale. - "Copied Liftoff's ranking format" — partially true. Rank-CTA content is ~15-20% of output; 80% is cheap meme-remix reaction videos. The multi-account structure is the biggest omission from the podcast narrative. It's also the single most important missing piece for anyone trying to execute this playbook: you can't sustain 9/day on a single account without throttling, but you can hit 11/day combined across two parallel accounts posting different content (caption overlap between the two accounts is only 10.4% — not duplication, true volume multiplier). The analysis file now documents the full combined picture, the monthly cadence by account, where my first-pass read was wrong, and a sharpened set of implications for the Strategy 8 rewrite — including a new "multi-account as Stage 4 of the content engine" recommendation. Adds research/runify-secondary-top-reels.csv with the top 30 reels from @runifyy.app for structured reference. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Based on the scrape analysis in research/runify-content-engine-analysis.md, rewrite Strategy 8 to reflect what Runify actually did rather than the sanitized narrative from the Superwall Podcast interview. Key changes: - Rename: "Pre-Build Distribution Validation via Competitor Format Replication" → "Parallel Instagram Reels Content Engine (Consumer Mobile)". The validation framing is downstream; the content engine is the primitive. - Timeline: "2-4 weeks" → "5-6 months on a fresh discovery account, 2-4 weeks on a sibling launch account once the format is validated." Matches the observed Runify pattern of 4-5 months of grinding on @runifyyy before the October 2025 algorithmic lift. - Content type: dropped Remotion / Creatomate / Bannerbear / After Effects parameterized-template tooling recommendations. Added CapCut + hand-curated clip library + GPT caption prompt as the actual tool stack. The engine is manual meme-remix, not programmatic layered rendering. - Content format: described explicitly as an 80/20 interleave of meme-remix reaction videos (5-10 sec movie/animation clips with 1-5 word emotional captions) and functional rank-CTA posts. Gave direct examples pulled from the scraped feed. - Multi-account infrastructure: added as Stage 3 of the content engine. This is the load-bearing mechanism behind the "9 reels/day" cadence claim and was omitted from every public version of the Runify story. Documents the discovery-account / launch-account pattern, caption-overlap discipline (<15%), cross-promotion, and follower-graph minimalism. - Kill criteria: calibrated against actual scraped hit rates (2.5% of posts clear 100k, 1% clear 500k, 0.5% clear 1M). The "first 100k+ hit by post 300" threshold matches what Runify actually experienced on the primary account. - IP risk: elevated from a one-liner caveat to a first-class pitfalls-section entry. Acknowledges honestly that meme-remix content leverages copyrighted movies, animations, and music, and that the multi-account structure mitigates but does not eliminate takedown risk. - Sourcing honesty: the opening "Why it works" section now points readers to research/runify-content-engine-analysis.md for the primary-source analysis, and explicitly states that the playbook is grounded in scraped feed data, not just the founder's interview. Also: - Prioritization Matrix row updated: effort Very High, cost $0-50/mo, timeline "5-6 months (discovery acct) / 2-4 weeks (launch acct)", applicability caveat about the 6+ month commitment and IP stance. - Recommended starter combination updated. - README.md strategy list updated with new title, new one-liner, and a pointer to the research analysis file. - research/runify-content-engine-analysis.md gains a third-account sanity-check section documenting the search for additional Runify operational accounts (none found beyond @runifyyy and @runifyy.app). Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Code Review
This pull request significantly refines Strategy 8 in the growth playbook, transitioning it from a programmatic validation approach to a high-volume 'Parallel Instagram Reels Content Engine' for consumer mobile apps. The update is backed by a new ground-truth analysis of the Runify case study, emphasizing multi-account infrastructure and meme-remix content over automated rendering. Feedback focuses on resolving minor inconsistencies in priority levels and duration constraints, as well as broadening the scope of IP risk assessment in the provided agent tasks.
| **Time to first result:** 2-4 weeks | ||
| **Best for:** Native iOS/Android consumer apps — especially social, competitive, gamified, or habit-tracking categories where a short-form video can demo the value in under 15 seconds | ||
| **Skip if:** B2B SaaS, dev tools, APIs, agencies, enterprise sales, or niches where no non-VC-funded competitor has sustained $100k+/month for 12+ months (no proven format to copy = no signal to trust) | ||
| **Priority:** High (for consumer mobile apps with visual, competitive, gamified, or habit-tracking mechanics) |
Contributor
There was a problem hiding this comment.
The priority level for Strategy 8 is inconsistent. It is listed as "High" here, but the Prioritization Matrix on line 569 lists it as "Very High". Given the depth of the rewrite and the data-backed results, "Very High" appears to be the intended priority.
Suggested change
| **Priority:** High (for consumer mobile apps with visual, competitive, gamified, or habit-tracking mechanics) | |
| **Priority:** Very High (for consumer mobile apps with visual, competitive, gamified, or habit-tracking mechanics) |
| **Priority:** High (for consumer mobile apps with visual, competitive, gamified, or habit-tracking mechanics) | ||
| **Time to first result:** 5–6 months on a fresh discovery account; 2–4 weeks on a sibling launch account once the format is validated | ||
| **Best for:** Native iOS/Android consumer apps whose value proposition can be visually or emotionally teased in a 5–10 second short-form video. Teams willing to commit one operator to 10–15 hours per week for 6+ months of sustained content production. | ||
| **Skip if:** B2B SaaS, developer tools, APIs, agencies, enterprise sales. Niches where no non-VC-funded competitor has sustained $100k+/month for 12+ months. Products that cannot be visually teased in under 10 seconds. Teams unwilling to engage with meme-remix content (which sits in copyright grey territory). |
Contributor
There was a problem hiding this comment.
There is a logical inconsistency between the "Best for" and "Skip if" criteria regarding video duration. The "Best for" section (line 399) includes videos up to 10 seconds, but the "Skip if" section suggests skipping if the product cannot be teased in under 10 seconds. This would mean a product that requires exactly 10 seconds would be both recommended and skipped.
Suggested change
| **Skip if:** B2B SaaS, developer tools, APIs, agencies, enterprise sales. Niches where no non-VC-funded competitor has sustained $100k+/month for 12+ months. Products that cannot be visually teased in under 10 seconds. Teams unwilling to engage with meme-remix content (which sits in copyright grey territory). | |
| **Skip if:** B2B SaaS, developer tools, APIs, agencies, enterprise sales. Niches where no non-VC-funded competitor has sustained $100k+/month for 12+ months. Products that cannot be visually teased in 10 seconds or less. Teams unwilling to engage with meme-remix content (which sits in copyright grey territory). |
| - Draft the Mode A fake landing page HTML with a Stripe Payment Link and waitlist capture, OR the Mode B per-reel UTM routing plan | ||
| - Write the explicit kill criteria in terms of posts-to-first-100k and posts-to-first-500k, tied to `{{BUDGET}}` and timeline | ||
| - If iOS and pre-launch: produce the App Store Connect pre-order configuration document including the 2-to-180-day release window constraint and the exceptional-delay communication plan | ||
| - Flag IP-risk elements in any template that crosses from structural copying into brand-asset copying |
Contributor
There was a problem hiding this comment.
The agent task for flagging IP risk is too narrow. The original wording focused on "brand-asset copying," but the rewritten strategy identifies a much more significant risk: the use of copyrighted movie and animation clips for meme-remixes. The task should be updated to ensure the agent flags these broader copyright concerns as well.
Suggested change
| - Flag IP-risk elements in any template that crosses from structural copying into brand-asset copying | |
| - Flag IP-risk elements in any template or clip selection that crosses from structural copying into brand-asset copying or copyright infringement |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR rewrites Strategy 8 and adds a supporting research artifact, both grounded in primary-source data rather than the founder-interview narrative that the original Strategy 8 was built on.
The backstory
The original Strategy 8 (merged in PR #9) was written against Caleb Dean's account of Runify's growth as told on the Superwall Podcast. The narrative described a principled, engineered content engine: 10,000 parameterized Reel variations, a ranking-graphic format copying Liftoff's Instagram strategy, 9 reels per day, 5 million views in month one.
When we cross-checked against Runify's actual Instagram feeds, the story didn't match. This PR preserves the ground-truth analysis (on a research branch — not committed to the playbook itself) and rewrites Strategy 8 to describe what Runify actually did.
What the scraped data shows
Two parallel Instagram accounts were scraped via Apify:
Combined: 901 reels, 22.7M cumulative plays over 9 months.
Key findings:
Full analysis with monthly timeline tables, top-reel listings, and implication breakdowns lives in `research/runify-content-engine-analysis.md` (added in this PR).
What the rewrite changes
Files changed
Test plan
🤖 Generated with Claude Code