What do you need from us for each release?
Whatever your team already produces: a ticket list, merged pull requests, a staging environment or a short demo recording. Where the source is unclear, we ask rather than guess.
Release ops
Release notes and release ops
This is for SaaS teams that ship often and document late: release notes written the night before from a list of ticket titles, a changelog that stopped being updated months ago, and screenshots of a UI that no longer exists. We take the documentation side of every release off your team's plate, covering notes, changelog, versioned docs and refreshed visuals, written from the source and checked before anything publishes.
Price
Retainer from $900/month
Response
Reply within 1 business day
After delivery
30-day fix window
Who it's for#who-its-for
- Product and engineering leads who want every release to ship with notes customers can read, without an engineer writing them at the last minute.
- Heads of support who hear about changes from customers first, and need release notes and help articles updated before the tickets arrive.
- Docs leads maintaining versioned docs by hand, who need someone to cut versions, update screenshots and keep the changelog honest.
- Product marketing leads who want release communication to look as considered as the product, without hiring a full-time writer for it.
It works best when releases follow some rhythm, even a loose one. If you ship continuously, the notes can be bundled into a regular digest instead of one note per deploy, and the retainer is scoped around that cadence. Either way, the notes stay tied to what actually shipped, not to what was planned.
What you get#what-you-get
A standing process, run every release, so documentation ships with the code rather than after it. It covers:
- Release notes written from your tickets, pull requests and demos, grouped by what changed for the customer rather than by team or ticket type.
- A changelog kept current in your repository or help center, in one consistent format.
- Versioned docs cut and updated whenever a release changes behavior, with the previous version kept for customers who have not upgraded yet.
- Screenshot and GIF refreshes for every page whose UI changed, with a list of what was replaced and where.
- Help center articles updated alongside the notes, so support links point at current instructions on release day.
- A review gate: a checklist and a named approver on your side, so nothing publishes unreviewed.
- If you want them, in-app announcement copy and a customer email summary drawn from the same notes.
Each note answers the questions customers actually have: what changed, who it affects, whether they need to do anything, and where to read more. Internal detail stays out unless it helps the reader, and breaking changes go at the top, never buried in a list.
How it runs#how-it-runs
- Setup. We learn the product, read your past notes, and agree a template, a voice and the review gate with you.
- Intake. Before each release, we get access to the release branch, the ticket list or a demo, whichever your team already produces. If nothing is written down, a short walkthrough call works too.
- Drafting. We write the notes and docs changes in a branch or draft, and flag anything we could not verify ourselves.
- Review and publish. Your approver signs off, and we publish or hand over for publishing on your release day.
- 30-day fix window. For 30 days after each release's notes go out, we correct errors in anything we wrote, at no charge.
The point of a retainer is that someone already knows the product when the next release lands. You do not brief a new writer every time, the notes read as if they come from one voice, and the changelog stays continuous instead of restarting whenever the person who kept it moves on. Screenshots are captured from a consistent test account and window size, so a refreshed image matches its neighbors and never shows a real customer's data.
Pricing#pricing
- Monthly retainer
- From $900 / month
- about €830
The retainer starts at $900 a month. The monthly price depends on how often you release, how much each release changes, how many products or versions the notes cover, and whether screenshots and GIFs need refreshing every cycle or only occasionally.
If a release is much larger than usual, such as a redesign or a new product, we tell you before starting and we agree how to handle the extra work, so the monthly price never changes quietly. If you already have a writer, the retainer can cover only the parts they do not reach, such as screenshots, versioning or the changelog.
Release notes can also ship in other languages through the localization service, with the translated notes passing the same review gate as the English ones.
Prices are in US dollars; the euro figures are approximate conversions for reference.
Frequently asked questions#faq
Can you write in our existing format?
Yes. We start from your past notes and changelog. If there is no format yet, we propose a template with a review gate, and we adjust it after the first few releases.
Who approves the notes before they go out?
Someone on your side, named during setup. Nothing publishes without their sign-off. The review gate is part of the service, not an optional extra.
Do you handle versioned docs in Docusaurus?
Yes. We cut versions with the Docusaurus versioning command, update the pages that changed and keep the version menu tidy. The same approach works in MkDocs with a versioning plugin.
Can you work from a staging environment behind SSO?
Yes. We can use a test account, a staging environment behind SSO, or screen recordings from your team, whichever your security policy allows.
Send us what you have
Send a link to your docs, an export, or a few lines on what needs to change. We reply within 1 business day with questions or a quote.