Launch intelligence is in early access. Become a design partner

Use casesChangelog and email

A changelog entry and a release emailfor every release you ship.

Both are drafted from the same cited launch brief as your social posts. The release email goes only to people who opted in, once each.

Changelog entrychangelog

v2.4.0 · Billing

Recurring invoices

Set a schedule once and Acme sends the invoice every cycle. Pick monthly, quarterly, or yearly, and pause any time from the invoice page.

  • – New: schedules on any invoice
  • – New: pause and resume a schedule
  • – Limitation: one schedule per invoice
whatChanged.0limitations.0
Email172 / 5,000

Recurring invoices are here

Set a schedule once and Acme sends the invoice every cycle. Pick monthly, quarterly, or yearly, and pause any time from the invoice page. One schedule per invoice for now.

whatChanged.0limitations.0

Changelog

The changelog says what changedand what it doesn't do yet.

It covers what changed and why it matters. It also lists limitations, because the launch brief has a limitations section and the entry cites it.

01

The entry

A heading up to 100 characters and an entry up to 4,000. Written to the launch brief, so it agrees with every post about the same release.
  • What changed, from the launch brief
  • Why it matters, from the release
  • Limitations, stated plainly
  • No hype words, no unsupported claims
Changelog entrychangelog

v2.4.0 · Billing

Recurring invoices

Set a schedule once and Acme sends the invoice every cycle. Pick monthly, quarterly, or yearly, and pause any time from the invoice page.

  • – New: schedules on any invoice
  • – New: pause and resume a schedule
  • – Limitation: one schedule per invoice
whatChanged.0limitations.0

Email

Each subscriber who opted ingets the email once.

A subject up to 90 characters and a body up to 5,000. One template renders both the HTML and the plain text, so the two match.

  • consent · per workspace

    Consent first

    Recipients are looked up at send time, so a late unsubscribe is honored. Unsubscribing from one company's emails doesn't affect another's.
  • POST + GET unsubscribe

    One-click unsubscribe

    The one-click unsubscribe Gmail and Yahoo require, plus a footer link for every other client. Links are signed, so nobody can unsubscribe someone else.
  • unique (message, email)

    Exactly once

    Each address gets one row under a unique constraint. A retry after a partial failure reaches only the people who have not received it.
  • suppressed ≠ unsubscribed

    Bounces respected

    Hard bounces and complaints stop sending even if the person never unsubscribed.
  • approved only

    Approved releases only

    Shots emails only approved releases, and refuses to send to an empty audience.
  • markdown → text

    Plain, safe content

    Release text is flattened to escaped plain text, so nothing in a release can run in an inbox.

Questions

Anything else? Talk to us.

Is this a newsletter tool?
No. It emails release news to people who opted in. Drip campaigns and newsletters are out of scope.
Can I import my subscriber list?
Yes, with our help during early access. Addresses are normalized on import, and re-importing never brings back someone who unsubscribed.
Is release email available now?
Sending is built and running. It is part of early access while the writing screens are finished.

Related

Read how publishing works,how a feature launch runs, and Shots for developer tools.

Send your next changelogto the people who asked for it.