Adobe contract pricing is one of the few corners of the enterprise market where you can check the number before you agree to it. Analytics and Experience Platform work has enough posted contract volume in the UK to produce a real median, and US occupational wage data gives you a defensible metro differential for the same skill base. Put those two things next to a Solution Partner retainer quote and the gap stops looking like a premium for expertise and starts looking like a premium for packaging. Here is the 2026 band, by specialism and region, and the short list of things a retainer genuinely buys you that a contractor cannot.
The UK contract band is verifiable, and it is narrower than you think
Adobe Analytics contract roles in London carry a median day rate of £460. The UK-wide figure is £446 across 37 quoted rates in the six months to 2 October 2026 — a thin sample, which is what you would expect from a specialism this narrow, but a consistent one. Strip London out and the median falls to £375, roughly a fifth lower.
That fifth is the entire geographic spread of the UK market for this skill. Not a multiple. A fifth. For remote-delivered AEP implementation work — schema design, identity stitching, destination configuration, CJA workspace build — you are paying a London postcode, not a different calibre of engineer.
| Specialism / region | Median contract day rate |
|---|---|
| Adobe Analytics — London | £460 |
| Adobe Analytics — UK-wide | £446 |
| Adobe Analytics — UK excluding London | £375 |
| Adobe Experience Manager — UK median | £500 |
| Adobe Experience Manager — UK top decile | £710 |
AEM is a different price class and should be scoped separately
The single biggest pricing mistake in Adobe contracting is treating “Adobe consultant” as one line item. Experience Manager work sits at a £500 UK median against Analytics at £446, and the AEM top decile runs to £710. That is a £54 median gap and a long right tail, because AEM-heavy builds pull in Java, Sling, OSGi, dispatcher tuning and front-end component work — a genuinely different engineer from the one who models XDM schemas and debugs Web SDK calls.
If your statement of work bundles a headless AEM migration with AEP activation and a CJA reporting rebuild, you will be quoted the blended top of the range for all of it. Split the scope by specialism and you pay the AEM premium only on the AEM hours. We have written separately on how AEM delivery compares across agency, contractor and in-house routes — the shape of that decision is almost entirely a function of how much of the work is genuinely AEM.
What drives a rate above the median
- Multi-sandbox AEP with real-time CDP activation and consent enforcement across regions
- Analytics-to-CJA migration where historical data continuity is contractual, not nice-to-have
- AEM as a Cloud Service migration with dispatcher and CDN rework
- Adobe Target or Journey Optimizer alongside the core build, not after it
Everything else — tag deployment, report suite hygiene, dashboard build, standard destination wiring — prices at or below the median, and you should refuse to pay specialist rates for it.
US metro differentials are real but modest for this skill base
Adobe practices in the US quote as if a New York engagement is a different economy. The wage data says it is a surcharge, not a different market. Mean hourly pay for computer and mathematical occupations in the New York–Newark–Jersey City metro is $67.04. In Dallas–Fort Worth–Arlington, the same occupational group averages $57.55 — almost exactly the national figure, and about 14% below New York.
| Metro | Mean hourly, computer & mathematical | Read-across |
|---|---|---|
| New York–Newark–Jersey City | $67.04 | Regional ceiling for this skill base |
| Dallas–Fort Worth–Arlington | $57.55 | ~National average, ~14% under NY |
Analyst-grade data roles stretch wider: New York carries a 36.5% premium over national figures in 2026, the largest metro differential in that set. So the honest answer is that the New York premium for Adobe work lands somewhere between 14% and 36.5% depending on how analyst-weighted the role is — and nowhere near the 2x that a tri-state delivery pod gets quoted at.
If the quoted premium for a New York engagement is larger than the entire wage differential between New York and Dallas, you are buying something other than labour.
Practically: scope the Dallas, Austin or Atlanta contractor for implementation hours and reserve the New York rate for the people who have to sit in the room with marketing leadership. That split is the same logic as the London/non-London one, and it survives contact with a remote delivery model.
What a Solution Partner retainer actually covers
Adobe’s Solution Partner ecosystem is small at the top. Across the entire global programme, partners had collectively earned 400 Specializations as of December 2024. That number cuts both ways. It is the scarcity argument for a retainer — there genuinely are not many firms with validated depth across the product set. It is also the limit of the argument, because 400 Specializations spread across every product and every geography means the partner you hire may be Specialized in something adjacent to what you are building.
A retainer earns its money on four things:
| What you need | Retainer | Direct contract |
|---|---|---|
| Escalation path into Adobe engineering on a production incident | Yes | No |
| Named accountability on a fixed-date go-live | Yes | Partial — depends on contract terms |
| Licence and roadmap leverage at renewal | Yes | No |
| Pre-built accelerators and reference architectures | Often | Sometimes, via the individual |
| Day-to-day AEP/Analytics build hours | Expensive | Market rate |
| Continuity of the person who built it | Weak — staff rotate | Strong — you contracted them |
| Internal capability transfer | Variable, rarely contracted | Direct, if you scope it |
The first three rows are worth real money and you cannot replicate them with contractors. The bottom three are where retainers quietly lose you money — you pay a partner multiple on commodity build hours, and then the consultant who learned your identity graph rolls off to another account.
How to split the scope
Buy the retainer narrow and buy it for the escalation, the licensing leverage and the one architectural review that has to be signable by a Specialized partner. Contract the delivery hours directly, at the rates above, against named individuals you have technically screened yourself.
The mechanics that make this work:
- Separate the SOWs. One retainer agreement covering advisory, escalation and architecture sign-off. One or more contractor agreements covering build. Do not let the partner subcontract the build back under the retainer rate.
- Name the people. Specialization sits with the firm; the knowledge sits with the engineer. Insist on named resources with the right to interview, and on notice if they are rotated.
- Scope handover as a deliverable. Runbook, schema documentation, dataflow inventory, tag governance model. If it is not a deliverable it does not happen.
- Rate-card by specialism, not by seniority label. Pay the AEM band for AEM, the Analytics band for Analytics, and refuse blended rates that average commodity work up to the specialist number.
This is the same blended model that works for data platform delivery — GSI plus in-house plus contract — applied to the Adobe stack, where the specialist supply is thinner and the partner multiple is consequently higher.
Sanity checks before you agree a number
Rate alone tells you nothing if the person cannot do the work. Four screens that filter fast:
- XDM under pressure. Ask them to model a loyalty event with a many-to-many profile relationship and explain what breaks in identity stitching. Vague answers here mean they have configured AEP, not designed in it.
- Analytics-to-CJA migration scars. Anyone who has run one will volunteer what went wrong with historical data and calculated metric parity. Anyone who has not will describe the documentation.
- Dispatcher or Web SDK debugging. A concrete story about a caching or consent bug, with the resolution, separates build engineers from slide authors.
- What they would refuse to build. Specialists with real AEP mileage have opinions about which activations should never leave the warehouse. That is the signal you are paying £500 a day for.
A London AEP consultant at £460 and a Dallas-based one priced off a $57.55 mean hourly base can be the same engineer in capability terms. The band is knowable, the metro premium is bounded, and the retainer should be scoped to the three things it uniquely delivers. If you want to see who is actually available in that band, that is what the Adobe network is for.