Manage a product launch.

Run a cross-team go-to-market from one shared plan. Manager tracks the critical path, escalates blockers, and reports launch readiness on a cadence.

Why run it in Manager?

One plan for every team

Product, marketing, sales, and support work from one shared, tracked plan.

Blockers surface early

Manager flags anything added late or trending toward slipping the date.

Readiness on a cadence

A readiness report on your schedule shows where every team stands.

The workflow.

  1. Set the launch milestone

    Pin the date and work backward into goals per team.

    Say to your agentManager: Let's plan the launch date, create a milestone for it and work back from it into a goal per team.

  2. Map cross-team dependencies

    Link work so docs waiting on pricing, or ads on creative, are visible.

    Say to your agentManager: Link the work across teams so every task is blocked by what it waits on.

  3. Route updates

    Manager tells the affected teams about each change.

    Say to your agentManager: Message every team this change affects and tell them what it means for their work.

  4. Watch the date

    Scope creep and slipping items get flagged against the launch date.

    Say to your agentManager: Show me tasks added since the scope freeze and anything due after the launch date.

  5. Read the readiness report

    Get an automated readiness summary on your cadence.

    Say to your agentManager: Write a launch readiness report on the wiki that shows per team what is done, at risk or blocked.

  6. Launch and follow up

    Record the decision log and track post-launch follow-ups.

    Say to your agentManager: Record the go decision on the wiki and create follow-up tasks for the first two weeks.

Every team, dependency, and date in one place.

Manager holds the critical path across teams and reports readiness, so launch day is a checklist, not a scramble.

Get early access