Close the loop at scale
One entry links twelve shipped posts, and everyone who asked for any of them gets one email.
Private previewWorkspaces are by invitation
Skip to content01Collect
Feedback boardsBoards that ask for exactly what your team needs to act.Votes, comments & mentionsOne vote per person, threads with mentions, and notes only your team sees.In-app widgetFeedback from inside your product, from customers who are already signed in.02Understand
Merge & duplicatesTen posts asking for the same thing become one, with every vote kept.User segments & revenueProSee which requests your biggest customers want, in dollars.InsightsWho reads, what's rising, and whether you answered.HeedPost AIPlus and ProTags, duplicate judging, drafts, summaries, themes and Ask, each with its own switch.03Ship and tell
Roadmap & statusesMove a post and everyone who asked hears, in your own status words.ChangelogRelease notes linked to the requests behind them, mailed to everyone who asked.Notifications & digestThe right email to the right person, and a switch for every one.04Run it
Activity logEvery change, who made it and when, a day at a time.Team, roles & sign-inUnlimited teammates, clear roles, and sign-in your way.Branding, domain & languagesYour logo and colour, your own domain, and 21 languages.ImportMove in from Canny, Featurebase or UserJot, with nobody emailed.05Connect
Slack & issue trackersPlus and ProSlack threads, and issues in Linear, Jira, GitHub or ClickUp that move posts back.MCP serverPlus and ProYour AI agent can read, file, vote and ship, as you.REST APIPlus and Pro27 operations and one key: build anything on top of your feedback.WebhooksPlus and Pro110 events, signed and retried, the moment they happen.Chapter 3 · Ship and tell · Changelog
Write what changed, link the posts it answers, and publish. Everyone following those posts gets one email about the request they made, and anyone subscribed to your changelog gets every release.
Try it
Link posts and watch who will hear. People who followed more than one are counted once.
Step by step
Give it a title and tell the story in markdown.
New, Improved, Fixed, or labels in your own words.
Pick the requests this release answers.
Followers of those posts, and everyone subscribed to every release, get one email each.
Readers react right under the entry.
Who it's for
One entry links twelve shipped posts, and everyone who asked for any of them gets one email.
The feature 400 people voted for ships. Publishing tells every one of them, and they can react right under it.
However many of their posts a release answers, each person gets one email, and a retry never sends it twice. Listen for changelog.published to show it in your app.
The details
A title, the story in markdown, an author, and labels in your own words. Readers see it on your changelog page and in the widget.
Pick the posts this release delivers. The release links back to them, and everyone following those posts is told, once each, about the request they made.
The people who asked for something in it, and anyone who subscribed to every release, from the changelog page or their own settings. Readers without an account can subscribe too, by confirming their email.
Readers can answer each entry with one of four reactions: 🎉, ❤️, 🚀 and 🤔.
The API, the events, and what you can rely on when you build on it.
Two groups hear about a release: people following a post it answers, if they want release emails, and people subscribed to every release. The groups are combined, so nobody gets two emails, and a retry never sends the same email twice.
Entries are saved as written and displayed safely. Each email is written in the reader's language at the moment it's sent, and comes from "Your workspace via HeedPost" with your reply-to address.
You'll receive changelog.created, changelog.updated, changelog.published with the slug and title, changelog.deleted, changelog.restored and changelog_label.*. Entries brought in by an import are published without any email.
The changelog isn't in the public REST API yet. Its events reach your webhooks.
9 event types from this feature reach your webhooks. Each line shows what its data carries.
changelog.createdslug, titlechangelog.deletedslugchangelog.publishedslug, title, postschangelog.restoredslugchangelog.updatedslug, changedchangelog_label.createdname, colorchangelog_label.deletednamechangelog_label.restorednamechangelog_label.updatedname, was, changedPlans
Free is $0, Plus $29 and Pro $59 a month, per workspace. Never per seat. Every plan, line by line
| Feature | Free | Plus | Pro |
|---|---|---|---|
| Changelog and reactions | Included | Included | Included |
| Changelog labels | 5 | 15 | 50 |
| Email to people who asked | Included | Included | Included |
| Subscribe to every release | Included | Included | Included |
| Emails a month | 1,000 | 10,000 | 25,000 |
| Email packs and your own SMTP | Not included | Packs | Both |
Something else? Write to us, and a person answers.
No. They get one email that covers all three.
Yes. They confirm their address, and every release reaches them.
Then only the people subscribed to every release hear about it.
Yes. The widget can open your changelog as a tab.
Yes. It's saved as you wrote it and displayed safely.
No. Entries brought in by an import are published quietly.