For product managers

Stop asking devs what shipped.

Every release becomes a clear summary in Slack or email — enriched with your Linear or Jira tickets and written in outcomes that sales, support and customers understand. Your devs change nothing.

Connect GitHub in 2 minutes · plans from $9/month · cancel anytime

# product-updates

changelogfa.stApp4:12 PM

v2.14 — Invoice payments and faster exports

Two things customers have asked for since spring are now live.

Pay by invoice

Annual-plan customers can request an invoice at checkout instead of paying by card.

Large exports no longer time out

CSV exports over 10k rows now complete reliably. Closes the 14 open support tickets about it.

Fixed: duplicate welcome emails

New users received the welcome email twice in some cases. Fixed.

4 internal changes (dependencies, tooling) were left out.

Example — written and sent automatically

Sound familiar?

Release notes are your job. Rewriting PR titles at 6pm on release day shouldn't be.

Sales asks what's in the release. Support asks if that bug is fixed. Engineering is already on the next ticket. The facts are in the pull requests and tickets — someone just has to turn them into something people can read, every single time.

What a release looks like

Written from the ticket, not the diff.

An example note — each point is traced back to the pull requests and tickets behind it. Dependency bumps and internal tooling are filtered out, not summarized. Detail level and tone adapt per audience: customers, sales, support.

What your team ships

9 commits since v2.13

feat: [PROJ-214] invoice payment at checkout

fix: csv export timeout on large datasets

fix: dedupe welcome email job

chore: bump dependenciesnoise · filtered

docs: update migration notesnoise · filtered

2 linked tickets

PROJ-214Annual customers can't pay by invoice

PROJ-198Exports over 10k rows time out

What you receive

# product-updates

changelogfa.stApp4:12 PM

v2.14 — Invoice payments and faster exports

Two things customers have asked for since spring are now live.

Pay by invoice

Annual-plan customers can request an invoice at checkout instead of paying by card.

Large exports no longer time out

CSV exports over 10k rows now complete reliably. Closes the 14 open support tickets about it.

Fixed: duplicate welcome emails

New users received the welcome email twice in some cases. Fixed.

4 internal changes (dependencies, tooling) were left out.

How it works

  • 1Connect GitHub (or GitLab / Gitea) — and Linear or Jira if you use them.
  • 2On every release, the merged work and linked tickets become a note — written from the intent in the tickets, not the commit messages.
  • 3It goes to Slack, email or a public changelog page, in the voice each audience needs.

Your developers install nothing and change nothing — no commit conventions, no extra fields, no process.

Your next release writes itself.

Two minutes to connect a repo. See a real note from your own releases.

Plans from $9/month · cancel anytime