Most buyers walk into an AEM sourcing exercise with a fixed idea: London is the cheap bench, New York is the expensive one, and the arbitrage is the whole strategy. That stopped being true somewhere in the last twelve months. A London AEM contractor now sits in the same cost band as a New York developer once you convert and add employer on-costs — which means the money on your next Experience Manager engagement is won or lost on how you shape the work, not on which time zone you buy it in.
The price gap buyers assume no longer exists
The median contract day rate for London roles citing Adobe Experience Manager is £548 in the six months to 18 October 2026, up from £400 in the same period a year earlier. That is a 37% move in a single year on a skill that was already scarce. Convert at whatever rate your treasury is using and add the on-costs a UK engagement carries — agency margin, IR35 determination overhead, VAT handling — and the delta against a New York equivalent narrows to rounding error for most mid-sized programmes.
The practical consequence: a global brand that splits AEM delivery across London and New York to chase rate is now paying a coordination tax for no saving. Two squads in two time zones on the same component library means two sets of code review conventions, two interpretations of the authoring model, and a handoff window of about four hours a day. That cost is real and it is not in anyone’s rate card.
The arbitrage you budgeted for in 2024 was spent by the market in 2026.
What London actually bills in 2026
The London distribution matters more than the median, because almost nobody buys AEM at the median. You buy either a mid-level component developer or a replatform lead, and those sit at opposite ends.
The top decile of London AEM contracts bills £692 a day. That is the realistic ceiling for a senior replatform lead bought direct — someone who has taken a Sites instance from 6.5 to Cloud Service, owns the dispatcher config, and can argue dependency injection choices with your architecture review board without rehearsal. If an agency quotes you materially above that for a single named lead, you are paying for the logo and the bench behind them, not for the person.
Context from the national market is useful here. Across the UK the median AEM contract day rate is £500, and outside London it drops to £473 — so London carries roughly a 16% location premium inside its own market. If your authoring model is stable and the work is remote-first anyway, Manchester, Leeds and Bristol are a genuine 16% lever that most buyers never pull because the agency panel they inherited is all London-registered.
Why London moved and New York did not
The rate shift has a cause you can point at. London AEM contract demand tripled year on year: 61 contract vacancies citing AEM against 20 in the same period of 2025. Three times the demand against a contractor pool that did not triple produces exactly the £400-to-£548 move you see.
New York had no equivalent shock. The baseline there has been drifting with the broader developer market rather than spiking on an Adobe-specific squeeze. That is why the two cities converged — not because New York got cheaper, but because London caught up fast.
There is a second-order effect worth naming. When demand triples in a market that small, the people who move first are the ones who are easiest to move: contractors between engagements, and juniors re-badged as mid-level by agencies filling seats. The genuinely senior AEM people — the ones who have shipped a Cloud Service migration end to end — mostly did not move, because they were already booked. So a rising median in London does not mean a deeper pool. It means a hotter one.
Measuring New York honestly
New York does not publish an AEM-specific contract rate, so you have to triangulate from the salaried baseline and work upward. Software developers in the New York-Newark-Jersey City metro average $73.12 an hour, or $152,100 a year. That is the floor a contract or agency rate gets measured against — a general developer wage, before any Adobe specialisation premium, before benefits, and before the 25–35% loading a staffing firm adds.
The metro premium is the other half of the picture. New York metro computer and mathematical roles average $67.04 an hour against a US average of $57.73 — about 16%, the same order of magnitude as London’s premium over the rest of the UK. Two different labour markets, two different currencies, the same structural shape: a national base plus a sixth for the financial capital.
| Benchmark | London | New York |
|---|---|---|
| AEM contract median | £548/day | not separately published |
| AEM contract 90th percentile | £692/day | not separately published |
| Developer salaried baseline | — | $73.12/hr, $152,100/yr |
| Metro premium over national | ~16% (vs £473 outside London) | ~16% ($67.04 vs $57.73/hr) |
| Year-on-year direction | median up from £400 | broadly flat |
| Demand signal | 61 contract vacancies vs 20 | no comparable spike |
Read that table the way a procurement lead should: the only AEM-specific published numbers in it are London’s, and they have already closed the gap. Anyone quoting you a New York premium of 40% or more on AEM specifically is quoting a 2023 market.
Engagement shape decides the bill, not the city
Once the rate bands converge, the variable that actually swings your total is how the work is packaged. Two shapes cover most AEM spend, and they are not interchangeable.
Fixed-scope agency squad for a replatform
A migration to AEM as a Cloud Service, a full IA rebuild, or a multi-brand component library consolidation has an architecture risk that one contractor cannot absorb. You want a squad with a named architect, a defined cutover plan, and liability that survives the project. The per-day number will be higher than a direct contractor, and it should be — you are buying coverage for the week your lead developer gets appendicitis, plus an escalation path into Adobe support that you do not maintain yourself.
Where agency squads go wrong is duration. They are priced for a bounded replatform and they stay on for eighteen months of BAU component tickets at replatform rates. That is where the budget leaks, and it leaks quietly because the invoices look the same every month.
Direct contractors for ongoing component work
New templates, new components, dialog tweaks, Core Components upgrades, dispatcher rule changes, content fragment model extensions — this is steady-state work with low architecture risk and high domain-knowledge value. It rewards continuity in the same person, not bench depth. Buying it direct at the London median, or even at the £692 top decile for one strong lead, costs materially less than the same hours through a squad and leaves the institutional knowledge inside your organisation.
| Replatform / migration | Ongoing component work | |
|---|---|---|
| Best shape | Fixed-scope agency squad | Direct contractor or two |
| Duration | 3–9 months, bounded | Rolling, renewed quarterly |
| Rate reference | Above the 90th percentile is defensible | £548 median to £692 top decile |
| What you’re buying | Architecture risk transfer, cutover accountability | Continuity and domain knowledge |
| Failure mode | Squad stays past cutover at project rates | One person becomes a single point of failure |
| Where to run it | Either city — pick on time zone overlap | Cheapest credible market, remote-first |
The hybrid that works: agency squad through cutover with a contractually defined exit, one or two direct contractors embedded from month two so knowledge transfer happens during the engagement rather than in a handover document nobody reads. We’ve broken the trade-offs down further in AEM agency vs contractor vs in-house.
How to budget either market this year
Start from the published distribution, not from a vendor quote. If London’s median is £548 and the top decile is £692, then a three-person squad quoted at an effective blended rate above the top decile needs to justify what the premium buys — and “senior resources” is not an answer, it is a billing category.
Four things to hold firm on:
Price the location lever separately. The 16% London premium over the rest of the UK is the single cleanest saving available on remote-first AEM work, and it requires no change to scope or quality bar.
Measure New York against the salaried baseline. At $152,100 a year for a metro software developer, you can model what an equivalent full-time hire costs loaded and decide whether twelve months of contract is actually the cheaper path. Often it is not — and for genuinely ongoing component work, it rarely is.
Treat the demand signal as a lead-time input, not just a price input. Tripled vacancy volume in London means your shortlist is competing with sixty other open briefs. Budget four to six weeks of search, or accept whoever is immediately available and pay for it later in rework.
Vet to the same bar in both cities. Rate convergence means a New York candidate and a London candidate are now genuinely comparable on cost, so the decision comes down to assessment. If your AEM screen cannot distinguish someone who has run a Cloud Service migration from someone who has read about one, geography is the least of your problems. The adjacent platform-side rates — Experience Platform, Journey Optimizer, RT-CDP — move on a different curve, and we’ve covered those separately in Adobe Experience Platform consultant rates for 2026.
The practical read for 2026: stop shopping cities and start shopping shapes. A fixed-scope squad for the replatform, direct contractors for everything after it, and a published rate distribution in your hand when the quote arrives. That combination saves more than any transatlantic arbitrage ever did. If you want to see which Adobe specialists are currently working on comparable stacks, the network is searchable without an account.