I had a conversation recently with a product manager at a multinational industrial manufacturer. We were talking about how his organization handles content across markets. I asked a simple question: who does the localization? He laughed. Nobody is dedicated to it. It lands on whoever has the best English. Or the best patience. Product managers, marketing coordinators, and sometimes assistants. They translate between meetings, between deadlines, between their actual responsibilities. There is no localization team. There is no budget for one. There is a folder full of Word documents and a group of people doing their best.
The pattern nobody measures
This is more common than most people think. Headquarters produces content: product descriptions, marketing campaigns, technical documentation, internal communications. It flows outward. And at every local office, someone absorbs the cost of making it work in their market.The content volume keeps growing. AI makes it easier to produce content at scale. Marketing teams publish more, product teams document more, compliance teams regulate more. None of this increased output comes with increased localization resources at the local level.CSA Research data tells part of the story: content volumes are rising while dedicated translation budgets decline. But the work doesn't disappear. It shifts to people who aren't measured on it, aren't trained for it, and aren't compensated for it.73% of localization managers report spending more time on coordination than strategic work. That's people who have "localization" in their job title. Imagine the figure for someone whose job title is "Product Manager, Iberian Peninsula."
The hidden costs
When localization happens informally, the costs are real but invisible. They don't show up on a localization budget line because there isn't one. They show up everywhere else.
Time. A product manager spending five hours a week translating marketing materials is a product manager not spending those five hours on product work. Multiply that across every local office and the number gets significant fast.
Quality. People doing translation as a side task don't have terminology databases or style guides. They make judgment calls in isolation. One office translates your brand tagline one way. Another office translates it differently. Nobody catches it because nobody is looking.
Consistency. Without centralized processes, every market develops its own version of your brand voice. The German office sounds formal. The Spanish office sounds casual. The French office went a different direction entirely. Over time, you don't have one brand in twelve languages. You have twelve brands.
Speed. When translation depends on whoever has a free afternoon, launch timelines slip. Local offices become bottlenecks not because they lack talent, but because the work competes with everything else on their plate.
Talent drain. The people absorbing this work are often your best local employees. The ones with the strongest language skills, the deepest product knowledge, the most cultural awareness. And you're using that expertise for a task that could be systematized.
Why companies end up here
Nobody plans for this. It happens gradually.
A company starts with one or two markets. The local teams handle translations. It works fine. The volume is manageable. Then the company grows. More markets, more content types, more channels. The approach that worked for two markets doesn't scale to twelve, but nobody has the bandwidth to fix the process because everyone is too busy translating.
There's also a visibility problem. When localization happens inside local offices, headquarters doesn't see the effort. It looks like content just arrives in the local language. The cost is invisible, so nobody builds a business case to address it. The pain stays local.
And there's the perception issue. Translation looks simple from the outside. "You speak Spanish, right? Can you just translate this?" It's a question that underestimates the difference between speaking a language and producing professional content in it.
Signs you've outgrown the DIY model
If any of these sound familiar, the informal approach has probably run its course:
-
Local teams are consistently behind on content launches
-
Brand messaging varies noticeably between markets
-
Your best local employees spend significant time on translation
-
Nobody can tell you how much localization actually costs across all offices
-
Quality issues surface through customer complaints rather than internal review
-
Content sits in a queue because the person who does the translations is on holiday
What actually works
The companies that solve this don't necessarily throw money at it. They make a structural shift: from localization as an informal task distributed across local offices to localization as a managed operation with clear ownership.
That can take different forms.
Build an internal team. Some companies create a centralized localization function. This works if you have the volume to justify dedicated headcount and the expertise to manage linguistic quality, terminology, and tools. For most mid-market companies, the investment is hard to justify.
Use a platform. Translation management platforms can systematize the workflow. Files go in, translations come out. The technology is real, but platforms don't solve the quality problem. Someone still needs to review, manage terminology, and make cultural decisions. If that someone is still the product manager in the local office, you've automated the routing but not the work.
Partner with a specialist. An external localization partner absorbs the operational complexity. The right partner doesn't just translate files. They manage the workflow, maintain terminology, preserve brand voice, and free your local teams to do their actual jobs.
The common thread: someone has to own localization as a responsibility, not as a favor.
Making the invisible visible
The first step is usually the simplest and the hardest: measure it.
Ask your local offices how much time they spend on translation. The number will surprise you. Calculate the loaded cost of that time. Compare it to what structured localization would cost. In most cases, the DIY approach is more expensive than any of the alternatives. It's just that the cost is hidden in salary budgets rather than sitting on a localization line item.
56% of consumers prefer buying in their native language. Every $1 invested in localization generates $25 in incremental revenue, according to CSA Research. The ROI case isn't hard to build once you know what you're actually spending.
The product manager I spoke with knows all of this. He's lived it. His local teams are doing their best with no support, no tools, and no recognition for the work. The content keeps coming. The resources don't.
If that sounds like your organization, the question isn't whether to change the model. It's how long you can afford not to.
Photo by Christina @ wocintechchat.com M on Unsplash
