BoplisExplore the demo
Launch library

A small launch you can actually finish.

Choose a preview, a feature or a useful guide. Each kit gives you a preparation checklist, an announcement template and a way to follow up.

Three launch kits

Start with what people can try today.

These are original planning templates, not campaign results or promises of reach.

Launch a preview and learn from it

Use this when people can try part of the experience, but the full service is still being built.

Before you share it

  • List the interactions that work today.
  • Show a short demonstration of one of those interactions.
  • Label samples, unavailable features and what happens to edits.
  • Make the button lead to the preview it describes.
  • Ask one specific question about what the visitor tried.

Make the announcement your own

We are building [product] for [reader].
You can now try [working interaction] at [link].
Here is a short demo: [proof].
This is a preview: [important limits].
After trying it, tell us [one specific feedback question].
Download .md

After the launch: Record where people got stuck, what they expected and the next capability they asked for. Turn the clearest confusion into a page or interface fix before announcing more.

Announce one useful feature

Use this when an existing product changes one task in a way you can demonstrate.

Before you share it

  • Describe the previous task in the reader's words.
  • Verify the new behavior and who can use it.
  • Capture a screenshot or demo that proves the change.
  • Write one short post and one help note with the same facts.
  • Check the destination and have someone ready to answer questions.

Make the announcement your own

If you use [product] to [task], you can now [new action].
Previously: [old behavior].
Now: [verified behavior].
Example: [demo or concrete example].
Available to: [eligibility and limits].
Try it here: [destination].
Download .md

After the launch: Group replies into bugs, unclear instructions and new requests. Respond with what you know, update the help note and state any corrections plainly.

Share a practical guide

Use this when you have something useful to teach, even without a product release.

Before you share it

  • Answer one question your audience actually asks.
  • Include a worked example someone can follow.
  • Check outside claims and link the original sources.
  • Share one useful step in the announcement itself.
  • Invite questions that could improve the guide.

Make the announcement your own

A question we keep hearing: [question].
The first step is [useful answer].
We wrote a guide with [example or checklist]: [link].
It is for [reader and starting point].
What part of this task still trips you up?
Download .md

After the launch: Add useful questions to the guide, date meaningful revisions and reuse the lesson in your next weekly plan. Keep any audience figures separate from claims about business results.

Keep a simple launch record

Write down what you shared, where it went and which question it was meant to answer. Add feedback and measurements only when you have them. This keeps the next decision tied to what happened.

Launch and date: [name, date]
Audience and goal: [reader, intended action]
What went live: [links]
What people asked: [questions]
Verified measurements: [figures, definitions, dates]
What remains unknown: [gaps]
Next change: [task, owner, review date]
Need the full timeline?

The Launch Handbook.

Plan preparation, launch day and the week after with four phases and sixteen steps.

Read the handbook