One product. Four content sources. Forty-seven terminology conflicts. An AI assistant that contradicted itself mid-conversation. This is the story of how content strategy became operational infrastructure — and how language, treated as architecture, started paying for itself.

The Challenge

TechFlow is a 7-year-old B2B project management platform with 50,000+ customers. Halfway through a microservices migration and freshly post-acquisition of an AI analytics tool called Tracklytic, the company's content infrastructure had silently collapsed.

The symptoms were everywhere:

• 47 documented terminology conflicts across web, mobile, API docs, help center, and email
• The same core feature — the organizational container where teams work — was called Projects, Workspaces, Organizations, Team Spaces, Initiatives, and Project Containers depending on who built the surface
• An AI assistant that pulled from all four content sources simultaneously and contradicted itself mid-conversation
• Support costs 68% above industry average ($47/month vs. $28 benchmark)
• 847 confusion-related tickets per quarter, each averaging 22 minutes to resolve
• Enterprise deal velocity down 23% year over year
• A $340K DocuSign deal at risk because a new admin couldn't reconcile the welcome email with the actual product interface
• Localization six months behind across eight supported languages

I was brought in as Senior Content Designer to assess, prioritize, and build a path forward — without derailing engineering or product delivery.

My Role

Lead Content Designer, responsible for:

• Organizational and stakeholder assessment
• Business case development and executive presentation
• Content modeling across six core product concepts
• AI writing assistant documentation and governance framework