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

A public roadmap is a conversation, not a contract.

Use visible states to show direction without turning every request into a deadline.

Nº 08 · HeedPost team · Sep 8, 2026 · 2 min read

WENS HEEDPOST NOTESNº 08

Teams hesitate to publish a roadmap for one reason more than any other: they're afraid it becomes a list of promises they'll be held to. Then plans change, which they always do, and every change looks like a broken promise.

That fear is real, but it comes from treating the roadmap as a contract. Treat it as a conversation instead and most of the risk goes away.

Show direction, not dates

A roadmap that says "CSV export, March 14" is a contract. A roadmap that says "Planned: CSV export" with a short note on why is a direction. Customers mostly want to know whether you heard them and whether their thing is coming at all. A date adds pressure and very little reassurance.

If you do share timing, keep it coarse. "This quarter" survives a slipped week. "March 14" doesn't.

Fewer items, honestly labelled

A roadmap with sixty planned items isn't a plan. It's a wish list, and customers can tell. Keep "Planned" for things you genuinely intend to do, and keep "In progress" short. A small, true roadmap earns more trust than a big, hopeful one.

Let people talk back

The point of making it public is that customers can react. They vote, they comment, they tell you a planned item doesn't quite solve their problem. Those reactions are the cheapest product research you'll ever get, and they arrive before you've written any code.

So read the comments on planned items closely. A comment like "this would help, but what we really need is..." on something you're about to build is worth a meeting.

Changing your mind is allowed

Plans change for good reasons: you learned something, the market moved, a smaller fix turned out to solve the real problem. Customers accept that, as long as you tell them. What they don't accept is a planned item quietly disappearing.

When something comes off the roadmap, move it back with a sentence. "We've moved this back to review. The new import covers most of what people asked for here, and we want to see what's left." Honest and short.

One source of truth

The quickest way to a stale roadmap is keeping it separately from the work. If your public roadmap is a slide someone updates once a quarter, it'll be wrong most of the time. If it's the same data your team moves every day, it stays current without anyone remembering to update it.

A roadmap that's always roughly right beats one that's perfectly right once a quarter.

Start hearing everyone.

Free for your first two boards, with no card.