Debrief
Read this after the window closes, and again at the end of the cycle.
Second and third waves
The launch window opens distribution. Two follow-ups extend it, and both belong in the original brief rather than being improvised once the first post does well.
Around T+2, the process teardown. First-person, how it was actually made, what it cost, what went wrong. This feeds three audiences simultaneously: people who want to learn the method, people who want to argue with it, people who want to buy the thing. It frequently travels as far as the original and costs almost nothing to produce, because the material is a byproduct of having done the work.
Around T+3 to T+7, the method and the on-ramp. Publish the template, the workflow, or the prompt so others can reproduce the result, alongside a short getting-started path and a destination for the traffic. Showing an impressive output without the method earns applause and stops there. Publishing the method converts viewers into participants, and each participant becomes a new distribution point.
Review cadence
Hourly during the window. Weekly across the cycle. Monthly across the roster. Three different questions, and collapsing them into one monthly review loses the only one that could have changed an outcome.
Metrics worth keeping
| Metric | What it tells you | Reasonable target |
|---|---|---|
| Engagement rate | Whether the post earned its distribution | Above 1.5% |
| Sentiment split | Whether the attention is the kind you want | Positive above 80%, negative below 5% |
| Reshare-to-like ratio | Passive consumption versus active spread | Rising is the signal; the absolute value matters less |
| Save rate | Durable value rather than momentary reaction | Surface-dependent; on short video, above 4% strong, above 8% exceptional |
| Composition of early engagers | Whether the right people showed up | Titles you would put on a target list |
| Reply-to-like ratio | Whether the post created obligation or just approval | Compare against the account's own history |
| Attributed conversion | Whether any of it reached the business | Traceable end to end via per-creator parameter or code |
Hit rate belongs on this list only when the post count is large enough for a ratio to mean something. On a small roster it is noise wearing the costume of a metric: three posts out of eleven is not ten percent of anything, it is three posts.
Trap list
| Stage | Failure | Instead |
|---|---|---|
| Expectation | Betting on one post; treating reach as the finish line | Raise the rate across many; decide the destination before creating demand |
| Selection | Choosing on follower count; buying reach from bought audiences; using creators who read scripts | Choose on hit rate, audience fit, and whether they answer their own comments |
| Accounting | No attribution; judging by likes; forgetting paid usage rights | One parameter per creator; request back-end screenshots; put the rights clause in the contract |
| Content | Feature-list reviews; showing the result without the method; link in body plus hashtag stacking | Build the post to demand a response; publish the method; link in the first comment |
| Window | Posting and leaving; buying engagement; boosting a post that never cleared baseline | Author answers every comment for an hour; real people only; amplify winners with a numeric trigger |
| Conduct | Undisclosed sponsorship; letting the creator absorb the criticism; late payment; demos beyond what users can reproduce | Disclose by default; the brand answers for the brand; pay on time; ship the honest version |
What to carry into the next cycle
Per-creator performance measured against their own baseline, not against each other. Which hooks produced replies rather than likes. Which publish hours actually worked for this audience, which is usually not what the scheduling tool suggests. Which posts cleared the amplification trigger and what the spend returned against organic.
Tiering for the next round comes out of this record. It does not come out of follower counts, and it does not come out of which creator was easiest to work with.