Failure PatternDecision layer
The Reseller Trap: Why Translation & Localization Retainers Stall at Month Three
Symptom: Client invoices show translation volume growing 30 to 40 percent per quarter while the agency's retainer stays flat, so effective margin per string falls every month. Root cause: The engagement was scoped as platform access plus file handling rather than as a content strategy and QA service, so the agency's value is indistinguishable from the subscription it resells.
By InnovaAI ResearchPublished Updated
How do you recognize it?
- •Client invoices show translation volume growing 30 to 40 percent per quarter while the agency's retainer stays flat, so effective margin per string falls every month
- •Delivery leads spend the first week of each sprint re-exporting strings from a client's CMS because nobody agreed who owns the source of truth
- •Post-launch QA finds tone and terminology drift in German and Japanese builds that passed automated checks, and the client's local market team flags it before the agency does
- •Account managers describe the work as 'running the tool' in internal reviews, and no one can name a deliverable beyond translated files
- •Renewal conversations open with the client asking whether they could just buy the platform license directly, since the agency's markup is hard to justify
Why does it happen?
- •The engagement was scoped as platform access plus file handling rather than as a content strategy and QA service, so the agency's value is indistinguishable from the subscription it resells
- •No terminology or style asset is owned by the agency; glossaries and brand voice profiles live inside the client's vendor account and travel with it if the contract ends
- •Localization is staffed as a production queue with no named owner for linguistic review, so automated output ships unreviewed and quality problems surface in-market
- •Pricing is per-word or per-hour against machine translation baselines, which anchors the agency's rate to the cheapest possible comparison
How do you fix it?
- •Rewrite the scope document this week to sell three named deliverables (terminology system, in-market QA pass, multilingual content calendar) and price them separately from any platform fee
- •Export the client's glossary and style rules into an agency-owned master file, then version it in the agency's own repository so the asset survives a platform change
- •Add a mandatory human review gate on the top 20 revenue pages per locale before any automated publish, and log reviewer sign-off in the delivery ticket
- •Reprice the next renewal against a fixed monthly retainer with a defined locale count and review SLA, not against per-word translation rates