We Believe Feedback
Should Not Require
a Meeting.
This is why we built FeedbackFlow. Not because the world needed another tool. But because the tools we had were making us worse at understanding what we built.
Chapter 01
The Feedback Gap
Something broke in the last few years. We got faster at building. Dramatically faster. AI writes code. Frameworks handle the boring stuff. You can ship a feature before lunch.
But understanding what you shipped? That got slower.
Feedback still arrives the same way it did in 2015. Screenshots in Slack. Vague emails. “It's broken” with no context. You spend more time decoding what users meant than fixing what they found.
“Can you show me what you mean?”
— Every developer, every day, losing 20 minutes
“What browser were you using?”
— The question that should never need to be asked
“I can't reproduce this.”
— The graveyard of valid bug reports
The gap isn't between you and your users.
It's between what they saw and what you see.
Chapter 02
What We Believe
Capture at the Source
The moment a user sees a problem is the moment with the most context. Every second after that, details fade. We believe feedback tools should live where the problem happens—not in a separate app, not in email, not in a meeting scheduled for next week.
AI Should Translate
Users shouldn't need to write perfect bug reports. That's not their job. AI is finally good enough to look at a screenshot, understand the context, and ask the right follow-up questions. Let the machines do the translation work.
Open by Default
We don't believe in trapping your data. FeedbackFlow is open source because feedback belongs to you. Self-host it. Fork it. Read every line of code. Export everything. Walk away anytime. That's not a feature—it's a principle.
Tickets, Not Conversations
The goal of feedback isn't to create another thread to manage. It's to create a ticket you can act on. We believe in structured output: Linear issues, Notion pages, JSON for your AI workflows. Feedback should end up where work happens.
Chapter 03
Who This Is For
We didn't build this for enterprises with dedicated QA teams and 47-step bug reporting workflows. We built it for people like us.
Solo Founders
Who are customer support, product manager, and engineering lead—all before 9am.
Small Teams
Where everyone wears multiple hats and nobody has time for “can you clarify what you meant?”
Indie Hackers
Building multiple projects, shipping constantly, and needing feedback that doesn't require a Jira license.
AI-First Builders
Who want feedback in JSON format so it can flow directly into their AI development workflows.
Chapter 04
The Uncomfortable Truth
Most feedback never gets acted on. Not because teams don't care. Because by the time feedback reaches someone who can fix it, it's been through so many translations that the original signal is gone.
User tells support. Support writes a ticket. Ticket gets triaged. Developer reads it a week later. Developer asks for clarification. User has moved on.
We built FeedbackFlow to kill that chain. Screenshot to ticket. One step. Full context. No translations.
Chapter 05
Why We Built This
InfiniteMoney ships a lot of projects. AI tools, internal apps, client work—things move fast. And we kept running into the same wall: we'd build something that technically worked but emotionally didn't.
Users would tell us something was wrong, but we couldn't see what they saw. We'd ask for screenshots. They'd send blurry photos. We'd ask for steps to reproduce. They'd say “I just clicked the button.”
So we built a widget. Then we added AI to ask follow-up questions. Then we made it generate tickets automatically.
Then we realized everyone else has this problem too.
Why I built FeedbackFlow
and what InfiniteMoney is
I build fast, ship often, and I hate losing context. FeedbackFlow started as a selfish tool: something I wanted for every product I touch—capture what the user saw, preserve the details, and turn it into work you can actually do.
When feedback shows up as a screenshot in a random thread, the useful parts disappear: what page they were on, what they clicked, what broke, what they expected. This project is my answer to that: screenshot to ticket, with context attached by default.
InfiniteMoney is a research company exploring what happens when you give agency to AI and let it lead. Humans stay in the loop to lend a hand—direction, taste, constraints—but the AI drives. If you're curious what that looks like in practice, follow along at infinitemoney.ai.
Our Promise
FeedbackFlow Will Stay:
Open Source
Forever. No bait-and-switch. The code is yours to read, run, and modify.
Privacy-First
No tracking. No selling data. No “anonymized analytics” that aren't anonymous.
Fair Pricing
Pay for seats, not for feedback volume. And self-hosting is always free.
No Lock-In
Export everything. Switch anytime. We'll even help you migrate away if you want.
Join the Movement
Stop losing context. Start capturing feedback that actually helps you build better.