Contentful licence cost after the Salesforce acquisition

Salesforce's announcement is as brief as these things usually are: "Salesforce completed its acquisition of Contentful on September 1, 2026." Contentful's own pricing page now carries a banner saying it is officially part of Salesforce. Neither of those facts changes what you buy. Contentful is a content platform sold on its own plans, with its own units, and a Salesforce user licence does not include it. This page is about that licence. The project work to model content and connect it to Salesforce is a separate cost, covered on the Contentful implementation cost page.

#The published plan ladder

Contentful publishes more than most Salesforce acquisitions do, at least for the entry plans. This is what the pricing page listed when we read it on 13 October 2026.

Two things are worth reading closely. The first is the phrase "no overages" against the Free plan's API calls and bandwidth. It tells you there is no way to buy more on that plan, so the ceiling is a hard one. The page does not say what happens when you hit it, and that is something to test in a pilot rather than assume. The second is that Lite is described as being for smaller businesses managing a single project. The page does not say whether the monthly figure assumes annual billing, so ask at checkout.

Enterprise is where the list prices stop. The page lists a custom number of users, roles and locales, unlimited API calls, up to a 99.99 uptime service level, enhanced governance and security features, and compatibility with personalisation, Studio and AI Actions. It is a plan you negotiate, and the number of spaces, the size of each, and the add-ons you attach will all move it.

#Spaces are the unit that catches buyers out

Most platforms are priced per user. Contentful's natural unit is the space, and the page puts it simply: "Spaces are an area for each project." A space holds the content types, entries, assets and environments for one site or product, and the quotas that matter, such as records, environments and content types, attach to the space rather than to the organisation.

Every platform plan includes one Starter Space. On the page it is a free space that cannot be purchased separately, capped at 10,000 records, with workflows and additional API or bandwidth usage not available. Anything beyond that is a Premium Space, and the page describes three kinds.

This matters for budgeting because a design decision turns into a licence decision. One space per brand is clean for governance and multiplies the number of spaces you pay for. One shared space for many brands is cheaper on paper and harder to manage, and may hit record and content type limits sooner. Decide the space model before you ask for a quote, since the quote will otherwise be built on the vendor's assumption.

Environments are the other quota to understand. Contentful offers sandbox environments inside a space for development and testing, and an environment alias lets you promote one to production. That is separate from a Salesforce sandbox, and a Salesforce sandbox refresh does not copy a Contentful space. If your delivery process needs several environments, check how many each space allows and whether extra ones cost more.

#What sits on top of the platform plan

The platform plan is not the whole licence once you want personalised or AI-assisted content. Three products are layered on, and all of them are mostly quote-driven.

Personalisation is available on Enterprise Platform plans in three tiers. Start lists 100,000 monthly active profiles and 100 AI Suggestions, with one space enabled. Core lists 500,000 monthly active profiles, 500 AI Suggestions and up to five spaces. Scale lists 1 million monthly active profiles, 1,000 AI Suggestions and unlimited custom spaces, plus shared audiences across spaces. All three say contact sales, and each has upgrades available to purchase. The Core and Scale tiers also include premium data connections, and the connection list includes Salesforce CRM, which matters if you intend to feed audiences from Salesforce.

AI Actions is licensed with a quota and then metered. The page says "AI Actions is available on any Enterprise plan." and describes included AI credits, with two ways to go beyond the quota: pay as you go, or pre-pay and save at a discount agreed with the team. If your editors will translate, rewrite and tag at volume, the usage line may end up bigger than the plan fee, so ask for a usage report to be part of the contract.

Studio, the visual canvas for assembling experiences, is listed as a custom plan with a custom price a year, and includes professional services. Treat it as a separate commercial negotiation.

#How Salesforce ownership changes the picture, and what it does not

The honest position is that the public information does not yet show a Salesforce-specific way of buying Contentful. The pricing page still routes Enterprise, personalisation, AI Actions and Studio to Contentful sales. That may change, and the questions to ask are straightforward. Will your next renewal be on Contentful paper or Salesforce paper? Can Contentful spend be combined with a wider Salesforce agreement, and if so on what terms? Do any Salesforce credits apply? Do not assume that ownership brings a discount. Ask, and get any answer in writing.

#Contract and renewal mechanics

A word on timing first. The cleanest moment to negotiate is before you are dependent. Once a site is built against a space model and a set of locales, moving to a different structure is a project, and the vendor knows it. Settle the structure, get the quote, and only then commit the build. If you are already live, use the renewal date as your bargaining position and start the conversation two quarters ahead.

For the entry plans, the contract is the website's terms and a card on file, so the risks are about limits rather than negotiation. For Enterprise, the order form is the document that matters, and it should answer a short list of questions.

First, which spaces are included, of what type, and with what record, environment and content type quotas. Second, what the API call and bandwidth allowance is, how it is measured, and what happens above it. An unlimited API allowance sounds generous, and you should still read the fair-use or rate-limit terms, because a launch campaign can produce the busiest hour of your year. Third, how locales are counted. Each new market tends to add a locale, so an expansion plan is a licence plan. Fourth, how users and roles are counted, and whether developers, editors and integration accounts all take a seat. Fifth, the term, the renewal uplift and the notice period, none of which the pricing page publishes.

#How to size the licence

Measure before you ask. Count the content types and entries you expect in two years. Read your monthly API calls from your current CMS or your CDN logs, and add a peak factor for campaigns. Count locales by market launch date, not by wish. Count editors separately from developers and agencies. Work out how many environments your delivery process needs, and decide whether you are one brand or many.

Then place yourself on the ladder. If you are one project with a few editors, two locales and under a million API calls a month, Lite may be enough, and its USD 300 monthly figure is something you can put in a budget today. If you have multiple brands, more than three locales, strict governance, a service level requirement or heavy personalisation, you are in Enterprise territory, and the figure is whatever you negotiate. The jump is from a published price to an open one, so it is sensible to get the Enterprise quote while you still have the Lite option as a fallback.

#Three buyers on the same ladder

A single-brand business with one marketing site, two editors and a developer is the natural Lite customer. Its licence question is mostly about headroom: is one million API calls a month enough once the site is cached and a campaign lands, and are three locales enough for the markets on the roadmap? If both answers are yes, the list price is the licence and there is little to negotiate.

A multi-brand group with a site per brand faces the space question. It can buy a space per brand, or run one shared space with strong tagging and permissions. The first buys isolation and costs more spaces, and the second saves licence and asks more of governance. This buyer will almost certainly be on Enterprise, so the quote should show how many spaces, of which type, and what each additional one costs.

A retailer or financial brand that wants personalised experiences and an AI drafting workflow is buying three things at once: the platform, the personalisation add-on sized by monthly active profiles, and an AI quota. Each has its own unit, so the total is a sum of three negotiations. Ask for each to be priced separately and then together, so you can see whether bundling saves anything.

#Traps worth naming

The Free plan is for learning, and a production site that quietly depends on it has a hard ceiling it cannot buy its way past. The next trap is the locale count. Adding a language is a content decision made by marketing, and it can push you past a plan limit without anyone in procurement noticing. A third is the agency or integration user: if every service account takes a seat, a modest editorial team can exceed a user limit. The last is the AI quota. It feels free until a bulk translation job consumes the year's allowance in a week, so ask for a usage report and an alert before that happens.

#How to compare two offers

Put Contentful beside the alternatives on total cost, not on plan price. Include the licence, any additional spaces, usage charges for API calls, bandwidth and AI, the developer time to build and maintain the front end, and the cost of the Salesforce integration. A headless platform moves effort from licence to build, so a cheap plan can sit inside an expensive project. Ask every vendor to price the same scenario, with the same number of brands, locales, editors and monthly calls, and compare the totals.

#Where the other questions sit

The services fee and the content model belong on the Contentful page. Who bought the company belongs on what happened to Contentful. What an experience may read from Salesforce, and the failure when it cannot, belong on integrating Contentful with Salesforce. Whether to move the content belongs on should I migrate from Contentful.