How Zyloo works.
A public feature board in one loop: users post and vote, you decide and ship, and everyone sees the progress. No account for voters, no sales call for you.
One board. Three moves.
Not a support inbox, not a spreadsheet, not a private roadmap. A public board where the order is set by the people who use the product.
- Post
A user adds a request.
One title and an optional description. No account, no email wall, no moderator queue. The request lands on the public board immediately.
- Vote
Everyone ranks what matters.
Visitors upvote the requests they care about. One vote per browser, and voters are never capped. The board sorts by votes, so the top of the list is the real priority.
- Ship
You close the loop in public.
Move the request through Under review, Planned, In progress and Shipped from your dashboard. The public board updates in the same second.
What your users see.
The public board is the product. No login, no app, no roadmap PDF. Requests are ranked by votes and tagged with the current status.
- Vote without an account.
- Submit an idea in one field.
- See when something moves to Shipped.
What you see.
A short dashboard, not a second product. Change a status, delete a request, export the list. That is the core admin surface.
- URUnder review
New feedback. You have seen it and are deciding what to do.
- PLNPlanned
It is on the roadmap. Voters know it is coming.
- PRGIn progress
You are building it. The board shows the work is moving.
- SHPShipped
It is live. The people who asked can see the result.
Declined requests stay on the board so voters can see the decision instead of wondering what happened.
Who it helps.
For indie founders and tiny teams.
You are the product team. You do not need a sales call, a seat count, or an enterprise feedback suite. You need one public place to collect what users want and show what you did about it.
For the people who use your product.
They do not want another account. They want to say “this is the thing that would make me use this more” and see whether it is being worked on.
Why a public board.
Feature requests already exist. They are in DMs, a Discord thread, a support inbox, and a Notion page nobody updates. A public board gives them one address.
Votes turn a pile of opinions into an order. Status turns “we should build that” into “we are building that” and then “it shipped”. That loop is the difference between a complaint inbox and a roadmap people trust.
Live in about 90 seconds.
No onboarding wizard. Name the board, share the link, take the first vote.
- Name it. One field for the product, one for the board. We generate the public slug.
- Share it. Put the link where your users already are: your app, your docs, a launch post.
- Close the loop. Move the first request to Shipped when it ships. That is the whole habit.
Questions.
Short answers before you start.
Do users need an account?
Can people comment on a request?
How is the order decided?
Can I see who voted?
How do status changes work?
Can I delete a request?
Can I export the board?
Does it work on phones?
Can I email voters when something ships?
Can I use my own domain?
Start with a free board.
Free for 1 board and unlimited posts. No card. Share the link and take the first vote today.