Always-on internal customer-feedback intelligence — without a paid VoC tool
Customer-feedback intelligence, without the SaaS bill
It reads what the company's own customers are saying — across support tickets, in-product surveys, and public review sites — and turns it into a dashboard, a Monday-morning digest, and plain-English answers on demand. Built inside the warehouse the company already ran, instead of on a ~$10K/year off-the-shelf tool.
A five-figure annual SaaS replaced by infrastructure already paid for — shipped in about four weeks, running for well under a fifth of the price.
| Before | After | |
|---|---|---|
| Where feedback lives | scattered across tickets, surveys, reviews, sales calls | one place, inside the warehouse already running |
| Effort per question | hours of copy-paste and hand-synthesis into a doc | a one-line question, answered with source-linked quotes |
| Cadence | a manual reading sprint once a quarter, if at all | a live dashboard, a Monday digest, and answers on demand |
| Annual cost | ~$10K/yr for the off-the-shelf SaaS | well under $2K/yr, on infrastructure already paid for |
| Where customer data ends up | another vendor's database, behind another login | never leaves the company's own warehouse |
| Time to set up | a months-long vendor rollout | about four weeks to ship v1 |
A paid SaaS line item with the data leaving the building became a quiet always-on capability inside the warehouse the company already ran — for under a fifth of the price, shipped in weeks, with the security review reduced to 'where does the data go?' / 'it doesn't.' The researcher's hand-coded month a year goes back into the work that actually needed a human; everything that was just listening becomes the system's job.
What I built
A customer-feedback intelligence system, built end-to-end inside the company's existing data warehouse instead of on a paid SaaS. It pulls quotes from every channel where customers leave words, runs the AI on them inside the warehouse so the data never leaves the company's tenant, and serves the results three ways the team can actually use.
- A dashboard. Filter by segment, channel, date range, or theme — built on the BI tool the team was already using, sitting on the same auto-tagged quotes the digest and the
/voc-askcommand use. One source of truth, three lenses on it. - A weekly Slack digest. Every Monday morning, an auto-post: the top themes of the week, the biggest movers, the verbatims worth reading. The thing leaders read with their coffee instead of a stale report.
- A
/voc-askcommand. Plain-English questions answered in plain English: "what's driving churn?", "what do users in this region need?", "have we already heard this complaint?" Every answer comes with real customer quotes attached, each linked back to its source ticket, survey response, or review — so the team can verify any claim in one click.
The proof-of-concept ingested thousands of customer quotes across four channels (support tickets, in-product surveys, and two public review sites), auto-tagged each with theme and sentiment, and shipped the dashboard, the digest, and the /voc-ask script in about four weeks.
Why it matters
The team kept asking "have we already heard this complaint?" and the honest answer was "probably, but I don't know where." That isn't a tool problem — it's a "the words are everywhere and listening to all of them is a full-time job nobody has" problem. The off-the-shelf fix solved it with a five-figure annual subscription and another vendor holding copies of every customer quote. The replacement is the same outcomes — dashboard, weekly digest, ad-hoc queries with sourced quotes — built on infrastructure already paid for, with the AI running inside the warehouse so the data never moves. Under a fifth of the cost, weeks to ship instead of months, and a security conversation that gets short.
Normally "always-on customer-feedback intelligence" describes a category of SaaS with a sticker price to match. Here it's a Monday-morning Slack post, a dashboard a designer can filter mid-meeting, and a one-line question that returns the customer's own words — built in-house, on the stack the company was already paying for.
- 01Pull
Customer quotes from every channel — support tickets, in-product surveys, public review sites, and the team's call transcripts — land in the warehouse the company already runs.
- 02Tag
Each quote is auto-tagged with theme (pricing, onboarding, integrations, regional needs…) and sentiment, by the AI layer that lives inside the warehouse — so customer data never moves out of the company's tenant.
- 03Show
Two self-contained outputs ship from the same data: a dashboard you can slice by segment, channel, date, or theme — built on the BI tool the team was already using — and a trend report that highlights what's moved week over week.
- 04Digest
Every Monday morning, a Slack post lands automatically: the top themes of the week, the biggest movers, the verbatims worth reading.
- 05Ask
A `/voc-ask` command takes plain-English questions — 'what's driving churn?', 'what do users in this region need?' — and answers with real customer quotes, every one linked back to its source ticket, survey response, or review.
The shift is from buying a layer to using the one you already own: the warehouse, the AI inside it, the customer-IDs that tie feedback back to accounts. The same answers — what customers are saying, what's driving churn, what users in a region need — arrive on a dashboard, in a Monday digest, and on demand through a one-line question, for under a fifth of the SaaS the company nearly bought.