Product feedback · Feature requests

Customers ask once.Tore builds what wins.

One 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.

app.tore.ai/beacon-data/requests
Example data

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.

Stop guessing what to build.Build what they asked for.

Every request lands in one place, counted fairly, with the conversations behind it. Then the winner gets built.

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 abandoned

Counted fairly

Duplicates merge into one request and each person's vote counts once, so the list shows real demand.

the loudest customer winning by default

A public board that stays clean

Moderation and rate limits keep spam and pile-ons off the board your customers read.

deleting junk posts every morning

The winner arrives built

Tore turns the top request into a tested pull request, ready for your engineer to approve.

the top request waiting a quarter for a sprint

From a customer's askto a pull request.

Boards

A board for every product, public or private.

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.

  • Public or private boards, per product
  • Moderation holds anything that looks like spam for a person
  • Rate limits stop one account flooding the board
requests · boards
Example data
BoardsBeacon Data
Beacon Analytics24 open requests
public
Beacon Mobile11 open requests
public
Beacon Admin9 open requests · invited customers
private
Held for review

"Get 10k followers today, link in bio"

new account · 6 posts in 2 minutes · rate limit reached
RemoveApprove

Votes

Votes you can trust.

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.

  • Duplicate requests merge into one
  • Duplicate votes are prevented, one per person
  • Every voter stays linked, so they hear when it ships
requests · merge
Example data
34
Export to Google Sheetsposted by Maya · 5 conversations
20
Sync reports to Google Sheetsposted by Lena · 2 conversations
These look like the same requestMerge
51
Export to Google Sheetsmerged by Sarah · 7 conversations linked
Votes on both requests54
Same person on both, counted once−3
Counted votes51

From the inbox

A conversation becomes a request.

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.

  • One action from the shared inbox, no copy and paste
  • Matches an existing request, or starts a new one
  • The customer's vote and the conversation stay linked
inbox · Priya, Northwind
Example data
Priya · 9:14Any chance the weekly report could go straight into Google Sheets? We paste it in every Monday.
Dan · 9:16Good shout. I've added your vote to that request.
Turn into requestAssign
35
Export to Google Sheets+1 from Priya · conversation linked

Built for you

The top request, built and ready to approve.

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.

  • Built from what customers actually wrote, not a one-line summary
  • Tests written and run, and a second model reviews the change
  • Ask for changes in plain words and Tore revises it and re-runs the tests
  • By default it waits for your engineer's approval
beacon/web · PR #512
Example data
Export to Google Sheetsbuilt from request · 51 votes
112 passed
<Toolbar>
+ <SheetsButton report={report} />
</Toolbar>
Alex · request changes

Put it in the Export menu next to CSV, not on the toolbar.

Moved it to the Export menu. Tests re-run: 112 passed.
<ExportMenu>
+ <MenuItem>Google Sheets</MenuItem>
ApproveTake it over

Close the loop

Follow it. Hear at every step.

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.

  • Told at each step: planned, in progress, shipped
  • By email and in the widget, wherever they are
  • Voters and people from merged conversations follow automatically
  • One click to unfollow any request
requests.beacondata.com
Example data

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

Model for building features Codex · highAutonomy on beacon/web AssistApproval for UI changes approval required
All AI controls →
1board per product, public or private
1vote per person, duplicates merged
1 actionturns a conversation into a request
2models on every build: one writes, one reviews

Your next featureis already on the board.

Open a board, let customers vote, and let Tore build the request that wins.

You're on the list. We'll email you the day you can start.

Get early access when Tore opens. No spam.