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/Building on it

Your roadmap, on your own website

Draw what's planned in your own style, from live data, with a read-only key and an afternoon of work.

Nº 26 · HeedPost team · Oct 10, 2026 · 2 min read

HEEDPOST NOTESNº 26

A public roadmap doesn't have to live on a separate site. Some teams want it on their own marketing site, in their own design, next to their pricing and docs. The data is the same, and only the drawing changes.

Doing it well takes a few decisions.

Use a key that can only read

The page that draws your roadmap needs to fetch data, so it needs a key. Make it a read-only key, and keep it on your server, never in the browser. If someone finds a read-only key, the worst they can do is read what's already public.

Fetch on the server, not in the browser

Have your server ask for the planned and in-progress posts, then render them into your page. Visitors never see the key, the page loads fast, and you can cache the result for a few minutes so you're not asking on every page view.

A request might look like:

GET /v1/posts?roadmap=true&kind=planned

Ask for each kind you want to show, in progress, planned and shipped recently, and draw them in your own columns.

Decide what to show

Your roadmap page is a chance to be clearer than a generic board. A few ideas:

  • Group by theme, not just status, if your customers think in areas of the product.
  • Show vote counts if they help people see what's popular, or leave them off if you'd rather the page feel calm.
  • Link each item back to the post, so people can follow it and get updates.

Keep it fresh

A roadmap page that's cached for a week is a stale roadmap. A few minutes of caching is enough to keep load light and the page current. If you want it instantly fresh, listen for status-change webhooks and clear your cache when one arrives.

Mind the limits

Every key has a request limit, so fetch on a schedule or with caching rather than on every visit. One request every few minutes is plenty for a roadmap.

Keep the board for conversation

Your site can be the nicest place to read the roadmap. The board is still where people vote and comment. Link to it from each item, so a reader who cares can add their voice in one click.

Start hearing everyone.

Free for your first two boards, with no card.