When you’d need it
A launch is coming and the decision-makers need context before the meeting, not during it. You have the thinking in scattered notes, but no one will read ten slides async — they'll read one clear page.
A launch is coming and the decision-makers need context before the meeting, not during it. You have the thinking in scattered notes, but no one will read ten slides async — they'll read one clear page.
Copy directly for any go/no-go launch or feature decision. For a post-launch retro, keep the narrative-plus-recommendation shape and swap the workflow frame for a results frame.
Same structure, your scenario — pick a starting prompt.
A launch brief is a short document that gives stakeholders the context, plan, and recommendation for a launch so they can align or decide before a meeting. This example shows that as a four-page editable memo.
This is a document-shaped artifact, which is the right format when the reader needs to absorb context alone. You can ask Toft to turn the same content into a deck if you need to present it live.
Yes. The example is designed for messy input — paste your notes and Toft organizes them into a readable brief with a narrative, a workflow, and a recommendation.
One to four pages. Long enough to carry the argument and the plan, short enough that busy stakeholders actually finish reading it.
Yes. Ask Toft to reformat the brief into a deck, a one-pager, or a social pack while keeping the core content.
Yes. The document and its embedded diagram are editable artifact elements you can refine by prompt or by hand.
Describe what you need. Toft returns the finished, editable artifact.