--- title: "Why launch amplification has to land in the first hour — Shown Media" url: https://shown-media-spec.netlify.app/resources/first-hour-amplification description: "Creator amplification only compounds while the algorithm is still deciding how far to push a launch post. What the Merge and Slash launches show." --- # Why launch amplification has to land in the first hour By Shown Media. Published October 1, 2026. Amplification has to land in the first hour because that is when the platform decides how far to push the launch post. Creator posts that arrive inside that window compound. Posts that arrive after it do not. In Merge’s Agent Handler launch, 15 creators released together added 866K views to a launch that reached 2M+ across X and LinkedIn. ## What decides how far a launch post travels? The Slash case study describes the mechanism on X. Every post goes through a sample test. The algorithm shows the launch to a few hundred people and studies whether they stop scrolling, watch the video through and comment. “Pass, and you get pushed to the next tier. Fail, and the launch dies at 300 impressions no matter what was spent on it.” So reach is decided early, and it is decided by engagement. The Merge case study puts it this way: “Reach on X is exponential or it’s dead. The difference between 100K views and two million is not just the content, it is whether the chain reaction got enough traction early enough.” ## Is having creators enough? No. Merge had tried a launch on its own before working with us. On March 31, 2026, the team launched Gateway in-house, on X and LinkedIn. It saw minimal traction, and the motion died shortly after posting. The case study is clear that timing was not the only gap. That launch had no strategy and no video to carry it. But it did have influencer posts. “They had influencer posts, but what it lacked was timing.” The case study calls this pillar “The first hour is everything” and gives the reason: “Amplification only compounds when it lands inside the launch window, while the algorithm is still deciding how far to push the main post”. ## What does a wave look like? For Agent Handler, “we lined up 15 creators and released them as a wave instead of a drizzle.” A drizzle is creator posts arriving a few at a time. A wave is the whole group inside the launch window. The difference is what the algorithm sees while it is still making its decision. “That layer alone added 866K views, and every quote retweet fed engagement back into the post it was quoting.” The second half of that sentence matters. A creator’s quote post does more than reach the creator’s own audience. It sends engagement back to the launch post during the period when engagement counts most. ## Which creators should carry a launch? Two answers come from the case studies. The first is creators who have been tested. From the Slash case study: “Because we run launches every week, we know which influencer is which. The same vetted roster fired for Slash on each launch.” One Slash launch pulled over 1.7M influencer views. The second is creators the buyer already follows. WithCoverage wanted inbound from the GCs and CFOs who own insurance. They “don’t follow insurtech accounts. They follow finance and business creators.” So the influencer layer ran through accounts like Robert Sterling, “whose replies are full of the operators and executives WithCoverage needs in its funnel.” ## What else feeds the launch window? Creators are one source of early engagement. The post can generate its own. The launch put a $10,000 bounty on the demo, open to anyone on X who could pull sensitive information out of a live agent. “The demo was a dare, and the dare collected quote tweets from exactly the security crowd the product was built for.” It drove over 1,300 comments. Parker opened a free version of the product inside the launch post. Readers commented “Parker” and got a reply. The case study notes that “every author response reads as a live conversation to the algorithm, which directly extends reach”. Underneath, a two-tier influencer campaign “kept fresh audiences hitting the post through the day.” ## Does it get easier with repeat launches? For Slash it did. The same roster ran on each of four launches across 2025 and 2026, and the layer “got cheaper and sharper with every run.” The audience compounded as well: “the audience that found Slash through launch one was distribution for launch four.” The fourth launch, accounting automation, did 1.52M views in 24 hours. ## What are the limits of amplification? It cannot stand in for the launch. Our FAQ says it plainly: “We amplify what’s already there, so the stronger your product and offer, the bigger the upside.” It cannot guarantee a result either. “We can’t guarantee it, but we can engineer for it.” And it does not make the attention last. A launch is a spike. Impressions peak within 48 hours and then drop off. ## Sources This guide draws on these pages. - [Merge case study](https://shown-media-spec.netlify.app/case-studies/merge) - [Slash case study](https://shown-media-spec.netlify.app/case-studies/slash) - [WithCoverage case study](https://shown-media-spec.netlify.app/case-studies/withcoverage) - [Parker case study](https://shown-media-spec.netlify.app/case-studies/parker) - [Creator amplification](https://shown-media-spec.netlify.app/tech#creator-amplification) - [Tech launches: frequently asked questions](https://shown-media-spec.netlify.app/tech#faq-section) ## More guides - [How a launch campaign works: timeline, deliverables and what to expect](https://shown-media-spec.netlify.app/resources/how-a-launch-campaign-works) - [The most important line of a launch: how the mom-test works](https://shown-media-spec.netlify.app/resources/first-line-mom-test) ## Announcing something in the next 90 days? Send a short brief or book a call. We’ll map your positioning, define your bold claim and outline how we’d engineer the launch. We take on a limited number of clients at a time. [Plan your launch](https://shown-media-spec.netlify.app/contact) | [Book a call](https://app.cal.com/matt-epstein-7qqslk/shown-intro-launch-call)