Launch intelligence is in early access. Become a design partner

Use casesChangelog and email

Release notesthat reach people.

Every release gets a changelog entry and an announcement email, drafted from the same cited spec as the social posts. Email goes only to people who asked for it, 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

An honest recordof what shipped.

The changelog is the record. It says what changed, why it matters, and what it does not do yet, because the spec has a limitations section and the copy cites it.

01

The entry

A heading up to 100 characters and an entry up to 4,000. Written to the spec, so it agrees with every post about the same release.
  • What changed, from the spec
  • Why it matters, from the brief
  • 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

To people who asked.Once each.

A subject up to 90 characters and a body up to 5,000, rendered as HTML and plain text from one template so the two never drift.

  • consent · per organization

    Consent first

    Recipients are resolved at send time, so a late unsubscribe is honored. Leaving one company’s announcements never silences another’s.
  • POST + GET unsubscribe

    One-click unsubscribe

    The one-click unsubscribe Gmail and Yahoo require, plus a footer link for every other client, 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

    Only approved release documents can be announced, and an empty audience is refused rather than silently accepted.
  • markdown → text

    Inert content

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

Questions

Anything else? Talk to us.

Is this a newsletter tool?
No. It announces releases 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?
Delivery is built and running. It is part of early access while the authoring screens are finished.

Release notespeople actually read.