Leading Enterprise Data Storage Company

The decision to rename an established tech company with a $24B market cap is not to be taken lightly. As a first step, we were hired to work side by side with our client’s research partner to design name equity research studies. We designed questions that not only pressure tested our hunch that the name might need to change but that also helped us identify which parts of the existing name might be maintained as an equity bridge.

Renaming a publicly traded, globally recognized technology company is not a naming project — it's varsity level organizational change management. The name has to launch right. That means aligning leadership, preparing customers and partners, sequencing the announcement with other business news, and making sure the story behind the change is told with enough clarity and confidence that it reads as momentum rather than disruption.

We worked closely with the executive team through the strategic development of the name and the rationale that would carry it into the world. The company framed the rename explicitly as a non-disruptive upgrade — borrowing the language from their existing naming architecture to explain the brand evolution to customers. Like the platform itself, the identity was being upgraded without breaking anything. The values hadn't changed. The standards hadn't changed. Only the name — and what it was now capable of representing — had.

The company began trading under the new name on the New York Stock Exchange shortly after the public announcement, with the existing ticker symbol unchanged. The rename was timed alongside a major strategic acquisition that further extended the platform into advanced data intelligence and AI readiness — ensuring the new name had immediate and concrete business substance behind it from day one.

The old name did exactly what a great product name should do: it told you what the product was. Clean, confident, and completely on-brand for a company that had built its reputation on the purity and performance of its storage architecture. The problem was that the name had become a ceiling. As the company expanded from storage infrastructure into comprehensive data governance, dataset lifecycle management, AI readiness, and enterprise data intelligence — with an acquisition strategy to match — "storage" was no longer the right organizing word for the business.

The rename came at a high-stakes moment. This is a publicly traded company (NYSE) with a global footprint, a loyal enterprise customer base, and a portfolio of existing product names deeply tied to the parent brand. The new name needed to honor that equity without being constrained by it. It needed to work at the level of the company's ambition — signaling a genuine evolution, not a rebrand for its own sake — while remaining rooted in the core promise that had made the brand great: reliability, innovation, and a commitment to customer outcomes that never wavers.

A corporate rename doesn't happen in isolation — when the parent brand changes, every name that flows from it is thrown into question. Before the rename was decided, we conducted a structured audit of the existing product name portfolio: mapping the it against its underlying naming logic, identifying where conventions were working, where they had drifted across a decade of growth and acquisition, and where sub-brand relationships were harder to parse than they should be. From that audit came a set of standardization recommendations — clarifying the conventions governing the hardware product families, aligning the treatment of version and variant modifiers, and establishing clearer principles for how acquired brands with equity of their own would be positioned relative to the parent.

The second phase came once the new corporate name was in motion. With a new parent brand now anchoring the architecture, we worked with the team to determine which product and platform names would carry the new identity forward, which had enough equity to stand largely unchanged, and what the governing logic should be for any name that came next. The goal wasn't to rename everything — unnecessary disruption to established names carries real cost in enterprise markets where customers rely on them in procurement cycles and support relationships. The goal was to give the team a clear, principled framework for making those decisions confidently, and an architecture coherent enough to support the company's next chapter.