The context
An enterprise cybersecurity vendor with a broad portfolio. One of its products — a platform delivering data on threat-actor events — had quietly stalled. It was technically strong: the underlying data was genuinely differentiated. But revenue had plateaued, the roadmap had drifted into a feature factory, and the sales team had stopped leading with it.
The challenge
Diagnosis came first, and the honest answer was uncomfortable. The product was not losing on capability; it was losing on clarity. The roadmap was a list of features accumulated from individual deals rather than a strategy. Positioning tried to speak to every security team at once, which meant it resonated with none of them. And because releases rarely moved anything commercially, the team's confidence had eroded — a self-reinforcing loop.
The intervention
A sharper "where to play." Working with sales and the intelligence analysts, we narrowed the target buyer to the teams where the data was decisively better than anything else on the market, and stopped pretending to be for everyone. Positioning, demo narratives and roadmap priorities were all rebuilt around that buyer's actual workflow.
Re-cutting the roadmap around outcomes. The backlog was pruned hard. Everything on it had to answer one question: does this make the chosen buyer faster or more confident in an investigation? Features that couldn't answer were parked, however loud their sponsor. The roadmap got shorter and much more believable.
Rebuilding the engine, not just the message. A relaunch is a delivery commitment, not a marketing event. We set a release cadence the team could actually keep, aligned sales enablement to it, and made sure the first two releases landed visibly with the target buyers. Credibility with the sales organisation was earned back one shipped release at a time.
Board-level honesty. Internally, reporting shifted from feature counts to the metrics that mattered: pipeline influenced, win rates in the target segment, and revenue against the previous year.
The outcome
- In the first full quarter after relaunch, the platform generated more revenue than it had in the entire previous year.
- The sales organisation re-adopted it as a lead product for the target segment.
- The team's delivery cadence held — the relaunch was a new operating rhythm, not a one-off spike.
What I took from it
Stalled products are rarely broken products. They are usually unfocused ones: a good capability diffused across too many buyers and too many features. The fix is less romantic than a rebuild and more effective — choose who it is for, cut everything else, and ship on a rhythm the market can learn to trust.