Arbor Systems sells a data governance platform to regulated enterprises — banks, insurers, hospital networks. The product was technically strong and had a handful of genuinely happy customers, but it had been launched twice in three years under two different names, and neither launch had moved pipeline.
The problem was not awareness, it was that nobody could say what the product was for. Marketing described it as a data governance platform, sales sold it as a compliance tool, and our two happiest customers had bought it to solve a data cataloguing problem that neither of those descriptions mentioned. Every deal took a different shape because every deal started from a different story, and the analyst firms had placed us in a category we lost almost every time we competed in it.
I started with the customers who had renewed rather than with the pitch deck. Thirty interviews across the installed base made one thing clear: the product won when it was bought to answer "who touched this data, and when", and lost whenever it was positioned as a governance suite against incumbents ten times our size. We repositioned around that narrower job and rewrote the entire messaging hierarchy behind it. The hardest part was retiring the governance-suite language everywhere it already lived, including the analyst briefings. Sales got a competitive kit built around the three vendors we actually met in deals rather than the twelve in the category. We deliberately did not run a third launch.
Pipeline influenced went from $2.4M to $9.1M over the following year, and inbound-attributed revenue from $620K to $2.35M. Click-through on paid and email went from 0.9% to 3.1%, which was the earliest signal that the new language was landing — it moved months before any of the pipeline numbers did.
The instinct after two failed launches is to launch again, louder. What the product actually needed was a smaller claim that happened to be true. The most useful thing I did was thirty customer interviews, and it cost nothing but six weeks.