Sudharsanam Narasimhan

The Model Wasn't the MOAT: How 10 Design System Engineers Turned Platform Knowledge into Enterprise AI

Most enterprise AI strategies begin with models, central AI teams, and a list of potential use cases. We started somewhere else: with a platform organisation that already shaped how more than 2,000 frontend engineers built software.

A team of 10 engineers working across design systems, internationalisation, and accessibility had something a general-purpose model did not: deep organisational context, trusted workflows, enforceable quality standards, and a distribution path into nearly every product team.

We first transformed our design system into an AI-native platform. Structured content, AI skills, and Model Context Protocol capabilities gave developers and coding agents access to the same product knowledge. This raised the quality floor for AI-generated UI by helping generated code align with our components, styling conventions, accessibility expectations, and platform requirements.

In controlled frontend development tasks, measured implementation accuracy improved by 52% and task completion time fell by 34%. We then introduced a new operating model that replaced slow manual review gates with distributed ownership and automated quality enforcement. Cross-product component development that previously took months could move in days.

We applied the same strategy to localisation, a $3 million annual cost base with volume growing 272% year over year. A 45-day evaluation compared five AI pipelines with our existing vendor across 22 languages. The findings changed our build-versus-buy decision and created a pathway to up to $2 million in annual savings. But AI translation only works if the source code is clean. AI translating messy source just produces the wrong translation faster. So we ran two bets that reinforced each other: AI drafting every translation with human review, and AI-powered linting that fixed the source before it ever reached translation. The strategic advantage was not simply lower cost. It was owning the feedback loop: every human correction improved prompts, glossaries, style guidance, and future translation quality.

Internationalisation exposed another platform opportunity. We resolved more than 20,000 issues across the codebase by combining codified domain rules, automated remediation, and platform-level enforcement. What had previously looked like an unbounded manual cleanup effort became a repeatable engineering system.

Accessibility presented a similar scaling challenge. With more than 10,000 identified issues, no central team could remediate the backlog manually. We began building an AI accessibility remediation factory using pattern-based batching, orchestrated agents, automated validation, and feature-gated pull requests. The goal was not only to clear a backlog, but to move accessibility intelligence earlier into the development lifecycle so developers and agents could prevent issues while software was being created.

This talk presents a practical leadership and architecture framework for identifying where platform teams create genuine AI leverage, deciding what to centralise, choosing when to build or buy, and turning experiments into durable organisational capability.

The model was not the moat. The moat was the organisation's ability to turn domain knowledge, feedback loops, quality standards, and distribution into systems that AI could reliably use.