Skip to main content

From six-month lags to same-day launches: how Agentic CMS transforms localization 

How a global provider of employee talent assessment software moved localization inside Kontent.ai with Expert Agents, and launched a feature in 13 languages on the same day. 

Written by Madeleine Salisbury

Every global product launch runs on two timelines. The first is the day a feature goes live in English. The second is the day everyone else gets it, and for one global software provider of employee talent assessments, the gap between the two stretched to half a year. 

That's a long time to sit on a finished feature. It's six months of revenue at risk in every market outside English. It's also six months of regional teams asking the same question: when do we get what the English-speaking market already has? 

A launch calendar built around bottlenecks 

The company helps employers hire, develop, and retain people, and organizations in more than 100 countries use its software in 13 languages.  Every word customers see on it comes from a five-person team of psychologists, not content writers, who manage roughly 60,000 content items between them. 

Because that content is rooted in psychological science, word-for-word translation isn't adequate. A term rendered too literally changes what a result means, causing customers to stop trusting the assessment.  

That standard made every product change expensive. One updated screen meant new work in 12 other languages, and each item followed the same manual path: create a draft, send it to a translation provider, wait for linguists, sync it back, review it manually. Even low-risk in-product text, like buttons, login pages, and emails, took two to five days per cycle, longer when the person responsible for the next step was away. 

Across a full release, the delays compounded: the team had capacity to move two or three languages at a time, so features rolled out quarter by quarter. By the time the third language caught up, the product had changed again, and the first group needed updating. 

Built in a day, translated in months 

At the same time, AI was speeding up the company's product development. On a new platform it was building, features that once took three months now took about a day. Translation still moved at the old pace, so every faster release added to the backlog. Run through the old process, the new platform faced the usual rollout: English first, with every other language following over time. 

Moving localization into the workflow 

Instead of adding another tool outside the CMS, the team rebuilt localization inside Kontent.ai's Agentic CMS. Four changes did the work: 

  • Orchestration in the CMS. Aiko, our built-in agent, creates drafts in bulk and moves items into the right workflow step. When English content changes, drafting, translation, and review follow in sequence, without anyone messaging a colleague to ask what changed. 
  • One translation agent per language. Each Expert Agent carries its own glossary and style guide, built with native speakers and the company's channel partners, so every translation starts from approved terminology. 
  • Review agents on every translation. Before anything reaches a person, a review agent checks each translated item against the approved terms and style rules for that language. A single specialist term, used around 1,000 times across the content, has to carry its psychological meaning, not the literal one, and items that miss it get flagged. With well-built glossaries, the team found the agents more consistent at this check than manual review. 
  • People where judgment matters. Agents flag any item they cannot place, and the team reviews only those. High-risk assessment narratives still go to professional linguists, while in-product text and emails move through the agents with lighter review. 

Kontent.ai logs every agent action, simplifying audit reporting. 

From six months behind to same-day launches 

In a live test, the team launched an English feature at the same time as 12 other languages, a first for the company. Simultaneous launch is not yet the default for every release, but the direction is set: language activation is moving from months to days, and smaller releases can go out almost immediately. 

In structured testing over about two months, per-item translation time dropped from around five minutes to a few seconds. A 190-item backlog, which used to take a full day just to draft, was drafted, translated, and reviewed in about an hour. 

None of this reduced headcount. The same five psychologists now spend their time where customers see the value: writing and validating new assessment ad thought leadership content, and refining the glossaries the agents depend on. 

Room to grow into new markets 

The old process set a hard ceiling of two or three languages in motion at once. With agents taking on the drafting, routing, and first-pass review, adding a language now centers on building its glossary and style guide, then letting the workflow run. 

On the new platform, the team no longer plans an English-first rollout. It expects to release every language in quick succession, and it is automating the last manual trigger so that publishing validated English content starts the translation loop on its own. The aim: every market follows within days, not quarters. 

What this means for your launch calendar 

If your product, campaign, or regulatory updates reach English-speaking customers months before everyone else, your workflows create a costly bottleneck. The delay is rarely the translators: It's the manual work between the steps (drafting, routing, syncing, and checking), repeated for every item in every language. With Kontent.ai, Expert Agents take on that work inside the CMS, within the permissions of the people who run them, and your team approves what goes live. 

The same pattern holds where accuracy carries regulatory weight, from financial disclosures to educational material. Review agents check every translation against approved terms, people decide on high-risk content, and every agent action is logged, so speed does not come at the cost of control. 

Three lessons from this team apply to any global organization: 

  1. Start with your most repeated pain point, not your most complex use case. 
  2. Build glossaries and style guides first. They took this team the longest to set up, and they are what make a simultaneous launch trustworthy. 
  3. Give each agent one job or one language instead of building a single agent for everything. 

See what simultaneous launches look like across your markets. Talk to an expert about how Agentic CMS can speed time to market while maintaining accuracy and control. 

Popular articles

Creative team discussing evergreen content
  • For business
The ultimate guide to evergreen content

What if we told you there was a way to make your website a place that will always be relevant, no matter the season or the year? Two words—evergreen content. What does evergreen mean in marketing, and how do you make evergreen content? Let’s dive into it.

Lucie Simonova

A marketer writing a blog post structure
  • For business
7+1 steps to structure a blog post

To structure a blog post, start with a strong headline, write a clear introduction, and break content into short paragraphs. Use descriptive subheadings, add visuals, and format for easy scanning. Don’t forget about linking and filling out the metadata. Want to go into more detail? Dive into this blog.

Lucie Simonova