For your workProduct launch
A product launch plan that every team can see.
Product, marketing, sales and support work from one board, with every item dated back from launch day. Claude drafts the release notes, the support FAQ and the sales one-pager from the spec, and flags what has no owner.
A month of Premium free, no cardAgents never take a seat
How launches drift.
The plan is a slide, the checklist is a spreadsheet, and the real status is in chat.
Support hears about the launch after the customers do.
We relearn the same lessons every launch.
Every team on the same date, nothing without an owner.
Dates everything back from launch
A field for days before launch puts each item in place on the Timeline. Move launch day and you can see what has to move with it.
Drafts from the spec
Add the spec, the positioning doc and the pricing sheet. Claude drafts release notes, FAQs and briefings from them, quoting where each claim came from.
Runs the launch checklist
Positioning, assets, claims check, briefings, go or no-go. The workflow stops at each check and waits for the person who owns it.
Catches you up on the channel
Catch up summarises a busy launch channel, and any message can become a task or a decision on the board.
Start from a sentence. Keep what fits.
Say what the project is for and Claude drafts it: the statuses, fields and views below, ready to rename, switch off or add to.
Statuses
Fields
Views
- Positioning from the brief
- Assets drafted for each channel
- Product lead checks the claims (a person checks)
- Sales and support briefed
- Go or no-go (a person checks)
- Post-launch notes
Launch checklist, as a workflow. The clay steps stop for a person. How workflows work
Before you set the date.
What goes in a product launch checklist?
Positioning, pricing, web pages, release notes, emails, sales and support briefings, and a go or no-go. Projectify drafts one from a sentence about your launch, and you rename or drop any part.
Will Claude publish anything?
No. Claude drafts the copy and the briefs, a person checks the claims, and your team publishes from its own tools.
Can engineering keep its own board?
Azure DevOps, Trello and Monday sync both ways, and GitHub pull requests show on their tasks, so the launch board sees engineering’s status without a second update.
Can we reuse the plan next time?
Yes. Save it as a workflow and run it for the next launch; the steps and checks carry over.
Plan the next launch on one board.
A month of Premium free, no card, and your launch plan drafted from one sentence.