Customer signal

A single piece of feedback — a quote, complaint, request, or behavior — that reveals what a customer wants, struggles with, or values.

A customer signal is the atomic unit of product feedback. Anything a customer says or does that reveals intent, frustration, or unmet need counts: a sales call objection, a support ticket, an NPS verbatim, a Slack message, a churn-survey response, a feature request in a roadmap tool, a pause during a demo when the prospect can't find a button.

On their own, signals are anecdote. A single user asking for an export button could be a power user, an outlier, or the tip of an iceberg — you can't tell. The job of a product team is to aggregate signals across many customers and across many sources, so that patterns emerge. Ten signals from ten different accounts pointing to the same underlying problem is data; one signal repeated by the loudest customer is noise dressed up as data.

The hard part isn't collecting signals — most B2B companies have hundreds per week scattered across Intercom, Zendesk, Gong, sales notes, and CSM trackers. The hard part is synthesizing them into themes a team can act on. That's the entire reason a category called product intelligence exists, and it's what Kiln is built for.