A launch plan scaled to the launch, and a go/no-go nobody can quietly skip.
Two things go wrong with launch checklists: the template is either too heavy for a minor release or too thin for a major one, and the go/no-go happens in someone's head. This recipe fixes both. AI generates a checklist scaled to the launch tier and scoped to the channels you actually selected, grouped by workstream with suggested days-before-launch. Then a daily sweep watches every in-progress launch and, once it enters the readiness window, demands an explicit human go or hold.
Free · no credit card · you connect your own apps
Installing provisions each one, wired together and ready to run.
Where launch owners kick off a launch: product, tier, channels, target date, owner. Publishing it auto-creates the Launches response sheet, the single system of record.
On kickoff: the AI planner generates the tailored checklist, posts it as one board card, stamps the launch row with the plan and card link, and notifies the team.
Runs daily. Once an in-progress launch is inside its readiness window, it requests a human go/no-go sign-off and records the decision.
You connect your own accounts. Swap any app that offers an alternative at install.
Creates one card with the full launch checklist on your launch board. Swap for Jira, Linear, or Notion.
Notifies the launch team of the plan and requests/announces the go/no-go decision. Swap for Telegram or Discord.
A launch owner submits the New Product Launch Kickoff form: product, tier, channels, target date, and the owning DRI. Submitting it fires the kickoff workflow automatically. Naming the DRI on the form is deliberate: every launch has exactly one person accountable, from the first minute.
A TinyGPT step generates a tailored, ordered checklist scaled to the tier and scoped to the channels you selected, grouped by workstream, with a suggested days-before-launch for each task. A tier-three feature flag doesn't get a tier-one plan, and a launch with no paid channel doesn't get paid-channel tasks. You start from a real plan instead of a blank doc or a bloated template.
The full checklist is posted as one Trello card on your launch board with a due date, and the launch's row on the Launches sheet is stamped with the plan, the task count, and the card link. One sheet, one card, no second tracker. Swap Trello for Jira, Linear, or Notion at install.
Your launch Slack channel gets the plan summary and the board link, so work starts the same hour the launch is kicked off rather than after the first standup. Swap Slack for Telegram or Discord.
A daily sweep checks every in-progress launch against its target date. Once a launch is within the readiness window you configured, it triggers a human go/no-go request. The sweep is what makes this reliable, it doesn't depend on anyone remembering the date.
The launch owner either approves, marking readiness approved, or holds, in which case the launch stays in-progress and comes back on tomorrow's sweep. Either way the team is told the decision. Nothing ships on an assumption that someone else had checked.
Everything it creates is an ordinary form, table and workflow in your workspace. Edit any of it after install. Nothing is locked.
