Industry & Specialised department
Localisation, run as a continuous pipeline
Translation tends to happen in bursts: a launch, a rush, a spreadsheet emailed to a freelancer. Then the product changes and half the translations are out of date. Nexoryl runs localisation as a managed department: a continuous pipeline of translation, review and multilingual QA, connected to your content and code, with terminology that stays consistent in every language.
The first button opens an email to info@nexoryl.com.
You bring
- Source content, strings and files
- Target languages and markets
- Brand voice and key terminology
Nexoryl runs
- Translation
- Review
- Terminology
- Localisation QA
- Release
You get
- Every language live with each release
- Consistent terms across products
- Fewer language bugs in production
- Operating model
- A managed localisation pipeline with glossaries, translation memory, review steps and release tracking per language.
- Delivery model
- Remote. Work runs through your translation management system, repositories or CMS.
- Usual starting scope
- One product or website in two or three languages, then more languages or content types.
- Typical roles
- A localisation lead, translators and reviewers per language, and a localisation QA specialist.
- Runs inside
- Phrase, Lokalise, Crowdin or Smartling, plus your CMS and code repositories.
- Engagement
- A localisation audit, then a monthly retainer or per-release pricing.
Overview
What is localisation?
Localisation is adapting a product, website or content for a specific language and market: translating the words, and also dates, currencies, formats, imagery, tone and anything else that would feel foreign to a local user.
Translation is one step. Localisation also covers the workflow around it: extracting content, keeping terminology consistent, checking the translated product actually works, and keeping every language in step as the source changes.
Nexoryl model
What does Nexoryl's Localisation department do?
It runs your localisation pipeline: preparing content, managing translation and review in each language, maintaining glossaries and translation memory, testing localised products and websites, and keeping languages in sync with every release.
Source content comes from Content or your own teams, localised search optimisation is coordinated with SEO, and internationalisation bugs found in testing go to your developers or Software Engineering.
- Responsible for
- Translation and review management, terminology and translation memory, software and website localisation, multilingual QA and release coordination.
- Not included
- Certified or sworn translations for legal use, live interpreting, and printed materials.
- Connects to
- Content, SEO, Software Engineering and Web Design & Development.
The localisation pipeline
How content moves into every language.
Six stages run on every change, so languages stay in step with the source.
- 01
Extract
Strings, pages and files pulled from source systems, automatically where possible.
- 02
Prepare
Context, glossary terms and character limits added for translators.
- 03
Translate
Human translation, or machine translation with human post-editing where agreed.
- 04
Review
A second linguist checks accuracy, tone and terminology.
- 05
Test
The localised product or site checked for truncation, formatting and broken layouts.
- 06
Release
Translations merged back and published alongside the source.
Where localisation breaks
Four problems a localisation pipeline fixes.
Most of these come from treating translation as a one-off task rather than a process.
Out-of-date translations
- Shows up as
- New features ship in English while other languages lag months behind.
- We look at
- How source changes reach translators.
- What changes
- A continuous pipeline where changed content is translated with each release.
Inconsistent terminology
- Shows up as
- The same feature called three different things in German.
- We look at
- Glossaries and translation memory, if they exist.
- What changes
- A maintained glossary and translation memory used on every job.
Broken localised layouts
- Shows up as
- Truncated buttons, wrong date formats and untranslated strings.
- We look at
- Localisation testing and pseudo-localisation.
- What changes
- Localisation QA before release, with bugs reported to engineering.
Translation without context
- Shows up as
- Translators guess meaning from isolated strings.
- We look at
- What context translators receive.
- What changes
- Screenshots, character limits and notes attached to every string.
What the department covers
Localisation services.
The full pipeline, from extracting content to checking it works in every language.
Translation management
The right linguists, on schedule, in every language.
- Linguist coordination
- Scheduling by language
- Translation and review workflows
- Cost and turnaround tracking
Software localisation
Products that work in every language.
- String extraction and file preparation
- Pseudo-localisation for internationalisation issues
- Plural and variable checks
- Release synchronisation
Website and content localisation
Sites and content adapted for each market.
- CMS page and blog localisation
- Localised SEO metadata with your SEO team
- Marketing transcreation
- Help centre localisation
Terminology
One word for one thing, in every language.
- Glossaries per language
- Translation memory upkeep
- Style guides per market
- Do-not-translate lists
Localisation QA
Problems found before users find them.
- Linguistic review
- In-context visual checks
- Truncation and format testing
- Bug reports to engineering
Machine translation with post-editing
Faster turnaround where quality allows.
- Engine selection support
- Post-editing workflows
- Quality sampling
- Rules for which content is suitable
How remote delivery works
How a localisation engagement runs.
One language and content type goes through the full pipeline first, so the process is proven before it scales.
Step 1: Assess
Content types, languages, tools, existing translations and pain points reviewed.
Step 2: Set up
Translation system connected, glossary and style guides created.
Step 3: Pilot
One language and content type run through the full pipeline.
Step 4: Run continuously
Changes translated, reviewed, tested and released with each update.
Step 5: Report and improve
Turnaround, quality and cost reported monthly.
Machine translation is only used where you agree it's suitable, and published content always gets human post-editing.
Scope and boundaries
What's included, and what stays with you.
Digital localisation only. Certified, spoken and printed work is outside the department.
Included
- Translation and review management
- Software and website localisation
- Glossaries, style guides and translation memory
- Machine translation with post-editing where agreed
- Localisation QA
- Release coordination and reporting
Not included
- Certified or sworn translations for legal or official use
- Live or in-person interpreting
- Printed or physical materials
- Fixing code, which is done by your developers or Software Engineering
- Writing source content (see Content)
What you provide
- Source content and access to your translation system, CMS or repositories
- Target languages and priorities
- Brand voice and any existing glossaries
- In-market reviewers, if you have them
Tools and platforms
Where the work happens.
Connected to where your content and code already live.
- Translation management
- PhraseLokaliseCrowdinSmartling
- Websites and CMS
- WordPress with WPML or PolylangWebflow LocalizationContentful
- Machine translation
- DeepLGoogle Cloud Translation
- QA
- In-context review toolsXbenchStaging environments
Named as examples of tools we work in. They don't imply a partnership or certification.
Measurement
How a localisation department is measured.
Speed and quality together. Fast translations with errors aren't progress.
Speed
- Time from source change to all languages live
- Turnaround per language
- Release lag between languages
Quality
- Errors found in review
- Localisation bugs per release
- Terminology consistency
Coverage
- Languages live
- Content translated versus pending
- Strings with context
Cost
- Cost per word or per release
- Translation memory reuse
- Share of machine translation with post-editing
These are measurement categories, not promised figures.
Who does the work
The people localising your content.
Sized to languages, content volume and release frequency.
Localisation Lead
Owns the pipeline, schedules and quality across languages.
Translators and Reviewers
Translate and review in each target language.
Localisation QA Specialist
Tests localised products and sites and reports bugs.
A good fit when
- Other languages lag behind your main product
- Terminology varies between products or teams
- Users report broken layouts in translated versions
- Translation is managed by email and spreadsheets
Probably not the right fit when
- You need certified translations of legal documents
- You need live interpreters
- You need printed materials produced
Ways to start
Three ways to begin.
The audit shows where languages are falling behind and why.
Localisation audit
Content, languages, tools and quality reviewed, with a pipeline plan.
Language launch
One new language taken live across a product or website as a scoped project.
Managed localisation department
Continuous localisation on a monthly retainer or per release.
Fees depend on languages, content volume and turnaround, and are agreed after the audit.
Questions
Questions about localisation.
If your question isn't here, email us. The answer usually depends on your content types and languages.
What's the difference between localisation and translation?
Translation converts words from one language to another. Localisation adapts the whole experience for a market, including formats, tone and layout, and runs the process that keeps languages up to date.
Do you use machine translation?
Only where you agree it's suitable, and always with human post-editing for published content. Some content, such as marketing copy, is usually better translated or transcreated by people.
Which translation management systems do you work with?
Phrase, Lokalise, Crowdin and Smartling, among others. If you don't have one, we help you choose.
Can localisation be managed remotely?
Yes. Translation systems, CMSs and code repositories are all online, and linguists work remotely by default.
Do you provide certified translations?
No. Certified or sworn translations for legal or official use need an accredited provider.
How do you keep terminology consistent?
With a glossary and translation memory per language, used on every job and updated as the product changes.
Can you localise our WordPress website?
Yes, using plugins such as WPML or Polylang, with localised SEO metadata coordinated with SEO.
What do you need from us to start?
Access to your content or translation system, target languages and priorities, your brand voice, and any existing glossaries.
Next step
Ship every language with every release.
Tell us which languages you need and where translations fall behind. We'll audit the setup and propose a pipeline.