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

Five questions before you build the most-voted request

A short conversation with a few voters can save a quarter of building the wrong version.

Nº 18 · HeedPost team · Sep 26, 2026 · 2 min read

HEEDPOST NOTESNº 18

The most-voted request on your board has a strange property: everyone thinks they know what it means, and they don't all mean the same thing. Two hundred people voted for "Excel export". Ask five of them what they'd do with it and you'll get four answers.

Before committing a quarter to the top request, talk to a handful of the people who voted. Twenty minutes each. Here are the five questions we'd ask.

1. When did you last need this?

Ask for the last real time, not in general. "Last Thursday, when finance asked for the roadmap" is a story. "We'd use it all the time" is a wish. Stories tell you frequency and context. Wishes tell you very little.

2. What did you do instead?

The workaround is the most valuable answer you'll get. It tells you how painful the problem really is, and what the bar is for your solution. If they currently copy forty rows into a spreadsheet, a spreadsheet is the bar. If they currently take a screenshot, maybe a share link beats an export.

3. What would you do with it right after?

This uncovers the job behind the request. "I'd paste it into our finance deck" suggests something different from "I'd load it into our warehouse". Same request, different solutions.

4. What would make it useless to you?

People are better at spotting what's wrong than describing what's right. "If it doesn't include the vote counts, I can't use it." That's a requirement you'd have missed.

5. Who else needs to see it?

Requests often exist because of someone who never visits your board: a manager, a finance team, a client. Knowing who the real audience is can change the whole design.

Who to ask

Pick five or six voters who differ: big and small customers, recent and long-standing, people who commented and people who only voted. You're looking for the range of what the request means, not a vote.

Then write what you heard on the post as an internal note. When the work starts, whoever picks it up reads five real stories instead of a title and a number. That's often the difference between building the request and building what people meant by it.

Start hearing everyone.

Free for your first two boards, with no card.