Contentful implementation cost: plans, build work and quotes now it is part of Salesforce

Contentful is the newest acquisition in this group of guides. Salesforce announced the deal in June 2026, and its newsroom confirms: "Salesforce completed its acquisition of Contentful on September 1, 2026." The Contentful site now carries a banner saying it is officially part of Salesforce, but the product is still sold from contentful.com, on Contentful's own plans. That is what this guide prices.

The headline numbers are easy to find. The harder question is what an implementation costs, because Contentful is a headless content platform. It stores and delivers structured content through APIs. It does not render a website by itself. Every Contentful project therefore has two halves: the content platform, which you license, and the experience that displays the content, which you build and host.

#What you pay Contentful

As at October 2026, the Contentful pricing page lists three Platform plans, priced in US dollars. Its own summary of the entry plan reads: "The Free plan costs $0 forever and includes 10 users, two roles, two locales, 100,000 API calls per month, 50 GB of monthly CDN bandwidth, and one Starter Space."

The Starter Space included on every plan has tight quotas: 25 content types, 2 environments and 10,000 records. That is plenty for learning and too little for most production sites, which is why the Space you buy matters as much as the plan. Contentful also sells premium Spaces, named Standard, Enterprise and Templated, each with its own quotas and intended use.

For a Salesforce customer, Enterprise is usually where the conversation ends up. The personalisation product, Studio and AI Actions are all added to an Enterprise plan, and the enhanced governance, compliance and security features sit there too. The personalisation product also lists Salesforce CRM as a premium data connection, which is the most direct link between the two platforms on the price list today. AI Actions comes with an allowance of credits on Enterprise plans, with pay-as-you-go or pre-paid options for usage beyond it.

#Why the content model is the real cost driver

On a traditional CMS, the page is the unit of work. On Contentful, the content type is. A content type is a structured definition, such as Product, Article, Promotion or Store, with fields and references to other types. The front end assembles pages from those pieces.

Every content type you add has a cost in four places. It must be designed and agreed with the people who write content. It must be migrated, if content already exists somewhere else. It must be rendered, which means a component in the front end. And editors must be trained to use it. Locales multiply the migration and testing effort, and references between types make migration scripts more complex, because parents and children must load in the right order.

This is the single best question to ask any partner: how many content types does your design assume, and why? A model with 40 types where 15 would do will cost more to build, more to migrate and more to maintain, and it will push you into a larger Space sooner. A model with too few types forces editors to paste formatted blobs into rich text fields, which defeats the point of structured content and makes personalisation harder later.

#Contentful or the CMS you already have in Salesforce

Before pricing a Contentful build, check whether you need one. Salesforce already includes content management in several clouds. Experience Cloud sites have their own CMS workspaces, B2C Commerce has Page Designer for storefront pages, and Marketing Cloud Engagement has Content Builder for email. If your content lives in one channel and is managed by one team, the tool built into that channel is often enough, and it costs nothing extra to license.

Contentful earns its cost when the same content has to appear in several places. A product description used on the website, the mobile app, the storefront and in emails. A store opening hours entry that must be right on every channel at once. A brand with six regional sites that share most of their content but not all of it. In those cases a headless platform removes the copy and paste between systems, and that saving is the business case. If you cannot name at least two channels that will reuse the same content, the implementation cost is hard to justify, whatever the licence price.

#A sizing example

Take a hypothetical retailer with one main website, a mobile app and Marketing Cloud Engagement emails, operating in English and one other language. Its old CMS holds around 2,000 pages, most of them product stories and store pages.

Discovery shows that roughly a third of those pages are out of date and can be retired. The remaining content fits about fifteen content types: product story, store, promotion, article, author, FAQ, landing page, hero banner and a few supporting types. Two locales double the migration testing but not the build. The website and the app both read from the same Space through the GraphQL API, and emails pull promotion entries through a small custom integration.

The cost of that project sits mostly in four places: the content model workshops, the migration scripts for rich text and images, the front-end templates for the website, and the email integration. The licence is a line on the budget, but it is not where the risk is. If the same retailer had insisted on keeping every legacy page and modelling each page layout as its own type, the content model could easily have doubled, and every downstream package with it.

#What a Contentful implementation is made of

The Salesforce connection is the package most worth scoping carefully, because there are several distinct jobs that can hide under the same heading. Showing Salesforce data on a Contentful-powered site, such as a logged-in customer's products or cases, is a front-end and API integration job. Using Contentful content inside Salesforce channels, such as an Experience Cloud site, a B2C Commerce storefront or Marketing Cloud Engagement emails, is a content reuse job, usually through the Content Delivery API or a custom app built on Contentful's App Framework. Using Salesforce CRM data to decide which content a visitor sees is a job for the personalisation product, and it depends on that premium data connection and on the tier you buy. Name which of these you want before you ask for quotes, because each is priced differently.

#What the Salesforce acquisition changes, and what it does not

Salesforce's announcement describes Contentful as the content layer for its Headless 360 approach, says Agentforce agents will be able to query, assemble and deliver content without manual publishing steps, and positions Contentful alongside Data 360 for personalised experiences across email, web and mobile. That direction is real, and it may change what you buy over the next few years.

It does not change what you can sign today. As at October 2026 the plans above are sold by Contentful, and Salesforce has not published a Salesforce-branded Contentful price. If an account executive offers a bundle, ask for the Contentful lines to be shown separately, with the Space types, personalisation tier and AI Actions allowance named. If a partner's proposal depends on an integration Salesforce has announced but not yet released, ask for that part to be quoted as a later phase, so your go-live does not wait on someone else's roadmap.

Existing Contentful customers face a slightly different question at renewal. Your current contract runs to its term, and nothing in the announcement forces a change before then. When renewal comes, ask whether it will be written by Contentful or by your Salesforce account team, whether it can be co-termed with your Salesforce agreement, and whether any new bundle changes the Space types or usage quotas you rely on today. Compare the renewal line by line with your current order form. A familiar total can hide a smaller API quota or a different Space type, and those are the limits your front end actually runs into.

#Getting quotes you can compare

Contentful quotes vary more than most because the front end is open-ended. Two partners can quote very different numbers for the same content platform simply because one assumes 12 page templates and the other assumes 30. Give every partner the same inputs: the list of sites and channels, the number of locales, a rough content inventory, the Salesforce jobs you want, and a short list of the page types you know you need.

Then ask each one for the content type count, the template and component count, the migration approach for rich text and assets, the hosting they assume for the front end, and the redirect plan. Ask who builds the front end: some partners build the content model and expect your web team to build the site, and that difference alone can halve a quote without halving the work. Ask how they test performance and how they handle preview, because editors expect to see a page before it goes live, and preview needs its own API and front-end path.

#Costs that sit outside the first quote

1. Front-end hosting. The site or app runs on hosting you pay for separately, such as a cloud platform or a front-end host. Budget for its bandwidth, builds and monitoring.
2. API and bandwidth headroom. The Free plan caps usage with no overages. Paid plans set quotas, and Enterprise terms set what happens when you exceed them. Check the numbers against your traffic, including bots.
3. Extra Spaces and environments. A second brand, a second region or a separate staging Space can each mean another paid Space.
4. Locales. Each locale adds translation cost, either human or through AI Actions credits, and adds testing.
5. Personalisation profiles. Personalisation tiers are sized by monthly active profiles. Traffic growth can move you to the next tier.
6. Content freeze. During migration, editors usually stop publishing on the old system for a period. Plan around campaigns.
7. Old platform overlap. The old CMS licence and hosting continue until cutover and redirects are proven.
8. Editor adoption. Structured content is a new way of working for people used to page editors. Training and a few weeks of support after launch are cheaper than a rebuild.
9. Content model changes after launch. Adding a field is easy. Changing a content type that thousands of entries already use needs a migration script, testing in a separate environment and a release plan. Keep a small budget for the first year, because the first real campaign always reveals a field nobody thought to model.

#Where to go next

For the product picture now that Contentful sits with Salesforce, read Contentful and Salesforce and what happened to Contentful. The licence detail is covered in Contentful licence cost. The connection options are set out in integrating Contentful with Salesforce, and if you already run Contentful and are wondering whether to move off it, should I migrate from Contentful weighs it up. When you are ready to compare partners, hiring a Contentful Salesforce partner lists the questions worth asking.

The practical summary: the published plan price is the small number. Count your content types, name your Salesforce jobs, and price the front end as its own project.