Ship notes: how we write changelogs at Klow (and why you should too)

Most teams treat changelogs like a chore. A bullet list dumped into a Notion doc that nobody reads. That is a missed opportunity. A well-written changelog is a trust signal, a retention tool, and a growth lever — all in one.

At Klow, we publish weekly ship notes every Friday. They go to the blog, our Telegram channel, and a dedicated changelog page. Here is the exact format we use, why each section exists, and how you can steal it.

The template

Every changelog follows the same four sections. Consistency matters — your readers should know exactly where to look for what they care about.

🚀 New

Features, capabilities, or integrations that did not exist last week. Lead with the user benefit, not the implementation detail. Bad: "Added BullMQ repeatable job for digest." Good: "Your agent now sends you a daily summary of everything it did overnight."

✨ Improved

Polish, performance gains, and UX refinements on existing features. These show your product is getting better even when you are not shipping headline features. "Dashboard loads 40% faster on mobile" matters more than people think.

🐛 Fixed

Bugs squashed. Be specific and honest. Users respect transparency. "Fixed a bug where wallet balance showed $0 during RPC outages instead of an error message" builds more trust than hiding it.

🔮 Coming next

A short teaser of what is in progress for next week. One to three items max. This keeps people coming back and gives them something to look forward to. Never promise dates — promise direction.

Example entry

Here is what a real Klow changelog entry looks like:

Why this format works

Four sections. No jargon. User-facing language. The reader knows in 30 seconds whether this week matters to them. The "Coming next" section creates a reason to check back.

We publish on Fridays because it gives the team a natural sprint cadence. The changelog is the artifact that proves the week happened. If the changelog is empty, the week was wasted.

Tone guidance

• →Write like you are talking to a smart friend, not filing a report.
• →Lead every bullet with the benefit, not the technical mechanism.
• →Be specific — "40% faster" beats "improved performance."
• →Be honest about bugs. Users already know your product is not perfect.
• →Keep the whole thing under 300 words. Changelogs are not blog posts (ironic, we know).

Distribution

A changelog nobody reads is a changelog that does not exist. We push ours to three channels: the blog (SEO value, permanent record), Telegram channel (instant reach to active users), and a pinned message in our community Discord. Pick the channels where your users already are.

Want to see what Klow ships every week? Watch our agents build in real-time at klow.ai/live, or read about how our AI agents review their own code as part of the shipping process.