Why I Built Feedback Pulse (and Why You Might Actually Need It)
I kept running into the same problem. I'd ship something, wait for feedback, and hear nothing. Or worse — I'd get feedback scattered across emails, Slack messages, support tickets, and random DMs. No structure, no context, no way to see the big picture.
So I built Feedback Pulse.
What it actually does
It's a feedback collection tool. Simple as that. But the way it works is what makes it different.
You've got three ways to collect feedback:
- The widget. You drop a single script tag on your site and you get a clean feedback button. Users click it, leave their thoughts, done. Takes about 30 seconds to set up. You can customize the colors, position, text — make it look like it belongs on your site.
- REST API. If you're building a mobile app, a desktop app, a CLI tool, whatever — you can send feedback through the API. It doesn't care where it comes from. A few lines of code and you're connected.
- Webhooks. Want feedback to flow into your own systems? Set up a webhook and we'll push every new piece of feedback wherever you want it. Slack, Discord, your own backend, a spreadsheet — doesn't matter.
So what happens after you collect feedback?
This is the part I actually care about. Collecting feedback is easy. Making sense of it is hard.
Feedback Pulse gives you a dashboard where everything lives in one place. You can see trends, filter by sentiment, check satisfaction rates over time. The AI suggestions feature looks at your feedback and tells you what people are actually asking for. Not in some vague corporate way — it gives you concrete, actionable stuff.
You can separate development and production environments too. So your test data doesn't pollute your real feedback.
Team stuff
If you're not a solo dev, you can invite your team. Everyone sees the same feedback, same analytics. No more "did you see that email from the user who said..."
What it costs
There's a free tier. One project, 1,000 feedback entries per month. Enough to get started and see if it's useful for you.
Pro gets you more projects, more feedback, longer data retention. Enterprise is for bigger teams who need the extra capacity.
Why not just use Google Forms?
You could. I did, for a while. But forms are disconnected from your product. Users have to leave what they're doing, open a form, fill it out. Most won't bother.
A widget that lives right inside your app removes that friction. And an API means you can collect feedback from places where a form doesn't even make sense.
The honest pitch
Feedback Pulse won't change your life. It's a tool. But if you're building something and you want to know what your users think — without duct-taping together five different services — it might save you some time.
Give it a shot. It's free to start.