How to collect customer feedback (the right way)

Most SaaS founders collect feedback the same way: badly. Slack threads scroll into oblivion, support tickets pile up in Intercom, the cofounder texts you "we should add dark mode" at 11pm and you forget by morning.

Here's how to actually collect customer feedback in a way that survives growth — and what each channel is good for.

The eight channels

1. In-app widget. Highest volume, lowest signal. Customers click it during a moment of frustration; you get raw, contextual feedback with the URL they were on. Use it for bug reports and friction points.

2. Public board. Lower volume, much higher signal. Customers see what others have asked for and pile on. Vote count tells you what's actually wanted. Use it for feature requests and roadmap prioritisation.

3. Email forwarding. Customer-success teams already have a ton of feedback in their email. A simple forwarding address (feedback@yourdomain) captures it without changing their workflow.

4. Sales call notes. Highest-value customers, often the highest-stake feedback. Founders should be on every call for the first year. Take notes, write them up, drop them in your tool.

5. Support tickets. The bulk of inbound. Most of it is "how do I do X" — ignore. The 10% that's product feedback is gold.

6. Slack / Discord. Power users live here. Great for early-stage; harder to scale. Worth scraping with a bot once you're past 100 customers.

7. Twitter / X mentions. Public, fast, low-volume for B2B. Set up alerts. The signal is small but the speed is unmatched — you can ship a fix in 24 hours and tweet about it.

8. Quarterly customer surveys. Lowest novelty, highest legibility. NPS or CES surveys give you a number you can graph. Don't trust them as the only signal.

The workflow

The mistake most teams make is treating each channel as a silo. The whole point of a feedback tool is to funnel everything into one place, group it, and prioritise by volume.

Here's the workflow we recommend:

collect → cluster → prioritise → build → close the loop

1. Collect from all eight channels. Forward emails, embed the widget, surface the public board.
2. Cluster with AI. Three customers asking for "dark mode," "night theme," and "make it less bright" are one request, not three.
3. Prioritise by vote count, customer tier, and strategic fit. Public votes ≠ revenue, but they're a damn good proxy.
4. Build. Move the cluster to your roadmap. Public roadmap shows customers it's coming.
5. Close the loop. When you ship, the changelog auto-pings everyone who voted on the cluster. They feel heard. They tell others.

What we got wrong

When we started Supoid, we collected feedback in a Notion DB. By month 4, it was 600 rows of half-categorised text and we couldn't find anything. The lesson: a tool that costs $29/mo will save you 5 hours a week from week one.

Don't be the founder who builds a feedback DB by hand. We've been there. It's a bad use of your time.