Post launch window
Purpose
Most content guidance ends at publish. Early distribution is decided after it, by how a post performs in its first hours. This skill sets what has to be true before a post goes live, runs the first hours in order, and gives a numeric rule for whether paid spend should follow.
When to use
- A sponsored or creator post is about to publish.
- A founder announcement, launch thread or customer story is going live.
- A post went out and the team is deciding whether to amplify it.
Route elsewhere when:
- The question is choosing the creator. Use creator-discovery-and-vetting.
- The question is drafting the sponsored copy. Use creator-sponsored-post-drafting.
- The question is the program's measurement. Use creator-program-measurement.
Inputs
- The post, its draft, and the account it publishes from.
- The agreement's usage-rights terms and their window, for any creator or sponsored post.
- The tracking set up for the post: a parameter or code per creator, or a branded-search read where links are not allowed.
- The destination the traffic will reach.
- The account's own recent average engagement, for the baseline.
Procedure
Work through the pre-publish steps first, then the sequence, then the amplification decision.
Before publish
- Build the post to invite a reply. A neutral summary earns scrolling. A stated position, an open question, or a claim someone would want to correct earns replies, and replies carry the most weight. This is not a call for provocation.
- Confirm paid usage rights in the agreement, with a stated window, before publish. Without them, a validated post cannot be amplified, and renegotiating mid-window costs time and leverage.
- Set attribution: a distinct parameter or code per creator, or a read on branded-search lift where links are not allowed.
- Ready the destination. Decide where the traffic lands, such as a sign-up path, a template or a resource, before creating the demand.
- Keep the link out of the post body. Prepare it for the first comment.
The sequence
| When | Action |
|---|---|
| Thirty minutes before | Publish when the target audience reads, not when the team is free. Draft the first comment with the link, and three to five seed questions that would each draw a second person into the thread. Tell the people who care that the post is coming. |
| Zero to fifteen minutes | Post the link comment straight away. The author answers each comment individually and in substance. The default target is about ten substantive replies in fifteen minutes. |
| Fifteen to sixty minutes | Keep replying, and extend threads rather than closing them with thanks. Once the first wave settles, post a second question to restart the conversation. |
| Sixty to a hundred and twenty minutes | Keep replying. Check the amplification trigger. Use a second surface for a second pulse, rather than a duplicate. |
| Six to eight hours | Make the amplification decision. |
| Two days | Publish a teardown of how the piece was made, what it cost and what broke. Plan this in the original brief. |
| Three to seven days | Publish the method or template, so viewers can take part. |
Never edit the original after publish. Never post and leave.
Interaction types
Rank the kinds of response by how much they show a real conversation:
- the author replying to each commenter, which is the most valuable action available;
- substantive replies from others, which cost effort and are hard to fake;
- reshares with added commentary, which reach a network the post could not reach alone;
- saves, which signal that the content is useful;
- profile visits, which are a by-product of a clear point of view;
- likes, the weakest signal, and likes without replies are a low-quality pattern;
- hides, mutes and reports, which are strongly negative.
Outbound links in the body usually reduce distribution, and verified accounts usually receive wider reach.
Amplification: only behind proven posts
Paid spend should widen a post that organic distribution has already validated, and the post should be boosted as a native post. Rebuilding it as an advert discards the social proof that made it work.
- Trigger: engagement reaches about one and a half to two times the account's own trailing baseline within six to eight hours, with clearly positive sentiment. Use the account's own recent average, not an industry benchmark.
- Stop: stop on any one of these: cost per action running about thirty percent over target for two consecutive days; frequency rising while click-through falls; organic engagement on the original falling below its baseline; or a cluster of negative brand-safety comments.
A stated trigger turns the decision into a rule. Without one, spend follows whatever the team happens to like.
Pre-publish check
- The post invites a reply through a position or an open question
- No link in the body; the link is ready for the first comment
- Two hashtags at most
- The publishing account is verified where the platform offers it
- Publish time matches the audience's reading time
- Seed questions are written, and the people who care have been told
- Paid usage rights confirmed, with a stated window
- Attribution set up for each creator
- The destination exists
- The author has the first hour free
Output
- The pre-publish checklist result, with any item left open and why.
- The timed sequence for the post, with the owner of each action.
- The amplification decision at six to eight hours, with the trigger or stop condition that applied.
- The debrief, covering reach, reply quality, and the attribution read.
Quality bar
Every item on the pre-publish check is confirmed before publish. Amplification follows a stated trigger, never a preference. The author is free for the first hour. Watch for a post with no reply-inviting position, a link placed in the body, spend behind a post below its own baseline, and an original edited after publish.
Rules
- The author answers comments personally in the first hour.
- Use only real people on their own accounts, reacting because they have something to say. Coordinated groups and purchased engagement are excluded.
- Confirm paid usage rights before publish.
- Set the amplification trigger and stop conditions in numbers, in advance.
- Disclose commercial relationships as the applicable rules require.
- Never put the link in the post body.
- Never boost a post that has not cleared its own baseline.
- Never edit the original after publish.
- Never give a creator material that performs far beyond what an ordinary user could reproduce.
