Private previewWorkspaces are by invitation

HeedPost

01Collect

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.
AIDocsHelpPricingBlog

Collect

Understand

Ship and tell

Run it

Connect

Request an inviteSign in

Notes/Changelog

One email per person, per release

Why we send each person one email about a release, however many of their requests it answers.

Nº 38 · HeedPost team · Oct 19, 2026 · 2 min read

1HEEDPOST NOTESNº 38

A situation comes up more often than you'd think. You ship a release that answers twelve requests. One of your customers asked for three of them, voted on two more, and follows a sixth. How many emails should they get?

The naive answer is six, one per post. The right answer is one.

Six emails is spam, even when every one is relevant

Each message on its own is reasonable: "a request you follow has shipped". Six of them, arriving in the same minute, read as noise. The customer skims the first, ignores the rest, and learns that your emails come in bursts that can be skipped. The next time something they really care about ships, they skip that too.

One email that knows what they asked for

The better message is a single email about the release, written for that person: here's what shipped, and here are the requests of yours it answers. It's more useful than six separate notes, because they can see the whole picture at once.

It matters for your sending, too

Email has a cost, and not only money. Sending lots of messages that people don't open hurts how mailbox providers treat your mail. Over time, more of it lands in junk, including the sign-in links and invitations people actually need. Sending fewer, better emails protects every message you send.

And it has to be one, even on a retry

There's a technical half to this. Sending systems retry when something fails, and a careless retry sends the same email twice. The way to prevent it is to key each email on the person and the event, so a second attempt sees the first already went and stops.

That sounds like plumbing, and it is. But a customer who gets the same release email twice notices, and wonders what else is sloppy.

The principle

Write to people, not to posts. A person asked for things, follows things and cares about things, and every message should be built around that person rather than around your data model. One email per person per release is just that principle applied to a changelog.

Start hearing everyone.

Free for your first two boards, with no card.