Product launch checklist
A product launch checklist from two weeks out to the week after: the pitch, the assets, launch day and the review most launches skip.
A launch is a deadline with a lot of people watching. The work isn't hard, but there's a lot of it, and the expensive mistakes are the forgotten ones: a broken signup link, an announcement with the wrong price, nobody watching support on the day.
This checklist runs from two weeks out to a week after. It's a good one to share with an agent: drafting the announcement, writing answers to likely questions and summarising feedback are exactly the tasks it can pick up.
Two weeks out
One week out
Launch day
Week after
What you type is saved in this browser only. Nothing is sent anywhere.
Use it in Done
- Press Copy and open Done. The template goes onto your clipboard as a list.
- In Done, open Settings → Data → Import and choose Paste a list.
- Paste it, check the preview and import. The heading becomes a project called “Launch”, and each line becomes a task.
No account yet? Sign up free first; the import is waiting in Settings.
How to use this template
- Set the launch date and work back two weeks.
- Get the pitch and the assets done first — everything else uses them.
- Run the launch-day list in order on the day.
- Do the week-after list. That's where you learn what to build next.
Hand it to your agent
Connect Done to Claude, ChatGPT or any MCP client (it takes a minute), then paste this prompt. Your agent works through Done's own tools, under the same approval gate as everything else.
Fill in the parts in [brackets] before you send it.
Work only through the Done MCP connector, on my Done account. I'm launching [what] on [launch date]. 1. Call create_project for the launch, then create_task for one parent task called "Launch [what]" in it, with due_date set to the launch date. 2. Call propose_plan on that task with the checklist below as its steps. Give the steps you can do yourself assignee "claude": drafting the announcement and the email, writing answers to expected questions, checking links, summarising feedback afterwards. Leave publishing, sending and anything that needs my accounts to me. 3. Call render_plan so I can see who does what. 4. Anything outward-facing — a post, an email, a reply to a customer — goes to me through ask_decision first. Don't publish or send anything yourself. Two weeks out: - Write the one-sentence pitch and who it's for - Decide the launch date and channels - Draft the announcement post and email - Prepare screenshots and a short demo One week out: - Test signup and payment end to end - Check every link in the announcement - Line up people to share it on the day - Write answers to the questions you expect Launch day: - Publish the announcement - Send the email - Post on your channels - Watch support and reply fast - Fix anything broken before you promote further Week after: - Thank everyone who helped - Summarise the feedback and what people asked for - Compare the results with what you expected - Decide what ships next
Tools this prompt calls
create_projectcreate_taskpropose_planrender_planask_decision
More templates
Your list, with an agent on it
Sign up with just an email, import a template, and hand the first task to Claude or ChatGPT.