Skip to content

Launch Readiness Brief

Example prompt: "When a Linear initiative moves to 'Ready to Launch', run through our pre-launch checklist — release notes drafted, help docs updated, support team briefed, marketing scheduled — and post a status report in our #launches Slack channel with what's done and what's still outstanding."

The Problem

Every launch has a list of things that need to be true before it goes out — the release notes, the help docs, the support team having seen the demo, the marketing post being scheduled — and every launch is the day a PM realises one of them isn't done. The checklist exists somewhere, sometimes in a Notion template and sometimes only in the PM's head, and the act of walking it the morning of launch is exactly the kind of work that gets dropped under deadline pressure. Things ship that the support team hasn't seen, and the post-launch tickets show it.

How GloriaMundo Solves It

We build a workflow triggered when a Linear initiative moves into the "Ready to Launch" state. Integration steps check each item on the launch checklist in parallel — does a release notes draft exist in the Notion "Release Notes" page for this initiative, has the relevant help docs page been edited in the last 14 days, is there a "support briefing" message in the #cs Slack channel referencing the initiative, is there a scheduled draft in the marketing tool referencing it. A code step compiles the results into a green/red checklist with the missing items highlighted. An integration step posts the brief to the #launches Slack channel as a threaded message tagging the PM, and a final integration step adds a comment to the Linear initiative with the same status so the audit trail lives on the work item. Glass Box preview shows the proposed checks and the message body before it runs.

Example Workflow Steps

  1. Trigger (webhook): Fires when a Linear initiative moves to the "Ready to Launch" state.
  2. Step 1 (integration): Read the initiative's title and description from Linear.
  3. Step 2 (integration): Check whether a Notion "Release Notes" page has a section for this initiative.
  4. Step 3 (integration): Check whether the relevant help docs page in Notion has been edited in the last fortnight.
  5. Step 4 (integration): Search the #cs Slack channel for a recent message referencing the initiative name or its key.
  6. Step 5 (integration): Check the scheduled marketing posts in Mailchimp for an item referencing the initiative.
  7. Step 6 (code): Compile the results into a green/red checklist with a one-line note per item.
  8. Step 7 (integration): Post the brief to the #launches Slack channel as a threaded message tagging the PM.
  9. Step 8 (integration): Add the same checklist as a comment on the Linear initiative for the audit trail.

Integrations Used

  • Linear — source of the trigger and where the audit comment lands
  • Notion — where release notes drafts and help docs live
  • Slack — where the support briefing is checked and the launch readiness brief is posted
  • Mailchimp — where scheduled marketing posts are checked

Who This Is For

Product managers shipping more than one launch a month where the checklist is real but inconsistently walked, and where a missed pre-launch step shows up as a spike in support tickets the day after. Especially useful at scale-ups with a single PM running several launches and no dedicated launch manager.

Time & Cost Saved

Walking a pre-launch checklist by hand — checking four or five tools, chasing the owner of each item, writing up a status — takes a PM 30-60 minutes on launch day, which is exactly when they have least time to do it. This workflow keeps the check consistent and pre-empts the morning-of scramble; the PM intervenes only on the red items the brief surfaces.