Customer feedback that goes somewhere

Let your customers vote your roadmap.

Collect every request in one place, let customers upvote what matters, turn the top of the list into a public roadmap, and close the loop with a changelog.

A public boardA roadmap that updatesA changelog that closes the loop
Sound familiar?

Every request, in a different graveyard.

The idea was good. It just never went anywhere anyone could see.

  • Buried in DMs and tickets

    Requests arrive in support threads and DMs no one revisits after the reply.

  • A spreadsheet only you read

    A feature backlog in a tab you open twice a month and no customer will ever see.

  • The same idea, five times

    Five people ask for the same thing five different ways — and you count it as one.

  • Customers who never hear back

    You ship the thing they asked for, and the person who asked never finds out.

The public roadmap

From voted-up to shipped, in the open.

The top of the board becomes a roadmap your customers can watch move.

  1. Planned

    Dark mode + SSO

    The two most-voted requests, queued for the Q3 mobile release.

  2. In progress

    Bulk CSV export

    141 votes — in beta with a handful of admin teams.

  3. In progress

    Zapier (beta)

    168 votes — connectors are being wired up now.

  4. Shipped

    Slack notifications

    Jun 2026 · everyone who voted got an email the day it landed.

  5. Shipped

    Mobile deep links

    May 2026 · shipped from the board, closed on the changelog.

How it works

Feedback in, roadmap out, loop closed.

One board collects it, votes rank it, and a click promotes it to the roadmap customers can see.

Public & private boards

Run one public board customers can vote on and private boards for the ideas you're still weighing.

Upvotes that dedupe

Similar requests get merged, so the vote count reflects real demand — not how many ways it was phrased.

One-click to roadmap

Promote a request from the board to a roadmap lane in a click, and everyone who voted gets notified.

Changelog

Announce what shipped and close the loop with the people who asked.

Segments

See which requests come from enterprise, mobile, or power users.

A quarter on the board

Modest numbers, one honest story.

1,240Votes castthis quarter
318Requests, deduped from 540auto-merged
1 boardInstead of five inboxes
9Shipped from the boardthis year
Pricing

Start free. Upgrade when the board earns it.

Run a public board on the free plan for as long as you like.

Free

$0/mo

One public board to get customers voting.

  • 1 public board
  • Unlimited requests
  • Upvotes & dedupe
  • Changelog
Popular

Growth

$39/mo

For teams running a real roadmap.

  • Everything in Free
  • Private boards
  • Public roadmap
  • Segments
  • Integrations

Scale

Custom

For multiple products and larger teams.

  • Everything in Growth
  • SSO / SAML
  • Multiple products
  • API access
Fair questions

The objections a skeptic would raise.

Won't a public board just fill up with noise and junk?

Two things keep it clean. Auto-merge folds near-duplicate requests into one so a single idea can't be asked ten ways, and nothing is public until you say so — you triage what appears on the board, and you decide what stays private.

Can we keep some boards private?

Yes. Run one public board customers vote on, and as many private boards as you want for ideas you're still weighing. A request only becomes visible when you move it onto the public board or promote it to the roadmap.

How is this different from a spreadsheet or a Trello board?

A spreadsheet lists what you think matters. Sounding ranks what customers think matters — with real upvotes — and gives them a public roadmap and changelog so they can watch a request move. It's the customer-facing loop, not just an internal list.

Do voters need to create an account?

No password required. A vote takes an email so we can dedupe it and email the voter when the request ships. Customers can vote and follow a request without ever making a full account.

Can we hide requests we know we'll never build?

Yes. Not every idea belongs on a public roadmap. You can archive or keep a request private, so the board reflects what you're actually considering — not a wishlist you'll never touch.

From product teams

When the board decides, the arguments stop.

We used to argue about what to build next in a meeting nobody remembered. Now the board settles it — the votes are right there, and I stopped guessing.
YBYara BeaumontFounder, Overbrook
The first time a customer got an email saying the thing they asked for had shipped, they replied just to say thanks. That loop is the whole reason we switched.
CVCallum VailHead of Product, Junco Labs

Stop guessing what to build next.

Put up a board, let customers vote, and let the top of the list become your roadmap.

Free public board · No card required