Software & App Localisation

They are TMS platforms — they hold your strings, but they don't translate them. You still need a vendor. Most SaaS teams end up stitching a TMS together with a roster of freelancers and one big LSP for the regulated bits. We collapse that into one UK partner with our own secure portal, our own linguists, multi-engine AI routing, and direct integration into your existing TMS if you already run one. Fewer suppliers, one contract, one invoice.

Yes. 15-minute demo, sandbox workspace, no sales theatre. You can run a test translation through all five engines and compare outputs before you pick a plan. Book a demo.

Software: JSON, XML, XLIFF, PO/POT, YAML, .strings, .stringsdict, .resx, .properties, CSV, ICU MessageFormat. CMS: WordPress (WPML, Polylang, Weglot), Shopify, Headless (Contentful, Sanity, Strapi), Drupal, custom via API. Version control: GitHub, GitLab, Bitbucket. TMS: Phrase, Lokalise, Crowdin, Transifex, Smartcat, Memsource. E-learning: Articulate 360, Storyline, Rise, Captivate, SCORM.

We connect to your repo or TMS via webhook. When developers commit a new string, our system detects it, routes it to the right engine for a draft, queues it for linguist review, and returns the finished translation — typically inside 24 hours. Translation memory ensures terminology stays consistent across every release. Localisation stops being a release bottleneck.

Five stages: (1) AI-drafted translation routed per content type. (2) Native linguist review with full context. (3) Second-linguist signoff for accuracy and tone. (4) Pseudo-locale and visual QA for truncation and layout. (5) In-market sanity check for cultural fit. Every stage is logged inside LingoSecure with a full audit trail. No unreviewed strings ever ship.

Yes — Arabic, Persian, Urdu and Hebrew are our core specialism. Mirrored layouts, bidirectional text handling (English numbers inside Arabic paragraphs), font verification on real devices, and RTL-specific visual QA. We don't charge the 20-30% RTL surcharge most agencies add because this is the work we do most.

Local keyword research for each market — we translate search intent, not words. Proper hreflang implementation (the #1 cause of international SEO penalties). Localised meta titles, descriptions, URL structures, and Search Console setup per locale. First 100 words of every page engineered for AI search (ChatGPT, Perplexity, Google AI Overviews) which now trigger on 60%+ of queries before any click.

Yes. We plug into Phrase, Smartcat, Lokalise, Transifex, Crowdin, Memsource and others. If you already have a TMS, we work inside it as your linguist layer. If you don't, you use LingoSecure. Either way you keep the translation memory — it is yours.

We price per project, not per word, for enterprise pipelines — and the number depends on your content volume, language count, engine mix, and review depth. Starting budgets: a small SaaS product in 5 languages runs from a few thousand pounds to set up and a retainer after that. Larger programmes with 10+ languages and continuous updates are scoped directly. Tell us what you're shipping and we'll send a scoped number within 24 hours.

Yes. We execute DPAs and NDAs before any file is uploaded. LingoSecure is GDPR-compliant with AES-256 encryption at rest, TLS in transit, per-user audit logs, IP allowlisting on request, and optional bring-your-own-key (BYOK) for enterprise. Source strings stay inside the portal — never on freelancer laptops.

Yes. We adapt legal strings (terms, privacy, cookie notices, consent flows) for GDPR (EU), CCPA (California), LGPD (Brazil), DSA (EU), and other jurisdiction-specific regimes. For heavily regulated copy (finance, healthcare, gaming) we assign translators with subject-matter expertise and flag anything that needs target-market legal review.

We retain you monthly for ongoing updates: new features, blog posts, help centre articles, product launches. Quarterly audits flag outdated or stale translations. SEO performance monitoring per locale. Rapid fixes (24-hour turnaround) when something breaks. You get one named PM and one named account owner — not a ticketing queue.