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/Product practice

Keeping a board alive after launch week

Launch week brings a rush of posts. What happens in the following month decides whether customers keep coming back.

Nº 29 · HeedPost team · Oct 15, 2026 · 2 min read

HEEDPOST NOTESNº 29

Launching a feedback board is exciting. You announce it, customers arrive, the first fifty posts come in, the team is energised. Then launch week ends, everyone returns to their normal work, and the board slowly goes quiet. A month later, customers who posted in launch week notice nobody replied, and they don't post again.

Most boards don't fail at launch. They fail in weeks two to six.

Reply to everything from launch week

The people who posted first are your most engaged customers. Each of them should get some response within a week or two: a merge into an existing post, a question, a status, or an honest close. Not a promise, just evidence that a person read it.

Move a few things, visibly

Nothing builds trust in a new board like seeing a request move. Find three or four small things from launch week you can actually do soon, plan them, and ship them within the month. Then tell the people who asked.

Those first few shipped requests are worth more than their size. They prove the board works.

Set the rhythm before the rush fades

Decide in launch week who owns the board and when they'll look at it. An hour a week is enough for most teams, if it's the same hour every week. A board that's checked every Monday stays alive. One that's checked "when someone has time" doesn't.

Let the team see it without visiting it

People forget about tools they have to remember to open. A weekly summary in their inbox keeps the board in mind: what came in, what's rising, what shipped.

Keep inviting

Launch week is the only time most customers will hear about the board unprompted. After that, put the way in where they already are: a link in your product's menu, a line in your support replies, a mention in release notes.

Expect it to be quieter, and that's fine

A healthy board after launch has fewer, better posts, because it has settled into what it's for. Measure it by whether posts get answers and whether requests move, not by how many arrive.

Start hearing everyone.

Free for your first two boards, with no card.