One release, thirteen announcements

A release is one event, but it needs to be told a dozen different ways: technically for your docs, warmly for your users, briefly for the timeline, plainly for the people who will never read a commit. Shipnote writes thirteen versions of the same truth. Here's how different builders actually use them.

The solo founder's loop

You shipped all week; Friday is announcement day. Open the release, and the Changelog, X thread and Product Hunt update are already drafted from your commits. Read them over coffee, nudge the thread to be a little more excited, publish. Your hosted changelog page updates itself, the thread goes out, and you are back in the editor before the coffee is cold. The marketing department was you, for ten minutes.

The SaaS team's single source of truth

Teams lose more time to "what shipped?" than to shipping. With an automation set to draft on every push, each deploy produces the same story told three ways: Release notes for the docs, an Email for the customer list, and the Standup output, a spoken-word summary the team lead reads out in the morning meeting instead of scrolling the merge log. Support stops being surprised by the product.

The community game, fed weekly

A live game's community measures love in patch notes. The Discord output is built for it: short sections, bullets, the kind of post players actually read pinned in #announcements. Connect several channels (one per server, or one per language community) and pick which get each release. Telegram, SMS and WhatsApp via Twilio cover the communities that don't live on Discord.

The one everyone forgets: the non-technical reader

The newest output is the one we're most attached to: Plain English. No jargon, no APIs, no "refactored the caching layer". Just what got better, in everyday words, with the benefit first. Send it to your co-founder who does sales, paste it into the company all-hands notes, or show it to the customer who asked "so what did I get for my subscription this month?" It's the same release, translated for the people the other twelve formats forget.

Written once, everywhere it needs to live

Every output is editable, regenerable section by section, and downloadable as Markdown or a print-ready PDF for the places no integration reaches. And because publishing is per-destination, you can send Discord today, the email tomorrow, and hide a release from the public page entirely. Each channel keeps its own record of what was sent where.

One release, thirteen tellings, one afternoon saved. That's the whole product.