A founder we advised spent fourteen months building a B2B analytics tool nobody quite wanted, and three weeks realizing the support tickets were the actual product. This is the story of the pivot nobody in the room wanted to make — including us.
The signal was in the complaints, not the metrics
The dashboard looked healthy: steady signups, reasonable activation. But every support ticket followed the same shape — customers weren’t asking how to read the analytics, they were asking someone to just tell them what to do about what the analytics showed. The product was answering a question users weren’t asking, and quietly doing the job of a different product for free, one ticket at a time.
Why nobody wanted to see it
Fourteen months of engineering had gone into the dashboard. The team’s identity was “we build analytics tools,” and support tickets are, structurally, the least prestigious data in any company — nobody builds a roadmap review around the complaints inbox. Recognizing the pivot meant admitting the actual expertise the team had built was advisory, not software, and that’s a harder pitch to your own ego than to investors.
What changed after the pivot
They rebuilt the product around the “what do I do about this” question directly — turning the support workflow into the core feature, with the dashboard as a supporting view instead of the main event. Retention roughly doubled within two quarters, not because the new product was smarter, but because it stopped making users do the last, hardest step alone.
The lesson generalizes: your product roadmap is in your support inbox more often than in your competitor’s changelog. Worth an outside read? Let’s look at yours.
