Ship a feature with a plain screen recording, then repost it later as a fun 'dancing demo' video set to music; repackaging the same feature can outperform the first launch.
When it applies: feature launches on X
Fix the profile first: a friendly real photo you never change, a 1-2 line bio, and a pinned post stating your story and a concrete goal (e.g. SaaS to $10K/month, documented). Visitors from a viral post see the goal plus progress updates below and follow to watch the outcome.
When it applies: starting on X, building in public
Scan top posts daily for concepts that already went viral (e.g. a tweet 'algorithm simulator'), note ones you could build into your product, then ship and demo your version once a couple of months have passed so audiences have forgotten.
When it applies: product with a visual/demoable feature, audience on X
Pair a photo or video with a long-text genuine opinion (like a group-chat take, levelsio-style). Debate in replies means time on platform, which X rewards; avoid deliberate rage bait, which kills integrity.
When it applies: X, late 2025 algorithm
Pick the smallest acceptable version of your daily content (a quick clip, a song over it, a caption) and post that on sick or low days rather than breaking the streak.
When it applies: daily build-in-public content
Multiply daily signups by trial conversion and price for incoming monthly revenue, divide by monthly churn to get the plateau, then solve for the churn or signup level that hits your target.
When it applies: subscription SaaS with steady signups
Publicly thank and tag the creator who mentioned you; invite them to your affiliate program so their content links carry ongoing referrals.
When it applies: you have an affiliate program
Customers copy over automatically but subscriptions must be recreated by script; set billing dates and trials correctly and attach the specific card used on each subscription, or renewals fail and MRR drops.
When it applies: switching payment providers
Treat your ability to go viral as a limited energy meter; while churn is high, run passive channels (Google Ads, Meta ads tests) and spend the time on retention features instead of spikes whose signups would churn.
When it applies: high churn, existing audience
Prepare a backlog of viral-ready feature ideas and a posting plan before launch, because the spike can come faster than you expect.
When it applies: launching a relaunched product with an audience
Per Tibo's advice relayed by Rob: adding LinkedIn support spawns its own feature demands, which is why Tweet Hunter and Taplio were separate products.
When it applies: expanding to a new channel/platform
An acquired or inherited codebase (5 repos, 4 servers, API migrations, auth syncing) can eat months; budget for it and consider whether a rebuild is cheaper.
When it applies: acquiring or inheriting a product
Talk to churned users; when one says they stay on a competitor only for feature X (auto-DMs), build that rather than spending time on imperfect-but-working systems like SEO caching bugs. Separate non-ICP complaints (e.g. student discount requests) from signal.
When it applies: post-launch, high churn
Churned users don't see value fast enough; add a guided daily workflow (repurpose this viral post, reply to these 10 people, here are the follows you gained yesterday) so results are visible early.
When it applies: tool-style SaaS with churn from unguided users
Pick inspirations for different pillars (Marc Lou for the indie SaaS narrative, Daniel Dalen for video style, levelsio for raw opinions), imitate each with your own twist until your style emerges.
When it applies: starting to create content
Spend an hour every Monday scheduling seven days of tweets; even 24-48 hours of absence lets people forget you, and scheduling frees time to build things worth posting about.