HealthSherpa is a consumer-focused ACA quoting and enrollment platform that simplifies health coverage enrollment through an online quoting and enrollment product and customer support. The platform serves U.S. health-insurance markets and supports an expanding set of web projects used to drive customer enrollment and ongoing engagement.

As HealthSherpa grew, localization became an operational bottleneck for three reasons:

High traffic and platform limits — the enrollment product is high-volume; HealthSherpa needed to avoid service disruption from pageview caps imposed by localization tooling.

Multiple projects and languages — a growing footprint of web projects required a consistent approach to translation governance and state management.

Predictable capacity planning — the team needed a way to expand localization capacity incrementally as usage rose without creating governance headaches or costly refactors.

These pressures made centralized translation workflows and elastic capacity priorities for the product and engineering teams.

‍

HealthSherpa adopted Localize to centralize translations and synchronize language projects directly from the live web application. Key elements of the solution:

Centralized translation state — Localize kept pending phrases and translation state in one dashboard so product and engineering teams could manage translation work across projects.

Incremental pageview add-ons — rather than a single large commitment, HealthSherpa used staged pageview add-ons to expand capacity as traffic grew, reducing the risk of hard limits interrupting enrollment flows.

Project-level management — the team mapped multiple web initiatives to separate Localize projects so governance, QA and release control could be scoped by product area while preserving a unified process.

This approach allowed HealthSherpa to scale translation capacity in lockstep with traffic and minimize operational friction.

‍

During evaluation and POC, Localize and OneStudyTeam worked through several implementation details important for clinical apps:

‍

• PII exclusion patterns: Developers used CSS classes/IDs on patient name fields and other inputs so those elements are never pulled into the translation pipeline. For complex widgets (for example AntD selects that dynamically render options), the team validated ways to attach exclusion classes to option elements and to ensure placeholders and labels remain translatable while option values are blocked.
• Staging-first workflow: Translations and QA were run in staging before push to production so product and clinical teams could review localized UI and address layout or length issues (e.g., German length, Japanese typography) using the in-context editor.
• Glossary and dynamic variables: Clinical terminology and recurring phrases were added to a shared glossary. Dynamic phrase variables reduced review overhead for repeated patterns (e.g., “slide 1 of 10”), keeping translation memory consistent.
• Operational controls: Auto-approve flags, pending → QA → published bins, and task-manager workflows let site-success teams assign human reviews only where necessary and keep translators focused on priority content.
• Security and compliance: OneStudyTeam required security review, NDA/BAA discussions, and the ability to demonstrate audit trails. Localize provided compliance documentation, SOC-type artifacts, regional edge support, and recommendations for Part 11 / GxP considerations to be reviewed as part of contracting.

‍

With Localize, HealthSherpa established a standardized translation workflow across multiple product projects and achieved the operational flexibility required to support high-traffic enrollment flows:

The account now manages translations for 2 languages across 4 projects.

HealthSherpa completed multiple pageview add-ons to support peak enrollment traffic and avoid service limits.

Centralized translation state and governance reduced the operational risk of interruptions and made incremental capacity planning straightforward for product and engineering teams.

HealthSherpa’s localization effort shows how a centralized translation platform, combined with elastic capacity, can convert a scalability risk into an operational capability. By synchronizing translation state across projects and using staged pageview add-ons, HealthSherpa preserved enrollment reliability during traffic spikes while simplifying governance and planning for continued growth.

‍