Imagine you are an indie hacker. You build a tool you think people need, post it on X, Reddit, and Hacker News, and get the first sign-ups. You add features and ship them. A few days later those features are barely used. Meanwhile, people on social media have been asking for B and D. You never collected that, so you never ranked it.
Days spent building a feature well are fine. Building the right feature is worth more. That means involving users early: collect feedback, let demand sort it, and build from that queue instead of from a hunch. That is the gap Cawcus is built for.
What is Cawcus?
Cawcus closes the gap between what users ask for and what gets built. A widget on your site, or a hosted board, lets people drop a short idea or bug report. Votes rank the queue. Every item sits on a real board: Backlog, In Progress, Done. Priority comes from demand, not from whoever spoke last in standup.
What happens when that signal is ignored
Snapchat, 2018. A redesign mixed friends with brands and broke the muscle memory of Stories. About 1.2 million people signed a petition to undo it. CEO Evan Spiegel refused a rollback and said it would grow on users. Daily use fell for the first time since launch. Kylie Jenner’s “does anyone else not open Snapchat anymore?” post was followed by a stock drop of about 6 percent, roughly $1.3 billion in market value in a day.
Sonos, 2024. The company replaced its control app and shipped without sleep timers, alarms, and queue editing. Private beta testers and engineers had said it was not ready. Management launched anyway, tied to a hardware date. Customers flooded forums. The CEO later apologized, the chief product role was cut, and Patrick Spence eventually left. Reporting put the market-value hit near $500 million.
YouTube, 2021. In November 2021 YouTube hid the public dislike count. The button stayed, and creators could still see their own totals, but viewers lost the quality signal they used on tutorials and reviews. Co-founder Jawed Karim objected and edited the description of the first YouTube video to say so. The company did not reverse it. After the public API stopped returning dislike data that December, third-party tools could only show estimates.
These are not stories about users resisting change. They are stories about removing or replacing something people already relied on, then treating the objection as noise.
How Cawcus fits
Adapting a product has a cost either way. The expensive version is a backlash, a falling user base, or a rebuild of the feature you deleted. The cheaper version is hearing the request before you ship the wrong thing.
Cawcus puts that request on the board users already vote on, then exposes the ranked queue to coding agents over MCP. Tools such as Claude Code or Codex can fetch the top-voted backlog item, implement it, and write the status back. In Cawcus’s loop, the board updates when the work is done, so the next task is the next thing users actually asked for, not the next thing that was convenient to build.