Software Localisation
Handles software localisation against the terminology list you supply, or one we build.
Assessed first, quoted after
Technology Industry Translation
Applies to Technology Industry Translation; anything that depends on the recipient is confirmed in writing.
Software LocalisationIT Services TranslationAi/ml Technical TranslationSaas Product Translation
What we confirm before quoting
Requirements and review steps are documented rather than promised in advance.
Software LocalisationIT Services TranslationAi/ml Technical TranslationSaas Product TranslationAPI Documentation TranslationUx/ui Content Localisation
Where each angle lives
Software Localisation
Read next if you need software localisation.
Open →
IT Services Translation
Pairs with it services translation in most project sets.
Open →
Ai/ml Technical Translation
Often requested alongside ai/ml technical translation.
Open →
Saas Product Translation
Pairs with saas product translation in most project sets.
Open →The edges of this scope
Values that depend on the document stay pending until intake confirms them.
| Item | How it is handled |
|---|---|
| Software Localisation | Accepted. Handling is confirmed at intake and recorded on the order. |
| IT Services Translation | Accepted. Handling is confirmed at intake and recorded on the order. |
| Ai/ml Technical Translation | Accepted. Handling is confirmed at intake and recorded on the order. |
| Saas Product Translation | Accepted. Handling is confirmed at intake and recorded on the order. |
| API Documentation Translation | Accepted. Handling is confirmed at intake and recorded on the order. |
| Ux/ui Content Localisation | Accepted. Handling is confirmed at intake and recorded on the order. |
What sets this apart
Applies to Technology Industry Translation; anything that depends on the recipient is confirmed in writing.
IT Services Translation
Available for it services translation on the same review path.
Ai/ml Technical Translation
Handles ai/ml technical translation against the terminology list you supply, or one we build.
Saas Product Translation
Handles saas product translation against the terminology list you supply, or one we build.
API Documentation Translation
Available for api documentation translation on the same review path.
Ux/ui Content Localisation
Handles ux/ui content localisation against the terminology list you supply, or one we build.
The shape of a case entry
A case entry is published here only once it can be tied to a specific file set and a verifiable outcome. Until then this section shows the record structure only.
| Field | What it will record | Status |
|---|---|---|
| File type | The document set and language pair, as received. | Awaiting verified evidence |
| Challenge | What made the file difficult — layout, terminology, or an unclear requirement. | Awaiting verified evidence |
| Workflow | Which review steps ran: translator match, proofread, terminology and layout check. | Awaiting verified evidence |
| Outcome | What was delivered, and against which written requirement. | Awaiting verified evidence |
No customer names, figures or outcomes are shown until the underlying evidence is attached.
Get a written scope before you commit
We review the document, confirm the language pair and the receiving institution, then send pricing and turnaround in writing.
What matters here
The working method
Where Technology Industry Translation fits, and the parts we cannot confirm without seeing the file.
Software Localisation
Pricing for software localisation is confirmed after intake and does not move afterwards.
IT Services Translation
Every it services translation request gets a named contact and a written turnaround.
Ai/ml Technical Translation
Documented handling for ai/ml technical translation, stated up front.
Saas Product Translation
Second-reader review is mandatory on saas product translation — not an optional add-on.
API Documentation Translation
Requirements for api documentation translation are checked against the receiving institution, not a generic standard.
Ux/ui Content Localisation
Requirements for ux/ui content localisation are checked against the receiving institution, not a generic standard.
Get a written scope before you commit
We review the document, confirm the language pair and the receiving institution, then send pricing and turnaround in writing.