← All posts Launches

A pre-launch checklist that survives contact with launch day

Twelve items, each with a named owner. Copy it, cut what does not apply, and never rebuild it from memory again.

MK Maya Kessler9 July 2026 · 8 min read

Why most launch checklists fail

Not because they are missing items. Because nobody owns the items. A checklist with twelve unassigned tasks is a list of things everyone assumes someone else is doing, and on launch morning you discover the overlap was smaller than you thought.

Every item below has a role attached. Change the roles to real names before you use it.

Seven days out

  1. Confirm the actual stock number: Ops. Not the Shopify number: the number after you subtract damaged units, pre-orders, and anything committed to a wholesale order.
  2. Set the stock floor and who can breach it: Founder. A number, and one name. Write it down where the team can see it.
  3. Agree the dispatch promise with the warehouse: Ops and Warehouse together. Support cannot invent this on the day.
  4. Write the support macro using that promise: Support. Exact wording, approved in advance.

Two days out

  1. Staff the warehouse for the window: Warehouse lead. Including the two hours after the sale ends, which is when the picking actually happens.
  2. Check the ad creative points at the right SKUs: Paid media. Surprisingly often it does not.
  3. Set the pause trigger and permission it: Paid media and Ops. Whoever watches stock must be able to pause spend without asking.
  4. Lower your alert thresholds for launch products: Ops. A threshold of 10 is useless when you sell 14 an hour.

Launch morning

  1. Open the room and pin the two decisions: Founder. Stock floor and support promise, at the top, visible.
  2. Assign the four watchers: Ops. Stock, spend, queue depth, and the floor. Four numbers, four names.
  3. Confirm everyone can actually see the counter: Ops. Someone always cannot, and it is always the person watching stock.
  4. Set a hard time for the post-launch reconcile: Founder. One hour after sell-out, before anyone leaves.
The one item people cut, and regret

Number 12. The reconcile is where you catch oversells while they are still cheap to fix. Skip it and you find them on Thursday, in a customer email, after the parcel has shipped.

After the launch

Write the recap the same day. Not a retro. A recap. What sold, what ran out first, what the queue peaked at, and which of these twelve items you skipped and got away with. The next launch is a copy of this document with the wrong assumptions corrected.

We wrote more about the day itself in how to run a flash sale without losing your team.

Keep reading

The five-minute rule for store alerts
Operations

The five-minute rule for store alerts

If an alert cannot be acted on within five minutes of arriving, it is a report, not an alert. Here is how to tell them apart and where each one belongs.

18 July 2026·6 min read
What a good escalation actually contains
Support

What a good escalation actually contains

Most escalations fail because they are a forwarded email. Four things to include so the person receiving it can decide immediately.

1 July 2026·5 min read
Why your low-stock threshold is wrong
Inventory

Why your low-stock threshold is wrong

A flat threshold across the catalogue guarantees you get alerted too late on fast movers and constantly on slow ones. Set it by velocity instead.

24 June 2026·7 min read

Run your store team in one room.

Free for teams up to five, and about two minutes to connect your store.