Release notes are often the only place customers hear about the work you do. Yet most of them read like commit messages: technical, terse and written for the people who already know the context.
Lead with the outcome
Start every entry with what the customer can now do, not what you changed. “Export reports to PDF in one click” beats “Added PDF renderer to reporting service” every time.
Show, don’t list
A ten-second clip or a single screenshot explains more than three paragraphs. We add one visual to every meaningful update and skip it for small fixes.
One sentence on the benefit
One visual for anything customers can see
A link to the docs for anyone who wants depth
“Customers started replying to our release emails. That had never happened before.”
— Emily Carter, PM Lead at Kitebase
Liftoff’s AI release notes follow the same rules: they draft from merged work, rewrite in plain language and leave the final polish to you.
