RondiLoop: The Step Every Feedback Tool Skips
Factories hung up suggestion boxes more than a hundred years ago. Ideas went in. Word of what became of them rarely came back out. Software teams are not much better at this today. They collect feature requests in a board, maybe plan a few of them, ship some, and then nobody tells the person who asked.
RondiLoop is built around that missing step. It’s a feedback board, a roadmap and a changelog in one place, connected to GitHub, and when something ships, everyone who asked for it gets an email.
Why I built it
I run several products: mitKai, ShopSignal, Postmint, Brief-Generator and this site. Feedback for all of them came in through email, support messages and the occasional DM. Some of it was good. Very little of it turned into a plan, and I had no reliable way to remember who had asked for what by the time it was done.
I looked at the existing tools first. Most are priced for bigger teams with public boards. Some charge per tracked user, so the bill grows with your success. Others charge per board, or sell the roadmap, the changelog or a custom domain as an extra. And almost all of them stop at syncing a status with the issue tracker. None of the ones I found took a merged pull request, turned it into a changelog entry and then told the people who had asked.
That last part is the one I cared about. Telling users “you asked, we built it” is cheap, it builds trust, and it’s the step that gets skipped because it’s manual.
One request, start to finish
The idea is a single loop with four stages.
Collect. Users send ideas, bug reports and questions through a small widget in your app or a hosted page on your own feedback domain. No account, three fields, a few seconds.
Plan. Feedback from all your products lands in one inbox. Each item takes one decision: reject it, merge it into an existing request, or put it on the roadmap. Many requests can point at the same roadmap item, so you see at a glance how many people want something.
Build. One click turns a roadmap item into a GitHub issue, with a summary of the requests and no personal data. When a pull request for it opens, the card moves to In progress. When it’s merged, the card moves to Shipped. You don’t drag anything unless you want to.
Tell. You publish a GitHub release as you do today. RondiLoop drafts the changelog entry from the merged pull requests, written for users rather than developers and in their language. You read it, adjust it and publish. Publishing emails everyone who left their address with a request: here’s what shipped, and here’s what you had asked for.
Nothing goes out without your review. The AI writes drafts and makes suggestions. You make the calls.
Who it’s for
RondiLoop is for small software teams and solo makers whose code lives on GitHub. If you run one or more products, want your users to feel heard, and don’t want a second job writing release notes, it’s meant for you.
It’s not for everyone. The issue sync and the changelog drafts need GitHub. GitLab, Linear and Jira aren’t supported. The board, the roadmap and a hand-written changelog do work without it.
Pricing: one workspace, one price
I wanted the pricing to be the opposite of what annoyed me about the alternatives. There’s one flat price per workspace, monthly or annual. Unlimited end users and unlimited feedback. Every feature is included, custom domains, the GitHub loop and the AI drafts too. Nothing is billed per tracked user or per board.
The exact prices will be announced at launch. People on the early-access list hear them first.
Privacy as a feature
Feedback often contains things people wouldn’t post publicly. So RondiLoop runs on servers in Germany, with backups in the EU. The widget and the public pages set no cookies and load nothing from third parties. You can export or delete a person’s data straight from the admin, and closed feedback is anonymised automatically after 12 months.
The AI features use Claude by Anthropic. Before any text is sent, email addresses, phone numbers, payment details, IP addresses and the sender’s name are masked. If that’s still too much for a project, AI can be switched off for it.
For German teams this matters twice: the widget, the public roadmap, the changelog and the emails are available in German and English and follow each project’s language.
Where it stands
RondiLoop is running. mitKai is the first product on it, with its own feedback domain, and my other products follow. Using it on my own products first is the point. Every rough edge I hit there is one a customer won’t.
A few things aren’t there yet. Importers for Canny, Featurebase, Fider and CSV are planned but don’t exist today. There’s no launch date and no public sign-up. Early access is the way in.
If closing the loop with your users is something you keep meaning to do, put your email on the early-access list. The project page has the short version.