DXP total cost of ownership: what Sitecore, AEM and the alternatives really cost per year

Most DXP business cases compare licence quotes, and finance discovers the rest one invoice at a time. We build every platform budget from the same eight lines, so a DXP, a headless CMS and an agent-run headless site fit on one page.

The table shows what each line covers and what is public about it. Where a figure appears, it is labelled with its type: a published list price, vendor-reported transaction data, or a partner's estimate. Where nothing credible is published, we say so.

Sitecore does not publish a price for SitecoreAI, the product that XM Cloud has transitioned into. Its own developer FAQ on XM Cloud pricing gives no figure and no pricing metric. The public reference points come from third parties, and each has a bias worth naming.

Vendr, a software buying service, reports a median Sitecore contract of $60,944 per year, with a range of $8,687 to $396,007. This is transaction data from its own customers, not a list price, and it covers the licence. Vendr also writes that implementation can range from $100,000 to more than $1,000,000 and may exceed annual licence costs.

Fishtank, a Sitecore Platinum Partner, explains the licence model in a November 2025 article: core SitecoreAI is priced on visits, other modules such as DAM on users, and the base includes one production and two non-production environments. Because SitecoreAI is headless, the front end needs its own hosting; Fishtank gives a planning range of $8,000 to $35,000 per year for that, depending on the tier. It also estimates implementation as a low-to-mid six-figure investment. These are a partner's planning figures, not Sitecore prices.

Adobe's AEM Sites pricing page publishes no number. Its call to action is "Get customized pricing", and it describes a core package with optional add-ons such as Forms, Screens, Guides, Learning Manager and Developer App Builder.

The most detailed public description we found comes from Oshyn, an Adobe partner, in May 2026. Read it as a partner's experience, not as Adobe pricing. Oshyn writes that AEM Sites author licences are based on concurrent users and that content requests are counted monthly, with base packages of 20 concurrent users with up to 5 million content requests, or 40 concurrent users with 5 million or more. It describes annual licences that typically start in the low-to-mid six figures, implementation costs that often run two times the annual licence or more, Adobe Premier Support at 15 to 25% of the licence fee per year, and a single-site enterprise deployment taking 9 to 18 months.

One detail matters more than any range: Oshyn notes that fees begin at contract signing, not at go-live. On a 9 to 18 month build, your first licence year can be spent before the site launches.

When a vendor will not publish a price, the procurement conversation is where you get one. These are the questions we bring to every DXP renewal or selection, so the quote fills all eight lines instead of one.

• What is the pricing metric (visits, content requests, concurrent authors, environments), and what is the overage rate when we exceed it?
• Which modules are in the quote, and which features in the demo require a separate module or add-on licence?
• When does billing start, and can the first year start at go-live rather than at signature?
• What is the price cap on renewal, and is it written into the contract for every year of the term?
• Which support tier is included, and what does the next tier cost as a share of the licence?
• Is front-end hosting included, or do we contract and pay for it separately?
• What does an implementation partner typically quote for a site of our size, and can we speak to two customers with similar scope?
• What does it cost to exit: content export format, notice period, and fees during a migration overlap?

Headless CMS vendors publish more than DXP vendors, but only for their entry tiers. The enterprise tiers that bring SSO, custom roles and support are contact sales. Our comparison of agent-run headless vs Contentful, Storyblok and Sanity covers the features; here are the published prices that feed lines 1 and 4 of the worksheet.

A headless CMS removes the DXP licence but not the other seven lines. You still need someone to build the front end, host it, maintain it and train editors. Our guide on when a headless CMS pays off covers the architecture decision; the worksheet below covers the money.

The three options differ less in licence cost than in who does the work on lines 2, 3, 6 and 7. We describe each line rather than invent a total, because your traffic, number of sites and team decide the numbers.

The case for agent-run headless, and the cases where a DXP still wins, are in our pillar on enterprise headless without a DXP. In short: a large daily editorial team, vendor-run localization or regulated approval workflows can justify the platform. For most B2B marketing sites, the larger saving sits in lines 2, 3 and 6.

Run this worksheet once for each option, over the same contract term. Use quotes, invoices and payroll data, not the ranges above. Those ranges are there to tell you which lines deserve a hard question, not to fill the cells.

1. Pick the term: use the contract length on the table (often three years) and calculate every line per year and in total.
2. Licence: enter the quoted annual fee for each year, including the uplift written into the contract. If the uplift is not capped, ask procurement for the cap before you enter a figure.
3. Implementation: enter the partner quote, plus a contingency line for change requests that your finance partner agrees with. Spread it over the term or show it in year one, but use the same method for every option.
4. Retainer: enter the monthly retainer times twelve, or the number of developer hours per month times the hourly rate times twelve.
5. Hosting and add-ons: enter front-end hosting, CDN, extra environments, SSO and every module in the quote, each on its own row.
6. Staff time: list each internal role that touches the platform, estimate the share of its time spent on platform work, and multiply by its fully loaded annual cost from payroll.
7. Upgrades and overlap: add any planned version upgrade, and the months when the old and new platforms are both paid during a migration.
8. Training: multiply the number of authors and developers by training hours and loaded hourly cost, plus any certification fees.
9. Add the eight lines per year, then divide by the number of qualified opportunities or pipeline the site sourced last year, so the board sees cost against revenue, not only cost.

A platform that costs more but measurably sources more pipeline can be the right choice. One whose staff time grows while pipeline stays flat usually is not.

We start with this worksheet, filled in with your contract, invoices and team time, before anyone talks about a new tool. Often the result is a hybrid: keep a CMS for the content types editors truly need, and move templates, SEO, GEO, QA and experiments to an agent-run front end in your own repository.

Our headless website development service builds that function in your accounts, timed to your renewal date so you do not pay two platforms longer than needed. Bring your current licence and partner invoices to a free 30-minute pipeline plan and talk to our team about where your eight lines stand.