Translation panel

First end-to-end project: a localisation system that let one product ship in 12 languages without 12 separate release trains.

Role: Product manager and program manager — first end-to-end ownership
TEAM: 7-8 developers (front-end and PHP) with QA, UX and design experts, and data analysts; localisation vendors and marketing as stakeholders

Goal

Make localisation a streamlined internal capability rather than a release bottleneck: consistent, fast translation delivery for 12 languages across both the marketing site and the user platform, so market launches stop waiting on copy.

Context

Translations were handled ad hoc across the website and the application. Every new feature or pricing change meant chasing copy, hand-managing keys, and reconciling versions per market, which quietly set the pace for every international launch.

What I did

Framed localisation as a product surface with its own users (marketers, PMs, translators) rather than a support task, and defined the end-to-end workflow from key generation to production commit.
Specified and delivered translation key generation, test environments and versioning, and cache commits, so copy could be staged and verified before release.
Integrated Crowdin for translation management and DeepL for machine-assisted first passes, with Elasticsearch behind content search.
Extended the system into a pricing CMS with preview and versioning per segment and market - the foundation later reused in pricing project.
Coordinated translation vendors, marketing and engineering as a single delivery program across 12 languages.

Outcome

Shipped

Shipped and adopted as the standard localisation path. Directionally: materially lower localisation cost and a shorter time to launch features in 12 languages, with version and preview control replacing manual reconciliation.

Stack & methods

CrowdinDeepLElasticsearch

Visuals