SaaS & mobile apps

SaaS & app localization
that ships with each release

A website is translated once and revised now and then. A product that ships every week is never finished — strings turn up in small batches between releases, and the release cannot sit waiting for a language. So we set this up as a standing arrangement rather than a project with an end date.

  • Interface strings and microcopy
  • Small batches between releases
  • Help centres kept current
  • Wording consistent months later
  • Linguistic QA before you ship
Get my quote
Same-day answer

Get your quote

Send us your current strings, or just tell us what you ship and how often, and we will reply with a fixed price.

Your documents

    What comes to us between releases

    Rarely all at once, and rarely in large pieces. This is the material a shipping product generates week by week.

    Why a shipping product is different

    Nothing here is about file formats. It is about a product that changes faster than a translation project can be scoped.

    • Batches, not a project

      There is no final word count to quote against, because the product is never finished. Work arrives as it appears — a new screen, three changed labels, a rewritten setting — and is handled at that size.

    • The release does not wait

      We agree in advance when strings reach us and when they come back, so translation sits inside your release rhythm instead of interrupting it. A language is not what holds up a build.

    • The tenth batch reads like the first

      Months pass between batches. Your terminology database holds the product names, the interface wording and the tone, so a feature named in March is still named that way in November.

    • The words around the product count

      Help centre, knowledge base, in-product mail, notifications, release notes. Together they are usually more words than the interface, and they are where users go when the interface confuses them.

    How the arrangement works

    1. 1

      Tell us what you ship

      What the product does, which languages you need, roughly how often you release, and whether the help centre comes with it. A test account or a set of screenshots tells us more than any brief.

    2. 2

      We agree a cadence

      When strings reach us, when they come back, and who sends them. Each batch gets a confirmed delivery date before you commit to it — no work starts on a maybe.

    3. 3

      Batches come as they appear

      New and changed strings between releases, however you already get them out of the product. Nothing is too small to send: one dialog is a perfectly normal batch.

    4. 4

      Back in step with the release

      Translations return for the release they belong to, checked against the terminology already in use. If you want the strings looked at inside a build before it goes out, that pass happens here.

    Your help centre is the bigger job

    Most of what your users read is not in the product, and not on your website either. It is in the help centre — the article explaining the setting nobody can find, the page about billing, the troubleshooting piece support links to twenty times a day. That library grows every week, and it grows faster than the interface does.

    When it is maintained in English only, nothing breaks visibly. Users in the other languages quietly switch to the English article, or give up and write to support. You see it as support volume, not as a translation problem, which is exactly why it goes unfixed for years.

    So the help centre travels in the same standing stream as the interface: new and rewritten articles come to us as they are published, and they inherit the terminology already fixed for the product. An article calls a button exactly what the button calls itself — which is the difference between a help page that resolves a ticket and one that creates it.

    If the library is too large to take on in one go, we start with the articles support links to most often and work down. That order is yours to set, not ours.

    Happy to be of service,

    Founder

    Languages for your product

    These are the languages product teams ask us for most often. If the market you are opening is not here, tell us which one it is.

    • German
    • English
    • Spanish
    • French
    • Italian
    • Norwegian
    • Arabic
    • Chinese
    • Japanese
    • Romanian
    • Portuguese
    • Polish
    • Swedish
    • Finnish
    • Thai
    • Russian
    • Greek
    • Ukrainian
    • …and many others
    EnglishPortugueseSwedishGermanPolishGreekSpanishDutchTurkishFrenchRomanianJapaneseArabicUkrainianMandarinItalianRussianNorwegian

    Frequently asked questions

    Tap any question to see the answer!
    We ship every week. Are small batches really workable?
    They are the normal case here, not the exception. Once the arrangement is set up there is no scoping round per batch — you send the new and changed strings as they appear, we confirm the date, and they come back for that release. Forty words is a batch.
    What happens if a release comes before the translation is ready?
    That is what agreeing a cadence prevents, and the honest answer is that it is usually a question of when strings reach us rather than of translation. If something genuinely lands late, you ship the English and the language follows in the next update — but you decide that, and you know beforehand.
    Do you handle our help centre and knowledge base too?
    Yes, and you should assume it is the larger half of the work. Articles come to us as they are published or rewritten, using the same terminology as the interface. A knowledge base translated once and then left alone is worse than one that was never translated, because it now confidently describes a product that has moved on.
    How is this different from having our website translated?
    A website is a project: it has a word count, a start and a finish, and it gets revised occasionally afterwards. A product has none of those. The work is set up as an arrangement that runs alongside your releases, and the thing being managed is consistency across months of small pieces rather than delivery of one large file.
    Will the wording stay consistent over months of small batches?
    That is what the terminology database is for. Product names, feature names, interface labels and the tone they are written in are recorded once and applied to every batch after it, and a second linguist revises the work. Otherwise the tenth batch renames half your product.
    Do you need access to the product?
    It helps enormously. Strings arrive as a list with no context, and a list is where wrong translations come from — "Open" is a verb or an adjective, and only the screen says which. A test account, screenshots, or even a note beside the ambiguous strings resolves most of it before it becomes a bug.
    Can you check the translations inside the app before release?
    Yes. A linguist goes through a build in the target language looking for what a string list cannot show: text overflowing a button, truncation, a word that is right in isolation and wrong on that screen, and strings that were never sent for translation at all. You get a list with screenshots; you fix it in code and we supply the corrected wording.
    What does it cost?
    Nothing on this site is priced, because it depends on the languages, the volume and how much of it your memory has already seen — and for a product, repetition is high. Send us the current strings and a sample of the help centre, and you will have a fixed price. Nothing starts before you have seen one.