Localization studio · Mclean, VA
You hand us the strings, the help center, the IFU. You get back Spanish, Portuguese and French that a native reviewer has already clicked through inside your build. One fixed fee. Then you ship.
01 What we localize
Your users will forgive a missing feature. They won’t forgive a button that sounds like a machine wrote it.
Every fee below is fixed before we start. Languages run in parallel, so adding a second one doesn’t add a second timeline.
JSON, XLIFF, PO, .strings, ARB, RESX — we work in your files. Includes pseudo-localization, a string-length pass, and a reviewer who plays through your build.
Articles, tooltips, onboarding emails and changelogs, matched to your product’s own UI terms so support tickets don’t start with “what does that button mean?”
Instructions for use, labeling, patient-facing leaflets, and clinical summaries. Two-linguist workflow: a translator, then an independent reviewer, with terminology signed off in writing.
Already translated? A native reviewer runs your staging build or device and flags truncation, gender slips, and tone that falls flat. Annotated screenshots, not a spreadsheet dump.
02 The project we quote most
Spanish, Portuguese and French only. You choose the variant — Spain or Latin America, Brazil or Portugal, France or Canada — and your translator and reviewer live in it.
Words. One fixed fee. In-market QA included. That’s a full app localization at $5,380 per language, and you know the number before we open a single file.
French runs about 20% longer than English. Your “Save changes” button doesn’t know that until a person taps it. We catch it before your users do.
03 Project shapes
These are representative scopes, priced exactly the way we’d quote them. Find the closest one and we’ll adjust from there.
Shape A · SaaS product
Shape B · Medtech
Shape C · Help center
Fees assume clean source files and one revision round. Odd formats or a bigger word count? We re-quote before work starts, never after.
04 The Lantern rule
Your translator drafts against your glossary and translation memory, so the word for “dose” is the same word on screen 4 and in the manual. Then a second linguist, living in the market you’re selling to, uses your product the way your customer will.
That’s the lantern: we walk the dark corners of your UI before you send anyone down them. Truncated labels, formal-versus-casual slips, a date format that reads as next month. We fix those, and hand you the termbase so the next release starts ahead.
Meet the studio →05 Before the quote
Because you need a budget line, not an hourly clock. The fee covers translation, independent review, in-market QA on your build, one revision round, and the updated termbase. We re-quote only if the scope changes before we start.
Anything flagged in QA is fixed at no charge. If your own team finds an error in the delivered files, send it over and we correct it within two business days.
About three weeks from kickoff per language, and languages run in parallel. Need it faster for a launch date? Tell us the date and we’ll say honestly whether it’s possible.
We deliver the translated documents and reviewer sign-off. Your regulatory team files them. We’ll match terminology to the authority you’re submitting to and flag anything that looks off.
06 Start here
Send your file or just describe it. You leave with a fixed fee, a timeline, and the exact list of what we need.
Book my scoping callHours
Weekdays 10am–5:30pm Emails sent after hours get answered first thing.“Ship in Madrid the same Tuesday you ship in Memphis.”The Lantern Yard promise Get your fixed-fee quote
