The gap shows up differently for every client. The cause is always the same.

The store listing said "Save Money."

A gaming publisher launched a title in Germany. The English brief specified a tone for the value proposition. That context didn't survive the handoff. What arrived at the translation stage was a string with no context, no tone guidance, and no one accountable for whether it landed in market.

The title underperformed. The internal explanation was market conditions: a competitive quarter, a crowded window, audience fit. The commercial consequence was attributed to the wrong variable for months. That's the second cost: not the underperformance, but the time spent explaining it wrong.

The community filed the bug before QA did.

A gaming publisher runs live service titles across twelve markets. Forums in KO and JA were surfacing localisation errors within hours of patch deployment, before internal QA had filed a single report.

The failure wasn't quality. The vendors were producing technically correct translations. The failure was accountability: no single owner of the gap between English approval and in-market publication. By the time a patch note cleared English review, the context that made it reviewable had dissolved across four inboxes and two project tools.

The fix wasn't more vendors, more QA, or more review stages. It was one programme, one point of accountability, and a delivery architecture that didn't lose context at every handoff.

Four vendors. Four memories. No source of truth.

A gaming publisher needed consistent IP terminology across forty languages and nine content types at once: in-game text, patch notes, campaign copy, store descriptions, community posts, social, trailer scripts. Same names, same tone, same rules for when a term is translated and when it isn't.

The problem wasn't finding vendors who could handle the volume. It was that no single vendor held enough context to enforce consistency across all of them. IP terms were handled differently depending on who received which brief that week.

The solution was one termbase, held above all of them. Not consolidating to one vendor: building the operations layer that enforced consistency regardless of who did the work.