The pattern is always the same
Companies don't usually leave their localization vendor in year one. They leave in year three, when the founding project manager has moved on, the brand glossary is six versions out of date, the audit trail nobody asked for is suddenly required, and a regulated launch hits a jurisdiction the vendor turns out not to actually cover. None of these problems show up alone. They arrive as a system. If any of this sounds familiar, it isn't your team's fault.
PM rotation
The person who learned your brand is gone. Industry average project manager tenure at large LSPs is around 14 months. Every rotation is a reset on terminology, tone, and context. Your team trains the new PM. Then the new PM rotates. You absorb the cost of that turnover, even though you never asked for it.
Surprise billing
Surcharges that show up after the work is done. Charges for things you didn't think were billable, things you weren't told were billable, and sometimes things that weren't actually done. One client described their previous vendor as "they charged me even for grabbing a pen." Real-world surcharges routinely run 40 to 60% over the headline rate. The price you signed for is rarely the price you pay.
Subcontracting chains
You signed with one logo. The work is being done by three. Large LSPs routinely subcontract to smaller agencies who subcontract to freelancers. You think you're getting their A-team. You're getting whoever was available that week, two layers removed from the contract you actually signed.
Quality you can't actually measure
Self-reported scores. Auto-generated reports. Sample-based audits that check a fraction of a percent of output and round up. When you ask for per-segment data, you get a slide deck. Real measurement is per-segment, per-language, per-linguist, and audit-ready. Almost nobody does it. Most vendors hope you won't ask.
Specialization that isn't
The "fashion team" and the "healthcare team" share the same linguist pool. They wear different hats for different projects. Real specialization means people who do nothing else, year after year, and accumulate domain knowledge that compounds. The brochure says vertical experts. The roster says generalist.
Quality drift
Year one was fine. Year three isn't. When the same brand goes through dozens of rotating linguists, drift is structural. You see it in revision rates climbing past 5%. You feel it when local teams stop trusting the output and start fixing it themselves on the side, off the books.
Thin coverage where it matters most
"Global delivery" reads well in the brochure. Then you hit a regulated jurisdiction, a niche legal translator requirement, or a language pair the vendor doesn't actually staff in-house, and the cracks show. The only way to know is to pressure-test the specific places your content has to live, before you sign.
They process tickets. They don't run operations.
You bring problems. They fix them, sometimes. They never bring solutions back. Nobody on the vendor side is thinking about your operation, only about the queue in front of them. The difference between processing tickets and running operations is whether anyone over there actually owns your success.
Portal lock-in
The proprietary platform is convenient until you want to leave. Then you discover your translation memories live in their database, in their format, on their terms. Your assets become exit costs. That isn't an accident. It's how the platform was designed.
You shouldn't have to learn a new platform because you changed who does the work.
It isn't bad luck. It's the model.
Large LSPs optimize for margin at scale. Every one of the patterns above is a downstream consequence of that single fact. High project manager turnover happens because retention is expensive. Per-word pricing exists because the margin lives in the surcharges. Rotating freelancer pools are cheaper than dedicated teams. Subcontracting chains exist because the parent company can sell capacity it doesn't actually have on staff. Proprietary platforms exist because lock-in protects revenue. Quality measurement stays vague because real measurement creates accountability nobody wants. None of this is malicious. It's the math of running a billion-dollar service business.
The marketplace alternative trades the platform problem for a different one: zero continuity. A pool of 300,000 rotating freelancers, machine translation first, lightweight quality assurance. Every project starts cold. Your brand voice becomes whatever the next available linguist makes of it that week. The economics work for the marketplace. They don't work for a brand that lives or dies by how it sounds in twenty markets.
If your content is high-stakes, regulated, brand-defining, customer-facing, or just visible enough that errors get noticed, neither model is built to serve you well over time. The system you're inside isn't broken. It's working exactly as designed. The design just isn't designed for you.
What an actual operations partner looks like
We built Kobalt around a different premise: localization is an operations problem, not a sourcing problem. Once you accept that, the answers change. The differences show up in five places.
Same team for years
Some of our clients have worked with the same Kobalt project manager for over a decade. In an industry where 14 months is normal, that's the differentiator. Continuity is what makes brand voice consistent, glossaries useful, and feedback loops short.
Transparent pricing
Every project today is bespoke and gets priced to its specification. When a rush fee, a minimum, or a tech fee is on the invoice, it's because the work justified it, and you knew about it before the work started. No surprise lines. No charges for things that weren't done. Nobody ever billed for grabbing a pen.
Sub-minute response
From the moment you submit a request, your project is live, assigned, and in production in under 60 seconds. Not because we have a chatbot. Because the operation was built around speed.
Under 1% revision rate
Industry average sits between 5 and 15%. Ours is under 1%, measured per language pair, per client, per quarter. When you keep the same team on the account for years, quality compounds instead of decaying.
Tech-agnostic
We plug into your CMS, PIM, TMS, Slack, Notion, or whatever your team already uses. No new portal. No tools to learn. Your translation memories and glossaries stay yours, in formats you can take with you.
Dedicated, vertical-specific teams
Your fashion linguists know fashion. Your healthcare linguists know healthcare. Not because we assigned them this week, but because they've been doing it for years. Specialization compounds. Generalist pools don't.
The three models, side by side
If you're evaluating alternatives, this is the comparison nobody hands you in a sales meeting.
| Enterprise LSP | Marketplace model | Kobalt | |
|---|---|---|---|
| PM continuity | 14-month average tenure | None (project-based) | Same team for years |
| Pricing model | Per-word + hidden surcharges | Per-word, MT-first | Priced to spec, every line explained |
| Response time | Hours to days | Variable | Under 60 seconds |
| Revision rate | 5 to 15% | Unmeasured | Under 1% |
| Linguist model | Rotating pool | 300K freelancer marketplace | Dedicated, vertical-specific |
| Tech | Proprietary portal | Their tools | Plugs into yours |
| Quality measurement | Self-reported | Minimal | Per-segment, per-language, audit-ready |
You own the content. We own the operation.
Switching doesn't have to break your operation
The reason most companies stay too long with the wrong vendor is the perceived cost of switching. We hear it constantly: "We know it isn't working, but the migration would be a nightmare." It usually isn't. Here's what a typical onboarding looks like.
Week 1 — Audit
We map your current setup. Languages, tools, glossaries, brand guides, content types, volumes, the people who own each piece. We meet your team and understand how content flows today.
Week 2 — Extract and integrate
We help you recover your translation memories from your current provider. You own them, even when the contract makes that hard. We integrate into your stack: CMS, PIM, TMS, Slack, whatever your team already uses.
Week 3 — Pilot in parallel
We run a pilot stream alongside your existing vendor. Same content, parallel delivery. You compare turnaround, quality, and how it feels to work with us. No commitment until you've seen it.
Week 4 — Scale
If the pilot lands, we scale. Your team doesn't change tools. Your processes don't break. The work just starts happening differently. Most onboardings take less time than the average enterprise LSP RFP.
Some clients have been with us for over a decade. That isn't an accident.
14+ years
Managing localization for one of Europe's largest healthcare groups. Same lead team across the entire relationship.
12+ years
Running global content for a top-3 European fashion group, across 25 languages and weekly collection launches.
10K/month
Localization requests handled at peak, with 98.7% on-time delivery and a revision rate under 1%.
ISO 9001 + 17100
Certified for quality management and translation services. Audit-ready by design, not by exception.
Find out where your current LSP actually stands
Three minutes, ten questions, an honest read on whether your current vendor is keeping up. We email you a short report at the end. Or skip the scorecard and talk to us directly.