The items nobody
remembers to assign.

Product readiness: Feature complete against the agreed scope, the bug bar met, performance acceptable under real load, the flag or release mechanism tested, and a rollback that somebody has actually tried rather than assumed.

Marketing readiness: Positioning agreed, landing page live, announcement written, screenshots and video produced, social scheduled, and the paid plan set up. Most of these depend on product being finished, which is why they compress at the end.

Sales enablement: Pricing confirmed and in the system, the deck updated, objection handling written, and the team briefed before customers hear about it rather than after.

The dependency between them: Every item in marketing and sales is waiting on something in product. Making that explicit is what turns a compressed final week into a planned sequence.

Support readiness: Help articles written, macros in place, the escalation path agreed, and someone briefed and available in launch week. Support is the team that meets the consequences of everything the others missed.

Legal and billing: Terms updated if the offering changed, invoicing and tax handling correct for the new plan, refund and cancellation behaviour defined, and any consent or disclosure requirements checked. Dull, and each one can stop a launch on the morning.

Analytics instrumentation: The events that will tell you whether this worked, in place before launch rather than added in week two. A launch you cannot measure produces opinions instead of a decision about what to do next.

Operational readiness: Monitoring and alerting, who is on call, what triggers a rollback, and who has the authority to call it at nine on a Saturday.

Generate the complete list: Describe the launch and the AI produces every conventional item across all seven areas, which is the fastest route to a list that is not just the things you already had in mind.

Find the gaps in your own board: Ask which cards have no owner, which are blocked by something not on the board, or what a launch of this kind usually includes that yours does not.

It proposes, you decide: Storyflow structures and suggests; whether an item genuinely applies to your launch is your call, and deleting the ones that do not is part of making the list yours.

Re-generate when the scope changes: Add a region, a plan tier, or a platform, and ask the AI what that adds. Cards you have owned and marked stay exactly where they are.

Launch day itself: The order things go live in, who publishes what, what gets checked in the first hour, and the specific numbers that would make you pause rather than press on.

The follow-up: The second email, the case study, the paid push once the organic wave has passed. Launches that spend everything on day one go quiet on day three.

The review: Keep the board and mark what actually happened. The most useful output of a launch review is the list of items you did not have, and that list only exists if the original board is still there.