Coordinate a product launch across teams
Run a launch as one process — drafts assets and routes each step to the team that owns it.
A product launch workflow fails in the handoffs: engineering ships, marketing finds out late, sales learns from a customer. This workflow runs the launch as one process with every team in it. The agent drafts the assets, tracks readiness in Linear and GitHub, and routes each step to the team that owns it. Engineering approves the technical claims. Marketing approves the copy. Nothing goes out half-approved.
What does this workflow do?
Kick off the workflow when a launch gets a date. The agent builds the launch checklist from your own launch history and templates in Notion, then starts working through it: drafting the changelog entry, the announcement post, the sales enablement note and the help doc update, all grounded in what it knows about the feature from Linear tickets, GitHub PRs and spec documents.
The collaborative part is the point. Each item routes to its owner for approval. The agent asks engineering to verify the technical description ("Is it accurate to say sync is now real-time?"), asks marketing to sign off on messaging, and asks support whether the help docs cover the new flows. Approvals happen in Slack. If someone's answer changes an asset, dependent assets update and their approvers get pinged again.
How does it work?
- Kick off with the feature and the date. The agent pulls context from Linear, GitHub and your specs, and builds the launch plan from your team's launch template.
- It drafts every asset. Changelog entry, blog announcement, in-app copy suggestions, sales one-pager, support macro updates. Each draft cites its sources.
- It routes approvals by role. Technical claims go to the engineers who built the feature. Messaging goes to marketing. Pricing mentions go to whoever owns pricing. Each approval is a Slack message, answerable in seconds.
- It chases what's missing. Unanswered approvals get a reminder. Open questions become information requests to the person who knows. The launch dashboard shows exactly what's blocking.
- It ships on approval. Approved assets get published to their destinations: the changelog to your site pipeline, the doc to Google Docs, the internal announcement to Slack. Anything unapproved stays held.
Why run launches this way?
Launch coordination is mostly asking people things at the right time: is this claim true, is this copy final, is this doc updated. The agent does the asking, tracks the answers and keeps every asset consistent with them. No spreadsheet of checkboxes, no "who owns this?" thread.
The workflow's memory makes the second launch better than the first. It learns which approvals your team actually needs, which assets you always produce, and what feedback each approver repeats. The launch checklist stops living in one marketer's head.
Works with
Slack, Linear, GitHub, Notion, Google Docs. Kick off on demand for each launch.
Frequently asked questions
Can different teams approve different steps?
Yes. That's the core of the template. Each checklist item has an owning role: engineering approves technical accuracy, marketing approves messaging, sales confirms enablement. Approvals happen in Slack and are recorded on the launch.
What happens if an approver changes something?
The agent propagates the change. If engineering corrects a technical claim, every asset using that claim updates and its approvers get a re-approval request for the delta only.
Where does the agent get the feature details?
From your connected tools: Linear tickets, GitHub PRs and merged code descriptions, spec docs in Notion or Google Docs. Every drafted claim links to its source, so approvers verify quickly.
Does it work for small launches too?
Yes. The checklist scales down. A minor feature might be one changelog entry and one engineering approval. You choose the asset list at kickoff, and the workflow remembers your defaults per launch size.
Can it handle a launch calendar with multiple launches running?
Yes. Each launch is its own workflow run with its own dashboard. A weekly status report template can roll them up if you run many in parallel.