4 markets launched on one commerce platform for a US automotive retailer.

The retailer sold vehicles online across the US and wanted to expand region by region — but every new market was a bespoke infrastructure project. The first had taken three quarters: a hand-built copy of the stack, its own configuration drift, its own operational quirks. Two markets in, the engineering organisation was spending more time keeping the copies aligned than building product.

Leadership had committed to four new market launches in the next year. On the existing trajectory that was not an engineering plan; it was a hiring plan. The brief was to make market launch a repeatable operation rather than a project.

We rebuilt the estate as a multi-account AWS organisation: a platform account set for shared services — networking, identity, observability, CI/CD — and a templated account-per-market pattern defined entirely in Terraform. A market became data, not infrastructure: one configuration file declaring its region, locale, tax rules, and inventory sources.

Every market deployed from the same pipeline. No market-specific branches, no snowflake environments — a change shipped to all markets or none, behind feature flags where rollout had to be staged. The drift that had consumed the team became structurally impossible rather than procedurally discouraged.

Existing markets migrated onto the platform first — the least glamorous and most important decision of the engagement. Launching new markets on a platform while old ones stayed bespoke would have doubled the operational surface. Both legacy markets were re-platformed with zero customer-facing downtime before the first new launch.

Estate     ·  AWS Organizations, account-per-market, platform accounts
IaC        ·  Terraform modules; market = one config file
Delivery   ·  Single pipeline, all markets; feature-flagged rollout
Runtime    ·  ECS + RDS per market account; shared observability
Migration  ·  Legacy markets re-platformed first, zero downtime

All four committed markets launched on schedule — the fourth took three weeks from decision to live traffic, against ten weeks for the first launch on the new platform and three quarters under the old approach. Infrastructure cost per market dropped 31% as shared services replaced duplicated stacks. The platform team now launches markets without engineering involvement from the product organisation at all.