Name an owner for AI-translated pages: split launch cost and update work
For AI-translated overseas pages, estimate launch cost and update work separately, and name the update owner first.
Key points
- Update work remains; AI cuts launch cost
- Name checkers for each of 3 change types
- Name pricing owners and deadlines first
- Separate update work in the proposal
Contents
AI cuts launch cost, but update work remains
A&A perspective
AI translation lowers the cost of translating a page the first time; the update work after publication stays. By update work we mean the effort of revising, checking and republishing each translated page every time the Japanese source page changes.
From the sources
Lokalise is a European company whose localization platform helps global software teams deliver content in multiple languages. In a case study published by Anthropic, the AI company, over 80% of Lokalise's AI translations are described as ready to publish without post-editing. The case study also says customers saved 80% compared with traditional translation methods.
From the sources
According to the case study, the savings come from reducing the need for manual review. Translators choose whether to accept, modify or reject the suggestions the AI produces.
From the sources
Lokalise's CMO also describes what customers expect: with proper context given to the AI, they trust they will see human-like quality for at least 80% of their translations.
A&A perspective
Automate & Augment (A&A), the company writing this article, reads these numbers as describing the first translation of a page. The case study does not cover what happens when the source page changes after publication.
A&A perspective
When the price on the source page changes, the translated page does not change by itself. Someone has to notice the change, retranslate, check and republish. That effort recurs with every change and grows with the number of languages and pages.
A&A perspective
The retranslation step can be made cheaper with AI even during updates. Noticing the change, checking and republishing still fall to people. That remaining effort is what this article calls update work.
Sort changes into three types and name checkers
A&A perspective
The update owner sorts changes to the source page into three types, prices and conditions, policies, and descriptive copy, and names a checker for each type. Once changes are sorted, no single person has to review every change.
From the sources
Anthropic summarized how to build systems that use AI in an article published in December 2024. It describes a pattern that classifies an input and directs it to a specialized follow-up task. The article says this separates concerns and makes it possible to build more specialized prompts for the AI.
From the sources
The article says the pattern works well for tasks with distinct categories that are better handled separately, where classification can be done accurately. Without it, the article adds, optimizing for one kind of input can hurt performance on other inputs.
A&A perspective
A&A applies this pattern to people's responsibilities. Prices and conditions, policies, and descriptive copy differ both in how costly a mistake is and in how they are checked.
A&A perspective
Prices and conditions are changes such as fees, shipping costs or payment due dates, where a single wrong number changes what you promised the customer. Someone who can compare the figures against the source page checks them.
A&A perspective
Policies are changes to terms of use or return rules. The person who decided the content checks that the translation means the same thing.
A&A perspective
Descriptive copy covers product descriptions and reworded headings. Let the AI retranslate it; a read by the person in charge of overseas pages is enough.
From the sources
Lokalise plans to have AI evaluate translation quality so that customers can decide which translations need review and which are ready for immediate publication.
A&A perspective
A&A reads this as a translation company itself treating which translations people review as a decision to be made. For updates too, deciding by type where people look narrows the checking effort to changes in figures and conditions.
A&A perspective
The table below sums up how launch cost and update work differ. Its rows on who owns each cost and what to write in the proposal are used in the last section, when you draft the approval proposal.
| Item | Launch cost | Update work |
|---|---|---|
| When it is incurred | Once, when the page goes live | Every time the source page changes |
| What makes it grow | Volume of pages translated | Number of languages, pages and changes |
| Does AI translation lower it? | Yes. In a European case study, customer costs were reported to be 80% lower than traditional translation | Retranslation gets cheaper. Noticing, checking and recording remain |
| Who owns it | The person who orders the translation | The owner named for each change type |
| What to write in the proposal | The quoted amount | Owner's name, deadline, expected changes per month |
Name pricing owners and deadlines before adding languages
A&A perspective
Before adding languages, name the owner for the pricing pages first and give them a deadline. Prices are a promise to customers. If an old price stays up, every translated page becomes one more mismatch.
A&A perspective
Of the three types in the previous section, prices and conditions are the one where a single wrong number changes the promise to customers. Owners for policies and descriptive copy are named the same way once the pricing pages are running.
Hypothetical example
Here is a hypothetical example for illustration. A company sells a monthly service in Japanese, English and Chinese and changes its price. The Japanese page is fixed the same day. The English and Chinese pages have no owner and show the old price for several weeks.
Hypothetical example
The company decides three things. The person who updates the Japanese page notices the price change and passes it on. The person in charge of overseas pages fixes the English and Chinese pages within three business days of hearing about it. The record of the fix sits with the internal record of the price change. The number of days is hypothetical.
From the sources
Anthropic's article recommends finding the simplest solution possible and only increasing complexity when needed. It says systems in which AI chooses its own steps often trade speed and cost for better task performance, and that you should consider when that trade-off makes sense.
A&A perspective
For updates too, writing the owner and deadline on a single sheet of paper is enough at first. Change notifications and automatic retranslation can be added once languages and pages grow.
A&A perspective
Add tools when, even with the one-page agreement, notices start getting missed and pages with old prices are left up. Until then, having an owner and a deadline written down does more.
In the proposal, separate update work from launch cost
A&A perspective
An approval proposal for launching overseas pages with AI translation puts launch cost and update work on separate lines, down to the update owner and deadline. A proposal with only the launch cost gets approved as a cheap plan, and updates start out as nobody's job.
A&A perspective
The table after the section on change types works as a draft for the proposal. Launch cost is incurred once, when the page goes live, and grows with the volume of pages translated. Update work is incurred every time the source page changes and grows with the number of languages, pages and changes.
A&A perspective
AI translation lowers the launch cost and the retranslation part of updates. Noticing changes, checking and recording remain, so the update work line cannot be left empty.
A&A perspective
On the update work line, write the owner's name, the deadline and the expected number of changes per month. Estimate the number of changes from how often you have changed prices or policies before. The case study does not show how large update work is, so your own numbers are the only basis. On the launch cost line, write the quoted amount.
A&A perspective
Even if you hand translation to an outside service, the update work line does not disappear. Your company is the one that changes the prices and policies on the source page, so the job of noticing changes and passing them on stays with you.
A&A perspective
The right-hand column of the table answers the question your manager will ask: who fixes it, and by when? For a language where you cannot write an owner's name, you may decide to delay its launch until an owner is set.
A&A perspective
If you only translate a company profile whose source page rarely changes, update work is small, and deciding on launch cost alone causes no trouble. The update work line is needed when you translate pages that carry prices or conditions.
Summary
A&A perspective
AI translation lowers the launch cost; the update work that comes with every change to the source page remains.
A&A perspective
Sort changes into prices and conditions, policies, and descriptive copy, and name a checker for each type.
A&A perspective
Before adding languages, name the owner for the pricing pages first and give them a deadline.
A&A perspective
In the approval proposal, put launch cost and update work on separate lines.
In an AI translation plan, estimate the update work that comes with every change to the source page separately from the lower launch cost. What to decide next is who owns the pricing pages and by when they fix them.
FAQ
Can an AI translation service also handle updates?
It can handle retranslation, but the job of noticing that the source page changed and passing it on stays with your company, because your company is the one that changes prices and policies.
How many days should the update deadline be?
There is no fixed number. The three business days in the article's example are hypothetical. The more a page carries prices or conditions, the shorter its deadline should be.
How many languages can we add?
As many as you can write an owner's name and deadline for in the proposal table. Launch a language without them only after an owner is set.
Sources & editorial note
Primary pages read for this article. Publication dates below belong to the sources; access dates record our research.
- Lokalise improves translation quality with Claude
Anthropic · Publication date not stated
Accessed 2026-10-28 - Building effective agents
Anthropic · 2024-12-19
Accessed 2026-10-28