← Winston Diaz

Alarm.com · 2013–2022

Global Localization at Scale

Localization & Internationalization Lead

Built and led Alarm.com's localization function from scratch, a critical enabler of the company's expansion from 2 countries to 40+, growing international subscribers to 1.3M and international revenue to $33M.

$33M
international revenue (from $0)
1.3M
international subscribers (from 0)
40+
countries (from 2)
75%
shorter time to market (12+ mo → 3 mo)

The problem

Alarm.com built its home security and smart-home product in the US, but growth meant taking it into dozens of international markets, each with its own language, data formats, international compliance, and customer expectations.

Localization ran on a manual, engineering-dependent process: getting localized strings imported meant months of asking engineering for the time. Early launches into Central and South America had the runway to make that work, since the internationalization prep, the process for Spanish wasn't especially challenging, and there was no rush, but it was clear the approach wouldn't hold up as the company kept expanding.

Automating early

A manual, ask-engineering-for-months process isn't how I like to operate, so I started automating from early on. I implemented a translation management system to replace it and built out automation and tooling around it that grew steadily over the next several years.

What I built

By the third year of international expansion, Alarm.com was launching in multiple countries at once, moving from Central and South America into Australia, Europe, the Middle East, and the process had to scale to keep pace. I joined the early beta of Google's AutoML Translation and started the first experiments of what eventually became a continuously-retrained pipeline of 20+ translation models across locales, integrated into the release workflow so localized versions shipped alongside the US English releases.

On the process side, I got leadership buy-in to institute mandatory localization timelines and quality-control gates for web, mobile, and hardware before any new-market launch, which changed how we sequenced the entire market-expansion roadmap.

The impact

The pipeline cut time to market for new markets from over a year to about three months, and closed the lag between US English releases and localized releases from three months to same-day for most products. I joined Alarm.com's international expansion effort about a year into its existence and built and led localization for 8+ years, a critical enabler of the company's growth from two countries, the US and Canada, to more than 40, with international subscribers growing from zero to 1.3 million and $33M in international revenue that hadn't existed before.

The pipeline also delivered near-real-time, high-accuracy translations and lifted customer satisfaction, engagement, and retention in 80% of markets, with each successive wave of concurrent launches going more smoothly as the pipeline and process matured.

The work enabled market expansion and multimillion-dollar B2B agreements across Europe and Latin America, including the Securitas partnership's European launch.

How it worked

Four codebases flow through extraction, Crowdin (paired with fine-tuned AutoML models), and auto-translation in 17 locales, then human review, Bitbucket PRs, automated QA, and release. Two Jira loops feed issues back upstream.

Fixing a broken handoff

One of my project managers was struggling with our international marketing team, whose requests kept arriving only a couple of days before their planned release, leaving no real time to translate or proofread. He was stressed and starting to take it personally. The first thing I did was make sure he knew it wasn't his fault: the quality problem was a direct result of not having reasonable time to do the work. From there, we fixed the process itself:

  • Sprint-based requests: organized marketing's asks into sprints, with placeholder tickets for documents we could already predict from historical volume, and room left for the unplanned ones
  • Capacity planning: had him calculate his team's average sprint capacity, giving marketing a real reference point for what they could reasonably request, one document per ticket
  • Partnership framing: made sure marketing felt we were on their side, since our goal was the same as theirs, getting high-quality documents out the door

I met with the marketing director to present the plan and get her help selling it to her team. Once both sides agreed, my PM set up regular backlog cleanup meetings and a weekly sync to catch anything urgent. Within three months, both teams had settled into a steady rhythm, and translation quality improved noticeably now that translators and proofreaders had the days they needed instead of being rushed.

The durable advantage was never the model. It was the data pipeline and the quality gates that made global launches repeatable.

More work