Release notes are the only documentation a company publishes on a schedule, which makes them the clearest signal customers have about whether anyone is home. A steady stream of specific, well-written notes tells an evaluator the product is alive and the team is disciplined. A gap of four months followed by "various improvements and bug fixes" tells them something else entirely, and enterprise buyers read the changelog during evaluation for precisely this reason.

We edit what product and engineering teams produce — release notes for web, mobile and desktop products, API changelogs and version histories, upgrade and migration guides, deprecation notices and sunset schedules, breaking change announcements, patch and hotfix communications, in-product what's-new panels and modals, customer email announcements accompanying releases, internal release communications for support and sales teams, known issues lists, and the release note templates and conventions that keep all of the above consistent. Our editors check that each entry says what changed from the reader's position rather than the codebase's, that breaking changes are unmissable, and that the note answers the only question the reader actually has: does this affect me?

The upgrade guide attached to a major version is where good release writing pays for itself many times over, because the alternative is a support queue full of people stuck halfway through a migration. Most upgrade guides are organised as a list of changes, which forces every reader to work out for themselves which ones apply. We restructure them so the first section is a short checklist that tells a reader in under a minute whether they are affected — the specific configuration, feature or API call that triggers each concern — followed by the changes in the order they must be made, with a working before-and-after for each. We insist on stating what happens if a step is skipped, and on giving a rollback route, because teams that cannot see a way back postpone the upgrade indefinitely and end up on an unsupported version, which costs you more than the migration ever would.

Everything you send is treated confidentially, including notes for unreleased versions and deprecation plans not yet announced. Whether you are a small team writing notes in the last hour before a release, a company establishing a consistent format across several products, or a group preparing a major version announcement that needs to go well, we can make the writing quick to scan and genuinely informative.