Creators ask what a launch post pays before they ask what it costs them. The fee is the easy number. The harder one is the two to three hours it takes across the week, and how much of that time lands at the worst possible moment: a morning you had blocked for something else, an hour before a deadline you actually care about.

Here is the week, hour by hour, with the parts the agency should be carrying and the parts that stay with you. The totals are small. The scheduling is what decides whether the job is worth taking, and the scheduling is the part most creators never ask about until the first launch lands on a bad week.

The week before

Ten days out you get the brief: 45 minutes, and one call if you want it. What you are reading for is the claim, the three facts behind it, the objection the post has to answer, and the window. Reply with a yes, a no, or a question. A decline at this point costs nothing and nobody keeps score.

Read the brief on the day it arrives if you can. The failure mode is a brief that sits unopened until the review deadline, and then a rushed post and a review round compressed into an afternoon. The 45 minutes is what buys you the option to say no early.

Three days out you write. For a single post that is 20 minutes. For a thread, 30 to 60. The number depends on how much you already know about the subject, which is why the category matters more than the follower count: a developer tooling account does not need to research a developer tooling launch.

Then one review round, answered inside 24 hours. Facts, links, and disclosure. A review that comes back asking for a different tone is not a review; it means the brief picked the wrong creator. If the window and your calendar do not fit, say so now. Moving the window costs the client a day. Posting from an airport costs you the post.

Book the reply hour at the same time you agree to the post. The usual failure is a creator who publishes on time and then disappears into a meeting, leaving a founder to answer questions about a post that carries somebody else’s name. If you cannot hold the hour, the window is wrong, and it is easier to say that on day minus ten than on launch morning.

Launch day, hour by hour

The window is 60 minutes wide and anchored on the founder’s post. Your job is to publish inside it with the link and the disclosure line intact. ChirpLift runs the schedule, so nobody refreshes a timeline or coordinates with fourteen other accounts.

Ten minutes before the window, check three things: the link resolves, the label is set, and the founder has actually posted. That is the whole task until the window opens. If the founder slips, the schedule moves and you get told, which is the difference between a coordinated launch and a group of people guessing.

This is also the hour the fee gets justified. The post lands in a timeline a founder has just lit up, and the audience has a reason to look at it right then instead of tomorrow. One post inside that window does more than three posts spread across a week, which is why the timing is worth the coordination it costs.

Ask which timezone the window is in and put it in your calendar with the conversion already done. Half the missed windows in a coordinated launch are arithmetic, not commitment, and the creator gets blamed for a number somebody else worked out.

The hour after you post

Budget 60 minutes for replies. Some will be questions about the product, which the founder answers better than you. Some will be people telling you that you sold out, which is a normal cost of posting anything with a label on it.

Answer what you can. Pull the founder into the thread when you cannot, and have the handle ready before you post so you are not searching for it while the notifications arrive. Leave the criticism standing, because deleting it turns a disagreement into a story about the deletion.

If you know about a limitation, say it in a reply before somebody else finds it. Being first with the caveat is worth more than the reach you lose by mentioning it. The replies are also the part of a launch that produces anything durable: a question answered well gets screenshot, and a screenshot travels further than the original post.

What not to do is argue about the payment in public. A defensive reply about how little the post paid reads worse than the disclosure line ever will, and it puts the fee in front of an audience that was there for the product. If a reply gets under your skin, answer it an hour later or not at all.

What we take off your plate

The scheduling, the other creators, the founder’s timing, the client’s questions, the review round, the recap. None of that needs you. What reaches you is the brief, the reply window, and payment.

That coordination is most of the reason a launch reads as a launch. Left to itself, it reads as eight accounts posting the same link at random times over two days, which the audience recognises and discounts.

If a client starts asking you directly for changes, send them to us. Answering those requests yourself is how a creator ends up with three versions of a post and a client who thinks the creator is the account manager.

The recap is smaller than it sounds and worth more than creators expect. Fifteen minutes at the end of the week, written by us, with the numbers the client asked for. You do not fill in a template, count impressions, or explain why a post performed the way it did. If the client wants a post-mortem, that conversation happens without you.

What we won’t do to save you time

Three shortcuts stay off the table even when a launch is behind schedule. We will not send you copy to publish. We will not wave a review through because the window is close. We will not ask you to drop the disclosure line to make the post read better.

Each one saves an hour at the moment it is most tempting, and costs the account something it cannot buy back. A review skipped on launch morning is how a wrong benchmark reaches a technical audience, and that audience does not forget a number that did not hold.

The honest alternative is to move the window. A launch that slips by a day is a scheduling note. A launch that ships with a claim nobody checked is a problem the creator carries in the replies for a week.

Two to three hours across the week, most of it on launch day. If a launch needs more than that from you, the brief is too complicated or the coordination is not happening.