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

The internal note: where your team's context lives

The most useful thing on a feedback post is often the part customers never see.

Nº 22 · HeedPost team · Oct 3, 2026 · 2 min read

HEEDPOST NOTESNº 22

A customer posts a request. Over the following weeks your team learns things about it: sales hears the same ask from two prospects, support finds a workaround, an engineer thinks it's a day's work, a designer has concerns. Where does all that go?

Usually: Slack threads, meeting notes, someone's head. Then, three months later, the person who picks up the work starts from the post's title and nothing else.

Put the context on the post

An internal note is a comment only your team can see, on the same thread as the customer's conversation. It keeps everything about a request in one place: what customers said in public, and what your team knows in private.

What belongs in a note

  • What sales and support hear. "Two prospects asked about this on calls this week." This is demand that never shows up as a vote.
  • Workarounds. "You can do this today with the API. Here's the script we sent Acme." Now everyone can send it.
  • Sizing and risks. "Probably two days, but it touches billing." The first thing whoever plans the work will want to know.
  • Decisions and why. "Discussed in planning, parked until after the import work." So the next person doesn't re-open it from scratch.

Mention people instead of messaging them

The best part of notes is pulling a teammate into the thread rather than into a separate chat. "@Raj can we size this?" Raj gets one email, answers right there, and the answer stays with the request forever.

Keep notes and replies separate

The risk with internal notes is writing one when you meant to reply publicly, or the reverse. A few habits help: write public replies as if the customer is reading over your shoulder, because they are. Write notes as if a new colleague will read them in a year, because they will.

Notes make the board a memory

A board without notes is a list of requests. A board with notes is your team's memory of what customers want and what you've learned about it. When people leave, change roles or just forget, the context stays. That's worth a lot more than the minute it takes to write each one.

Start hearing everyone.

Free for your first two boards, with no card.