Find out what your users actually want built.
Feedback gives your product a public board. Requests arrive from inside your app, your users vote on them, and the roadmap and changelog come off the same board.
The public feedback board for climbday: tabs for the board, the roadmap, and the changelog; filters for the feature and bug boards; and the open requests in vote order, each with its vote count, comment count, and status.
- Any app
- One script tag, or POST from your backend. Pylon is not required.
- One board, three pages
- Requests, the roadmap, and the changelog stay in step because they share a source.
- Readable by agents
- The public board answers over HTTP with no key, and no private field in the payload.
- Included
- Covered by the Stack0 subscription. Runs at feedback.stack0.app.
From a request to a shipped change
Each step happens on the board, so nothing is copied between a tracker and a spreadsheet.
Collect from inside your app
A script tag puts a feedback button on your pages. Each report carries the page it came from and the app version.
Text me when a full class opens up
Any detail that helps
<script src="https://feedback.stack0.app/widget.js"
data-project="climbday" defer></script>Catch duplicates as they are typed
Matching requests appear while someone writes a title, so they vote on the one that exists instead of filing a sixth copy.
Notify me when a class has space
Similar suggestions
- 47Text me when a full class opens upIn progressVote
- 9Waitlist for full classesMerged into the aboveVote
A vote on the request that exists counts for more than a sixth copy of it.
Triage with your team
Set a status, tag it, and leave notes your team can read. Internal notes never reach the public board.
Internal note · your team only
Twilio is already wired for booking reminders. Reuse it.
Reply · posted to the board
Building this now. It will text you the moment a spot opens.
Share the roadmap
Planned, in progress, and completed, drawn from the statuses you already set. Untriaged requests stay off it.
Planned
Apple Wallet pass for my 10-pass
31 votes
Show which routes were reset this week
24 votes
In progress
Text me when a full class opens up
47 votes
Completed
Remember the waiver for returning members
12 votes
Open and closed requests stay off the roadmap. A backlog read as a promise is the thing to avoid.
Publish the changelog
Draft release notes against the requests they close. Publishing notifies everyone who voted.
Class waitlist texts
DraftCloses 1 request · 47 people get notified when it publishes.
Waivers remember you
PublishedReturning members skip the waiver. Signing once is enough.
- Remember the waiver for returning members12 votes
Let agents read it
The board publishes a guide at /llms.txt and answers over HTTP. An agent can read what users asked for and file a request for one.
$ curl feedback.stack0.app/llms.txt
# Stack0 Feedback
Board: /p/<slug> · Roadmap, Changelog
Read: POST /api/fn/portalView { slug }
Submit: POST /api/fn/submitPost
$ curl -X POST .../api/fn/portalView -d '{"slug":"climbday"}'
✓ 38 open requests, top: 47 votes, in_progress
Public reads need no credential. Internal notes and unpublished entries are not in the payload.
What the board holds
One board per product, with the surfaces the screenshots above come from.
Requests and boards
Separate boards for features and bugs, each with its own posting rules.
Votes
One vote per person, from an account or a guest session. No sign-up wall to read.
Merge duplicates
Fold a copy into the real request. Votes combine, and the old link still resolves.
Roadmap
Planned, in progress, and completed, in vote order, on a public page.
Changelog
Drafts your team can see, published entries linked to the requests they close.
Internal notes
Comments marked internal stay with your team and never enter a public payload.
Notifications
Voters follow a request and hear when its status changes or it ships.
Agent access
A guide at /llms.txt, public reads over HTTP, and submissions on a user's behalf.
Part of the suite
Feedback holds what users asked for; the rest of Stack0 acts on it.
- 01
Add the script tag to an app from Build, a Pylon project on Cloud, or any site you already run.
- 02
Ask an Agent what the top requests are. It reads the same board your users do.
- 03
One subscription covers it, alongside Build, Cloud, Agents, Analytics, and the APIs.
Put your roadmap where your users can vote on it
Create a board, add one script tag, and the first requests arrive the same day.