Software and IT localisation

What we localise

We can help with interface strings, onboarding and error messages, app-store content, help-centre articles, product documentation, release notes and related marketing copy. Short strings need context: a label can mean different things depending on where it appears and what action it triggers.

Provide screenshots, character limits, product terminology and any instructions for variables or placeholders. These details help the linguist understand the content and preserve the elements your software needs.

Files, tags and terminology

Share a representative export and tell us where the translated content will be imported. We will confirm the supported format, handling of tags and placeholders, and the delivery method in the quote. If you use a translation management system, explain your preferred handoff; do not assume a direct connector until we have confirmed it.

We can use your glossary, style guide and previous translations to support consistency between the interface, documentation and marketing content. Agree a contact for queries about ambiguous strings and new terms.

Work around your release schedule

Batch size, review time and source changes affect delivery. Tell us how often content changes, when strings are frozen and when your team needs the translated files. We will confirm capacity and an agreed schedule for the assignment.

If you require linguistic, visual or functional testing in a build, specify the environment and scope. We will confirm which checks we can provide; testing should not be assumed as part of translation alone.

Our production environment uses Wordbee. Where files are exchanged with another platform, share a sample export and the import requirements so we can check the handoff before committing to the workflow.