How We Run sarvaFeed on sarvaFeed
We build a feedback tool, so we run our roadmap on our own public board. Here is what that dogfooding loop actually looks like, and what it shipped.
The fastest way to find the rough edges in a product is to depend on it. So our roadmap does not live in a private tracker. It lives on a public sarvaFeed board that anyone can read, vote on, and comment in. We read it every morning, and most of what we ship starts as a post there.
The board is the backlog
We do not keep a separate internal wishlist that we occasionally sync. The board is the backlog. Customer requests, our own ideas, and bugs all land in the same place, get the same statuses, and compete for the same attention. When something moves to In Progress, everyone watching sees it, including the person who asked for it.
What the loop shipped
Running on our own board is not a vanity exercise. It changes what we build. A few concrete examples from the last two quarters:
- Revenue-weighted voting came directly from watching our own board fill with popular but low-value requests. We felt the problem before we built the fix.
- Duplicate detection was a bug report against ourselves: our board had three versions of the same request and merging them by hand was tedious.
- The weekly changelog digest exists because voters told us in comments that they missed updates buried in the feed.
The numbers
Since moving our roadmap fully public, roughly 40 percent of what we shipped originated as a customer post rather than an internal idea. Repeat questions to our support inbox about what is coming dropped noticeably, because the answer is a link. And the median time from a request reaching Planned to shipping the notification back to voters is now measured in weeks, not quarters.
Why it works
Dogfooding keeps us honest. Every awkward workflow we hit is one a customer would hit too, so it gets fixed with real urgency. And closing the loop in public, telling the voter their request shipped, is the single action that keeps people contributing. We know because it keeps us contributing.
If a feature annoys us on our own board, it gets fixed before it ever annoys a customer. That is the whole point of running the loop on ourselves.
You can watch the same loop on our public roadmap. Most of what shows up in the changelog started as a post someone else made, and that is exactly how we want it.