Join the waitlist
Solutions · Product feedback

Build what they asked for.Then tell them you did.

A board your customers post to, votes that mean something, a roadmap fed by the same items, the top request built for your approval, and a changelog that tells everyone who asked.

Join the waitlistFollow one request

Tore opens soon. Join the waitlist and we'll email you the day you can start.

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

Example: one request travels the whole loop. Priya asks for Google Sheets export in chat. Dan turns the conversation into a request. Votes grow to 51 as a duplicate is merged. The item moves to In progress on the public roadmap. Tore builds it and pull request 512 waits for Alex's approval. Tore drafts the changelog entry and Sarah approves the wording. All 51 people who asked are told, and the next request starts the loop again.

Stop deciding from memoryand a spreadsheet.

The requests, the plan, the build and the announcement all run on the same items, so nothing falls between them.

Requests in one place

Asks from chat, email and the board land on one board per product, with the conversations attached.

some in email, some in chat, some in a spreadsheet

Demand you can trust

Duplicates merge and each person's vote counts once, so the loudest customer doesn't win by default.

building for whoever shouted last

Everyone can see the plan

A public roadmap fed by the same votes answers "is it planned?" before anyone asks.

the same question in every renewal call

Shipping gets noticed

When it ships, everyone who asked is told, so they see that you listened.

building what they asked for and never saying so

Collect, plan, build, tell.One loop, one set of votes.

It's the same loop Tore runs for bugs, pointed at features instead.

Collect

Every ask lands on one board.

Customers post and vote on a board for each product, public or private. When someone asks in chat or email, your team turns the conversation into a request in one action, and the vote counts.

  • Boards per product, public or private, with moderation
  • Conversations become requests without retyping
  • Duplicates merge, one vote per person
Feature requests →
requests · Beacon Analytics
Example data
ChatPriya asked
EmailTom asked
BoardMaya posted
51
Export to Google Sheets6 conversations · 1 duplicate merged

Plan

The roadmap runs on the same votes.

Move a request onto your public roadmap and it brings its votes and its conversations with it. The board and the plan can never disagree, and customers check progress themselves.

  • Public roadmap on your own domain, no login to read
  • Items carry their votes and original request
  • Columns you name and order
Product roadmap →
roadmap.beacondata.com
Example data
Board
Google Sheets51
Dark mode37
Slack alert24
Roadmap
Google Sheetsin progress · 51
Slack alertplanned · 24
CSV header rowshipped

Build

Tore builds the top request.

When a request wins, Tore reads it and every conversation behind it, writes the change with tests, has a second model review it, and preps the pull request. Your engineer approves it, asks for changes in plain words, or takes it over.

  • Built from what customers actually wrote
  • Ask for changes and Tore revises and re-runs the tests
  • By default it waits for your engineer's approval
How Tore builds it →
beacon/web · PR #512
Example data
Built from request · 51 votes
112 tests passed · 4 new
Alex · request changes

Put it in the Export menu next to CSV.

Moved it. Tests re-run: 112 passed.
ApproveTake it over

Tell

Everyone who asked hears it's live.

Tore drafts the changelog entry from the change that shipped. A person approves the wording, then it goes to the public changelog, the in-app feed and every customer who asked. Customers can follow any request, and followers hear at every step, planned, in progress and shipped, by email and in the widget.

  • Drafted from the change that shipped
  • A person approves the wording before it sends
  • The people who asked are told in their conversation or by email
  • Followers hear at each step, with one click to unfollow
Changelog →
changelog · v2.5
Example data
Drafted from PR #512 · approved by SarahExport any report to Google Sheets

Pick Google Sheets in the Export menu and your report lands in a sheet in one click.

58 followingPlannedIn progressShipped
Priya, Northwindtold in chat
Maya, Acme Corptold by email
Tom, Acme Corptold by email
and 48 more who askedtold

Tune it

Model for building features Codex · highAutonomy on beacon/web AssistWho is told when it ships everyone who asked
All AI controls →
1set of votes from the first ask to the changelog
1 actionturns a conversation into a request
2human checks by default: the pull request and the release wording
3ways customers hear: changelog, in-app feed and their own conversation

Each part of the loop.

Product feedbackFeature requestsBoards, fair voting, and the top request built for you.See how → Product feedbackProduct roadmapA public plan fed by the same votes.See how → Product feedbackChangelogRelease notes drafted from what shipped, sent to who asked.See how →

Close the loopon every request.

Open a board, let the votes decide, and let Tore build it and tell everyone who asked.

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

Get early access when Tore opens. No spam.