Revenue in the room
Filter a board to Enterprise, or to customers worth $10k or more, and sort by Most weight. Three quiet requests can turn out to carry most of the revenue.
Private previewWorkspaces are by invitation
Skip to content01Collect
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.Chapter 2 · Understand · User segments & revenue
Group customers into segments, like companies or plans, with what each pays. Every post then shows how many segments want it and the monthly revenue behind it, so a quiet request from your biggest accounts isn't buried under a loud one.
Try it
Switch between most votes and most weight, then narrow the board to one segment.
Step by step
User segments are part of Pro. Nothing changes for anyone until you add some.
Type them in, upload a CSV, point HeedPost at a feed, or send them in the sign-in token.
Nothing changes for your customers. They post and vote the way they always have.
Every post shows how many segments want it, what they pay, and how much comes from the biggest one.
Sort by Most weight or Most segments, and narrow the board by segment, label or minimum value.
Who it's for
Filter a board to Enterprise, or to customers worth $10k or more, and sort by Most weight. Three quiet requests can turn out to carry most of the revenue.
Filter the board to one customer and see everything they asked for, and what you already shipped.
Point each segment at an endpoint in your billing service and HeedPost reads it, or send the segment when a customer signs in. The values are only ever shown to your team.
The details
Usually a company, with one figure for what it pays. It can also be a group where each person pays their own amount, like a membership. Give it a label, like Enterprise or Growth, to filter by.
Type them in, upload a CSV, or point HeedPost at a feed from your own billing system. You can also send the segment in the token that signs customers in, which updates it every time they sign in.
Each post shows the segments behind it, the total they pay and how much of that comes from the largest one. Your team can sort by Most weight or Most segments, and filter by segment, by label, or by a minimum value.
Only your team. Not the public board, not the widget, not a member's API key from outside the team. If you move off Pro, segments are hidden and nothing is deleted.
The API, the events, and what you can rely on when you build on it.
Each post's demand comes as separate figures: how many segments asked, their total value, the largest single value and its share, and recent segments. HeedPost never blends votes and money into one priority number, so every decision can show its reasons.
The segment is read again at every sign-in. Its value is what the whole segment pays. For a segment where each member pays their own amount, set the value with a feed instead.
"user_segment": { "id": "acct_8812", // your own id: we key on it, never the name "name": "Larkspur", "label": "Enterprise", "value": 3100000 // minor units: $31,000.00 }
A segment can point at a URL with a key. HeedPost fetches it only from addresses it has checked, follows no redirects, and identifies itself as Heedpost-UserSegments/1. Yearly and other periods are turned into monthly amounts, and currencies are converted for sorting and totals.
Team keys can list segments, and filter posts by segment, by label or by a minimum value, given in minor units like cents. A key that belongs to someone outside the team gets a 403, not a narrower answer.
GET /v1/posts?value_min=1000000&sort=votes // backed by $10k or more
Each of these is a REST endpoint and, with the same name, an MCP tool.
GET/v1/user-segmentslist_user_segments Every user segment, largest first. Team keys only.GET/v1/postslist_posts Posts on this workspace's boards, newest first unless you choose another sort. Filter by board, status, kind or free text.GET/v1/posts/{post_id}get_post One post in full, with its board, status, author, tags and demand.Plans
Free is $0, Plus $29 and Pro $59 a month, per workspace. Never per seat. Every plan, line by line
| Feature | Free | Plus | Pro |
|---|---|---|---|
| User segments | Not included | Not included | Included |
| Most weight and Most segments sorts | Not included | Not included | Included |
| Filters by segment, label and value | Not included | Not included | Included |
| Companies from an import | Kept | Kept | Shown |
Something else? Write to us, and a person answers.
No. You see the segments, the revenue and the biggest share side by side, and you make the call.
Send figures on one basis. Feeds are turned into monthly amounts, but a token that mixes monthly and yearly figures makes totals nobody can explain.
Segments are hidden, not deleted. Move back to Pro and everything returns.
No. Values are shown only to your team.
Whether one big customer or many smaller ones are behind a request.
No. Use whichever matches where your customer data already lives.