I built an NPS tool and discovered the metric founders obsess over isn't the one that matters

Two years ago I was helping a small restaurant group figure out why one of their three locations kept underperforming at lunch. Same menu. Same prices. Same training. They'd tried surveys before, a generic SurveyMonkey link on a table tent pulling a 3% response rate, mostly complaints from people already annoyed enough to scan a QR on their way out.

We swapped in a branded NPS survey sent via SMS and email. Three weeks later they had 200+ responses and a score of +18. Not great. But the score wasn't the finding. Forty-seven comments mentioned the Tuesday lunch wait time. Not the wait itself. The gap between the quoted wait (12 minutes) and the actual one (often 30+).

They fixed one thing. The host stopped guessing and started quoting the real kitchen queue. Three months later NPS was +51 and lunch revenue at that location was up 22%.

That whole sequence eventually turned into NPSKit (npskit.com). But the more interesting thing for this audience isn't the product. It's what I learned about response rates while building it, because I think it applies to almost every founder running surveys, asking for feedback, or trying to listen to users.

The thing nobody warned me about: the tool barely matters. The branding does.

When a customer gets a survey link from a SaaS company they've never heard of, their brain categorizes it in roughly 400 milliseconds. Spam-folder behavior. Not because they're unfriendly. They'd probably give feedback happily if asked in a way that felt real. It's that nothing about the experience signals "this came from the place I just visited."

Across the businesses I ran this on, branded surveys pulled 3 to 4x higher response rates than generic third-party links. That's the difference between a dataset you c