Launch intelligence is in early access. Become a design partner

Use casesFeature launches

Ship the feature.Say so the same day.

A feature is not launched until people hear about it. Send the release from GitHub or describe it in a sentence, and get a cited brief, real screenshots, and posts for every channel the same day.

X134 / 280

Stop rebuilding the same invoice every month. Recurring invoices are live in Acme: set the schedule once and every cycle sends itself.

Invoices that send themselves

Monthly
Quarterly
Monthly
Yearly
capabilities.0whatChanged.1
LinkedIn147 / 3,000

The third invoice of the month is the one that gets forgotten. Recurring invoices fix that. Pick monthly, quarterly, or yearly, and pause any time.

problem.0capabilities.1
Product Hunt59 / 260

Acme recurring invoices

Set a schedule once and Acme sends the invoice every cycle.

summary

Walkthrough

From mergeto scheduled posts.

Six steps from merge to scheduled posts. Two of them are decisions only you can make.

  1. 01

    The release arrives

    A GitHub release fires your webhook, or someone fills in the release form with the pull request and changelog links.

  2. 02

    The spec drafts itself

    Problem, audience, what changed, capabilities, proof, and limitations, each claim citing the pull request, the changelog, or the brief.

  3. 03

    You answer what it could not

    Gaps show up as open questions instead of invented claims. Your answers join the trusted brief.

  4. 04

    You approve a plan

    Channels, angles, and the assets to capture, split into teaser, launch day, and follow-up.

  5. 05

    Visuals and copy arrive together

    Real screenshots framed on brand, and posts for every channel that cite their claims and fit their limits.

  6. 06

    Approve all, then schedule

    Approve every post in one click, or fix the one that is off. A publisher schedules the approved posts.

New releaseAcme Billing

Release title

Recurring invoices

Why it matters

Bill repeat customers without rebuilding the invoice.

Source links

github.com/acme/billing/pull/452

acme.com/changelog/recurring-invoices

github · release.published201 · signature ok
Launch specv2 · draft

Problem

Finance teams rebuild the same invoice every month.S1

What changed

Invoices repeat on a schedule you set once.S2brief

Open question

How many beta teams used it? No source says.

Answer

What you get

One release.The whole kit.

Everything a feature announcement needs, built to the same spec, so the X post and the changelog never disagree.

  • spec · cited

    A launch brief

    The cited spec doubles as the internal brief for support and sales.
  • 16:9 · 1:1 · 4:5 · 9:16

    Assets in every format

    A hero, a feature shot, a social card, and a story, from your real product.
  • X · LinkedIn · Instagram

    Social posts

    Several angles per channel, each within the channel limit and in your voice.
  • Product Hunt

    A launch listing

    A tagline and description that fit Product Hunt, ready to paste.
  • changelog

    A changelog entry

    What changed, why it matters, and what it does not do yet.
  • email

    A release email

    A subject and body for subscribers who asked to hear about releases.

Questions

Anything else? Talk to us.

What if nobody wrote release notes?
Link the pull request. The spec reads its title, description, and the release page, and asks you about anything it cannot support.
Can I launch a small fix too?
Yes, and you should keep it small. Pick fewer channels in the plan, or approve only the changelog entry.
What if the screenshot shows the wrong screen?
Each asset in the plan names the page to capture. Edit the plan, or revise that one design, and leave the rest alone.

Ship it Tuesday.Announce it Tuesday.