It covers our software localization work for your product release, based on the proposal you accepted, and it’s meant to keep scope, files, and deadlines aligned.
We’ll work the way product teams need it to work: we take your exported resource files and reference material, we translate without touching keys or breaking placeholders, and we hand back files that drop straight into your build. The terms below explain how we run the project and how we handle the common edge cases that can derail a release.
What you get
We’ll do software localization for the target locales you confirm, using the file formats you provide, and we’ll return the same formats back with structure intact so your import does not break. The project covers the deliverables listed below.
We start with a string freeze and export check, then a translation pass with terminology locked for UI labels. We then do build-based LQA and return an issue list you can route quickly, before we hand over the final import set and do a spot-check with you to make sure nothing was missed on key screens.
* Translated resource files * UI terminology glossary * Termbase and notes * Build LQA issue list * Final localized import set * Store listing localization
Payment
To book the work, we invoice 30% of the total price when you sign the proposal. We schedule the project once that invoice is paid. We invoice the remaining 70% when we hand over the finished work.
Every invoice is payable within 14 days of its date. If a payment goes past due, we’ll tell you what’s outstanding and what it means for the timeline. Until the account is up to date, we may pause handover, pause further work (including LQA fixes), or move booked time to the next available slot. We’ll always try to avoid release-day surprises by flagging this early.
Changes
Your project includes two revision rounds. A revision round means we apply your consolidated feedback to our translated strings and supporting assets, and we return updated files in the same formats. It also includes fixes for issues we logged during build LQA that are clearly translation changes.
Anything outside those rounds is treated as a change, and we price it before we do it. The most common case is source strings changing after the string freeze check. When that happens, we’ll list what changed (new keys, edited source text, removed strings, or moved UI), confirm the impact on LQA coverage, and send a quote so scope and invoice stay aligned.
Who owns what
Once the final invoice is paid, you own the translated resource files, glossary, termbase entries, and LQA issue list we produced for your software localization project. You can use them in your product, ship them, and keep iterating on them internally.
We keep ownership of our working files, checklists, scripts, QA patterns, and any reusable tooling we use to protect variables, tags, and file structure. If you ask for editable working files (for example, our intermediate bilingual tables or QA exports), we can usually share them, but they’re shared to help your team maintain the build, not to transfer our internal methods.
Problems and fixes
We take care with the things that can break a build. We do not rename keys, we keep file structure intact, and we keep placeholders, tags, and escape characters exactly as provided. If you spot a translation-caused issue that came from us not following that rule, tell us promptly and we’ll prioritise a fix.
We can’t take responsibility for issues caused by changes to source strings after freeze, broken exports, incorrect platform rules in the files, fonts and layout constraints in the UI, or missing context (for example, a screenshot or the screen a string appears on). Build LQA reduces risk, but it can’t guarantee every screen state your users can reach.
Ending the project
Either of us can end the project by giving notice in writing. We’ll agree the notice period with you in writing based on where we are in the schedule and what your release needs.
If the project ends, you pay for the work completed up to the end date, including any booked time we’ve already committed to your deadlines. Once paid, we’ll hand over what’s finished and usable at that point in the same file formats you provided, plus any notes we have that help your team pick up the thread. If we’re waiting on inputs we asked for (like exports, target locales, or a test build and login path), we’ll also confirm what was missing so you can restart cleanly later.
Signature
