Field Notes: How to Negotiate With Your TMS

About this episode

Your translation management system might not be failing, but it can still be quietly throttling your localization program. Stephanie and Giulia Greco unpack why many client-side localization professionals feel stuck right now: TMS platforms that looked “end to end” in the sales cycle start showing real product gaps once you add more content types, more stakeholders, tighter release cycles, and more languages. The result is a mix of stalled automation, awkward workarounds, and the sense that you’re always one workaround away from breaking something important.

We get concrete about what to do next without pretending there’s a perfect answer. We talk through the three paths most teams face: stay and cope, migrate and brace for cost plus politics, or build solutions alongside your TMS and figure out how to sustain them. Then we shift into a practical strategy that helps either way: think like a product manager. Document the painful use cases, write crisp requirements, quantify impact, and take your vendor a business case instead of a complaint. We also get candid about influence, including the uncomfortable truth that vendor attention often tracks with spend and how smaller teams can still move the roadmap through clearer arguments, better storytelling, and showing up as a beta partner.

Finally, we explore why AI localization has changed the build-versus-buy equation. Giulia shares a smart pattern for using an LLM translation workflow safely: start with a narrow slice of content, use native-speaker linguists to correct output, feed those corrections back, and iterate until quality is ready for production. If you’re wrestling with TMS limitations, vendor roadmaps, and the future of language operations, this one will give you a clearer next step. Subscribe, share with your localization team, and leave a review with the biggest TMS gap you want solved.