Turning a fragmented platform into a cohesive, value-driven product

This one started with a question I ask most new clients on the first call: "if I asked ten people on your team what the product does, in one sentence, how many answers would I get?" The honest answer here was eleven — one more than there were people on the call.

The platform had grown by saying yes. Every major renewal over eight years had come with a custom request, and rather than push back or generalise those requests into the roadmap, the team had built bespoke modules to close each deal. The result was a product with genuine depth and zero coherent shape — dozens of modules, inconsistent workflows between them, and a value proposition that had fragmented into whatever the last five enterprise contracts needed it to be.

Strong adoption, flat expansion — the same paradox as always

Feature adoption metrics looked healthy on paper because customers were contractually locked into using specific modules. But expansion — the signal that customers see enough value to want more — had been flat for six quarters. Those are two different things, and the team had been reading the first as proof the second would follow. It hadn't, and there was no reason it would without something changing.

Ten customer interviews later, the pattern was obvious: nobody inside these accounts, including the champions who'd bought it, could explain to a new hire what the platform was for in under two minutes. Onboarding a new team member onto the tool took weeks, not because the UI was bad, but because there was no single mental model to hand them. Just a list of modules and tribal knowledge about which ones mattered for which job.

Finding the core, not adding another layer

The instinct in situations like this is usually to build a unifying dashboard — a new layer on top that ties everything together visually. I pushed back on that early, because a dashboard papering over eleven different mental models doesn't fix the eleven mental models. It just adds a twelfth.

Instead, we ran a structured exercise across product, sales, and customer success to identify the one outcome that every single module, underneath its specific feature set, was actually in service of. It turned out every module — however different on the surface — existed to answer some version of "is my team's work on track, and where is it stuck?" That became the spine of the new product narrative: not a list of capabilities, but one central job, with every module positioned as a lens onto that job rather than a standalone feature.

What changed

• Rewrote the core value proposition around the single outcome customers actually hired the product to deliver, replacing the module-by-module pitch that had accumulated over years of custom requests.
• Restructured the roadmap around outcome-driven themes instead of a running list of enterprise asks, so new work reinforced the core narrative instead of fragmenting it further.
• Rebuilt first-week onboarding to teach the one mental model up front, rather than a tour of modules — cutting the ramp time for new users inside existing accounts.
• Set a new bar for future custom requests: anything that couldn't be framed as a lens on the core outcome went into a backlog for evaluation, not an automatic yes.

The hardest part wasn't the strategy work, it was the internal alignment. Getting eight years of "yes" culture to accept that some future requests would now get a "not right now, and here's why" required buy-in from sales leadership before a single line of the new roadmap was public. That conversation took longer than the customer research.

The result

Within two quarters of the repositioning and onboarding rebuild, time-to-value for new accounts dropped 35% — customers were reaching their first meaningful outcome in the product noticeably faster because they understood what they were looking at from day one. Feature adoption across the newly organised modules rose 45%, and — the number that mattered most to the board — expansion revenue doubled, because customers who finally understood the core value proposition could see, for the first time, what "more" would actually get them.