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/Feedback

The worst field on your feedback form

"How important is this to you?" feels useful and tells you almost nothing. There are better questions to ask.

Nº 07 · HeedPost team · Sep 6, 2026 · 2 min read

?HEEDPOST NOTESNº 07

Almost every feedback form we've looked at has some version of it. A row of stars. A dropdown from "nice to have" to "critical". A slider from one to ten. It feels like good practice. You're measuring priority at the source.

In practice it's the least informative field on the form.

Everyone picks the top

People write feature requests when something gets in their way. In that moment, it matters. So they pick "critical", or five stars, or ten. Look at the answers across a few hundred posts and you'll usually find a pile at the top of the scale and a scattering below it. A field where nearly everyone gives the same answer can't help you choose between posts.

It measures a mood, not a cost

Even when people answer carefully, the scale doesn't ask about anything you can compare. "Critical" from someone who copies data by hand once a quarter and "critical" from someone who can't close their books without it are the same click. The word carries no information about frequency, workaround, money or who else is affected.

It makes people defend themselves

There's a quieter problem too. When you ask someone to rate their own request, you're asking them to argue for it. Some will overstate, because they've learned that's how you get heard. Others understate, because they're polite. Neither tells you the truth.

What tells you about importance instead

Importance leaves traces you don't have to ask for:

  • Other people's votes. One person rating their own post "critical" is a mood. Fifty people pressing vote is a signal.
  • The workaround. Ask what they do today. "We copy forty rows by hand every Friday" tells you the cost directly.
  • How often it comes up. A problem people hit daily outranks one they hit once a year, whatever the stars say.
  • Who's asking. The plan and size of the company behind a post is often the most useful weight you have.

If you must keep a scale

Some teams like having one. If you keep it, anchor every option to something concrete. Instead of "low" to "critical", try:

  • I'd use this occasionally.
  • I'd use this every week.
  • I can't do part of my job without it.
  • We might switch tools over this.

Concrete options spread the answers out and mean the same thing to everyone. But try a month without the field first. You may find you don't miss it.

Start hearing everyone.

Free for your first two boards, with no card.