One board, not forty threads
Requests from the board, chat and email land on one list per product, public or private.
a spreadsheet someone started and abandonedOne board per product where customers post and vote, duplicates merge and any support conversation becomes a request. When a request rises to the top, Tore builds it and preps the pull request for your approval.
Tore opens soon. Join the waitlist and we'll email you the day you can start.
Example: the Beacon Analytics feature request board. Votes tick up. In a support conversation, Priya asks for the weekly report in Google Sheets and Dan turns it into a vote on the existing request. A duplicate request, Sync reports to Google Sheets, is merged into Export to Google Sheets, which rises to the top with 51 votes. Tore reads the request and its conversations, plans and writes the change with 4 new tests, a second model reviews it, and pull request 512 waits for Alex's approval.
Every request lands in one place, counted fairly, with the conversations behind it. Then the winner gets built.
Requests from the board, chat and email land on one list per product, public or private.
a spreadsheet someone started and abandonedDuplicates merge into one request and each person's vote counts once, so the list shows real demand.
the loudest customer winning by defaultModeration and rate limits keep spam and pile-ons off the board your customers read.
deleting junk posts every morningTore turns the top request into a tested pull request, ready for your engineer to approve.
the top request waiting a quarter for a sprintBoards
Give each product its own board. Open it to everyone so customers can post and vote, or keep it private for your team and invited customers.
"Get 10k followers today, link in bio"
new account · 6 posts in 2 minutes · rate limit reachedVotes
When two requests ask for the same thing, merge them. The votes combine, people who voted on both count once, and everyone who asked stays attached to the request.
From the inbox
When a customer asks for something in chat or email, turn the conversation into a request in one action. Nothing gets retyped and nothing gets lost.
+1 from Priya · conversation linkedBuilt for you
Tore reads the request and every conversation behind it, writes the change with tests, has a second model review it, and preps the pull request. Your engineer can approve it, ask for changes in plain words, or take it over.

Put it in the Export menu next to CSV, not on the toolbar.
Close the loop
Anyone can follow a request. Everyone who voted, followed, or asked in a conversation that was merged into it hears when it's planned, when work starts and when it ships, by email and in the widget. Nobody has to chase you, and nobody has to remember to update them.
Example: a customer follows the Export to Google Sheets request, which has 58 followers. Its status moves from Under review to Planned, In progress and Shipped, and at each step followers get an email and a notice in the widget. The last one reads: Export to Google Sheets is live: here's how to use it. Each request has an Unfollow link.
Tune it
Open a board, let customers vote, and let Tore build the request that wins.