ITT Flygt was a name specifying engineers had trusted for decades. When the global business became Xylem, the risk was not that customers would dislike the new name — it was that a consulting engineer writing a pump specification would keep writing the old one, or worse, specify a competitor rather than pause over an unfamiliar brand. In industrial water infrastructure the buying cycle runs for years, the decision-makers are technically expert and commercially cautious, and trust is transferred through documentation, not advertising. The task was to move hard-won equity from one name to another without a gap in the middle where a specification could be lost.
We led the national communications and education strategy on the principle that in technical markets, authority is earned by being useful before you are needed. Rather than a campaign announcing a name change, we produced the reference material specifying engineers actually reach for — including a technical Pump Station Handbook that became a working reference across the market. A handbook on an engineer’s desk carries the new brand into every project they scope, which no advertisement achieves. Around that sat marketing and advertising content, technical documentation and omnichannel communications, all sequenced so the new name appeared alongside the old consistently long enough for the association to transfer rather than break.
Brand transition strategy and communications architecture · technical content production including the Pump Station Handbook · education-led marketing to specifying engineers · omnichannel advertising and communications · B2B search visibility tracking on technical query sets · AI-assisted bid management within defined guardrails.
Search visibility in priority markets was tracked against the technical query set engineers genuinely use — specification language rather than marketing language — to confirm authority was transferring to the new brand and not stalling on the legacy one. AI-assisted bidding manages efficiency on the paid layer within defined guardrails. Technical content is structured so that answer engines fielding specification questions can cite it accurately, which in a documentation-led market is simply the modern form of being the reference on the desk.
Making the technical library properly machine-readable so it is retrievable and citable by the AI tools engineers now use during specification — the same principle as the handbook, applied to the surface where the question increasingly gets asked first.