process

How a project runs, step by step

Five steps, in this order. The second one carries the weight: the scope, the price and the timescale exist in writing before any work begins.

brief

You tell us where you are going

Which markets you are heading for, what the product is, and what state the material is in. Nothing has to be tidy at this stage: an incomplete string file and a set of screenshots is enough to have a useful conversation.

from you: The target markets, the designs or screenshots, the language files as they stand, and a note on which screens matter most.
at the end of it: A written answer covering what we would do, in what order, and what we would need in order to do it.

scope

The scope is agreed in writing

This is the step everything else rests on. The scope names the languages, the screens covered, which kinds of work are included, what you receive at the end, the full price in pounds sterling with tax included, and the timescale. It is agreed before work starts, not alongside it.

from you: Confirmation, and any correction to what we have understood. This is the cheapest moment to change your mind about anything.
at the end of it: A quotation you can hold us to, with nothing added to the price afterwards.

work

Translation and adaptation

Terminology is agreed as a list first and then held to. The strings are translated against the job each element does, and the adaptation work included in the scope is carried out on the screens in scope.

from you: Answers to queries. Queries arise on any project of this kind, and a fast answer to one is worth more to the result than anything else you can do at this stage.
at the end of it: Translated files, and annotated designs if adaptation was included.

review

The agreed check

The localisation QA pass runs over the built screens in scope: untranslated strings, cut or overlapping text, inconsistent terms, direction problems and formats that do not match the agreed locale.

from you: A way of seeing the screens that your team is comfortable with. We do not need access to live systems and we do not ask for passwords.
at the end of it: A report listing each finding, the screen it appears on and what we suggest doing about it.

handover

Handover, and implementation if it was included

Everything the scope promised is handed over together, with the findings. Where implementation was written into the scope, the agreed changes are made and described so your own reviewers can go through them; where it was not, your team applies what it chooses to apply.

from you: Whoever will act on the report, so that the handover reaches them rather than an inbox.
at the end of it: Files, designs, report, and a clear statement of anything we found but did not fix because it was outside the agreed scope.

scope.change

When the scope changes halfway through

A market is added, a release moves, twenty screens turn out to be forty, or the check finds something that needs a decision nobody expected to take. Any of that changes the scope, and the scope is what the price and the timescale are attached to.

When that happens the change is quoted before it is carried out, in the same way the original scope was: what it adds, what it costs in pounds sterling and what it does to the timescale. Work that has not been agreed does not appear on an invoice.

If the change makes the original plan the wrong one, we will say so rather than carry on with it.

agreed.in.writing

What the written scope covers

The languages and locales included, named individually.
The screens in scope, and what happens to a screen that is not on the list.
Which of the four kinds of work are included, and which are not.
What you receive at handover, item by item.
The full price in pounds sterling, tax included, with nothing added afterwards.
The timescale, running from the point the last material has arrived.

Payment, cancellation and refunds are set out on the Delivery & Refunds page.

Request a localisation review

Or write to us directly: sale@likelocal.sale