Launch Window Mechanics

Feeds do not distribute a post. They test it. A small slice of the audience sees it first, the system scores the reaction over the following half hour, and distribution either widens or stops. Almost everything written about creator marketing ends at publish. The reach was decided after that.

The job in this window is narrow: produce enough real, fast, high-quality reaction inside the test to clear the threshold, then decide whether the result deserves paid spend behind it.

Produces: a pre-publish setup, a timed sequence from thirty minutes before to two hours after, a go/no-go call on amplification with stop conditions, and a debrief that feeds the next cycle.

Before the post exists

The window cannot be worked if the post was not built to be worked. Three things are decided at draft time, not at publish time.

The post must create an obligation to respond. A neutral summary earns scrolling. A stated position, an open question, or a claim someone would want to correct earns replies, and replies are what the ranker weighs. This is not a call for provocation. It is the difference between "here is what we shipped" and "most teams are still doing this the slow way, here is the number that changed our mind."

Rights and attribution are contractual, not operational. The creator agreement must grant paid usage rights on the post itself, with a stated window. Without that clause, the post you spend six hours validating cannot be amplified, and renegotiating mid-window costs both time and leverage. This is the most common preventable failure in the sequence. Attribution goes in at the same time: a distinct tracking parameter or code per creator, and where links are not permitted, a read on branded-search lift instead.

The traffic needs somewhere to land. Reach is the entry, retention is the business. A spike arriving at a page with no next step is a spike that churns. Decide the destination before creating the demand: a signup path, a template, a resource, a community.

Choosing who to run this with: references/creator-scorecard.md.