You send us your strings files (JSON, XLIFF, PO, CSV or any format), your product context and your glossary if you have one. We assign your Tech PM and a specialized team, localize with full QA and return ready-to-import files. From the second sprint onward, translation memory kicks in and only new or changed strings need translation.
We work with any file format your stack uses. While we don’t directly connect to Lokalise, Phrase or similar TMS platforms via API (we use our own workflow), we can receive exports from and deliver imports to any platform. Our PM adapts to your toolchain. If you need a specific integration, tell us and we’ll scope it.
We set up a sprint-based localization cycle aligned to your release cadence — weekly, biweekly or monthly. Each cycle, you send us the new or changed strings and we process only the delta. Translation memory handles the approved segments automatically, so you only pay for genuinely new content. Over time, costs decrease as TM coverage grows.
We cover 40+ languages with tech-specialized linguists. Our strongest coverage is in European languages (EN, DE, FR, ES, IT, PT, NL, PL, RU, SV, DA, FI), East Asian languages (JA, KO, ZH-S, ZH-T), and key growth markets (AR, TR, HI, ID, TH). For right-to-left languages like Arabic and Hebrew, we include layout and functional QA.
Our LQA process covers four dimensions: (1) Contextual review — does the translation make sense in the actual UI context? (2) Functional testing — do strings fit their containers without truncation? (3) Cultural validation — is the tone appropriate for the target market? (4) Consistency check — does every string match the product glossary? We deliver a QA report with all findings before final delivery.
Translation memory stores every approved segment we produce. When the same or similar string appears in a future sprint, it’s automatically retrieved and applied — no need to retranslate. This creates a compounding effect: the longer we work together, the higher the TM coverage and the lower the cost per sprint. Full matches are priced at a significant discount versus new content.
Credits let you pre-purchase localization capacity and consume it across sprints without a separate purchase order for each project. Credits are deducted based on word count, service type and language combination. They don’t expire and can be used across any service — software localization, QA, help center content or other. Preferred and priority conditions apply based on credit tier.
Antes de irte
