Shipped means announced.
The last mile of every feature is telling the people who asked for it. Damper drafts the changelog from your shipped tasks, emails the voters and posts the release — you just review and hit publish.
Changelogs that write themselves.
When a roadmap task is marked done, its entry lands in a draft changelog — title, description and the work behind it included. Add a version, tweak the wording, publish.
- Built from real work — shipped tasks flow in automatically, nothing retrofitted.
- Draft first, always — nothing goes public until you say so.
- Agents can add entries — completed tasks append themselves via MCP.
Voters hear it first.
Publish an entry and Damper works through the fan-out for you: everyone who voted or submitted linked feedback gets an email, and your release goes out on X.
- Targeted notifications — only the people who asked about that feature.
- X / Twitter auto-posting — connect your account once, releases post themselves.
- Engagement you can feel — “you shipped the thing I asked for” is the strongest retention loop there is.
Stop shipping silently.
Every release is a reason to email the customers who care. Damper makes that a byproduct, not a chore.
Where this fits in the loop.
Collect
Catch feedback where it happens — in your app, in Slack, on a call — and land it in one clean inbox.
Prioritize
Rank requests by who is asking. Votes are weighted by plan, so paying customers move the roadmap.
Build
Hand the top task to your AI coding agent with the rules that govern it — and get proof when it is done.
Ship
Shipped work becomes a changelog entry, and everyone who asked for it hears first.
Around the loop
Docs, uptime, errors and team access — the product ops that sit next to the loop.