Who to hire for Contentful on Salesforce

Contentful projects go wrong in an unusual way. The software works, the connection to Salesforce works, and six months later the marketing team cannot publish a campaign page without a developer. The cause is rarely a bug. It is a content model built to suit the first launch and then stretched until it snaps. That is why hiring for this product starts with a different question from most Salesforce projects: who can design structured content that real editors will live with?

Some background helps you read proposals. Salesforce completed its acquisition of Contentful on September 1, 2026. At announcement, Salesforce described the intent this way: "Contentful will be integrated natively across Customer 360 while preserving the composability that developers and digital teams expect from a modern headless platform." The same announcement describes a future in which "Contentful’s structured content architecture becomes accessible to Agentforce, enabling agents to query, assemble, and deliver content dynamically without manual publishing steps." Both sentences are statements of direction. They tell you the platform is not being folded into a CRM screen, which is why the people you hire need front-end and content skills, not only Salesforce ones. The full text is in Salesforce's announcement.

#Two kinds of expert, and you may need both

Think of two profiles. The content architect designs the model: what a product story, a landing page, a help article and a promotion are made of, how they reference one another, how translations work, and what an editor sees. The integration engineer connects that content to everything else: publish events, preview, search, Salesforce records, personalisation and analytics.

Many firms are strong in one and describe themselves as strong in both. Test each skill separately. Ask the architect to walk through a model they built and then to explain what they would change now. Ask the integration engineer to describe how a published entry reaches a downstream system, how failures are retried, and how a webhook is secured. If one person is covering both profiles on a small project, that is fine, but you should be able to point at evidence for each half.

#The order of work matters more than the tooling

A reliable sequence has five steps. First comes an audit of existing content and editorial workflow, because a model that ignores how people already work will be bypassed. Second is the content model itself, including reusable components, references, locales and validation. Third is environments and governance: who may change the model, how changes are promoted from test to production, and how roles map to your organisation. Fourth is delivery, meaning the front end or channels that consume the content. Only fifth does the Salesforce integration appear in earnest.

Be wary of a proposal that starts with the Salesforce connection. It usually means the firm is expert in the connection and improvising the model. The reverse failure also happens, where a content agency delivers a beautiful model and then hands the integration to a junior contractor. A good proposal names the same lead across all five steps.

#Skills and certifications worth asking for

On the Salesforce side, ask for Salesforce Certified Platform Integration Architect where content will drive or react to CRM data, Salesforce Certified Marketing Cloud Next Consultant where personalisation and campaigns depend on it, and Salesforce Certified Agentforce Specialist if agents will consume content. Each is listed on Trailhead's credentials pages.

On the Contentful side, ask about hands-on delivery rather than badges. You want people who have modelled content types, managed multiple environments, used the delivery and management APIs, configured webhooks, and built or extended apps for the editing interface. Ask to see a model diagram and an anonymised migration plan. Check also for front-end competence in whichever framework your sites use, because content that cannot be rendered well is of little value.

#A first engagement built around one content type

Choose a content type that matters to the business and has an obvious Salesforce link. A product or service story, an event, or a help article often works. The aim is to take it from model to production behaviour, with a real editor, within six to eight weeks.

The outputs should be a documented model for that type, including validation rules and the reasons behind them; a preview and publishing workflow tested by actual editors; a defined environment and promotion process; and one integration with Salesforce, such as a published entry creating or updating a record or triggering a campaign step. The Contentful marketplace shows how apps can extend the editing interface; its SFMC Studio listing is one example of a Salesforce-related app, and a partner should be able to say when an existing app is enough and when a custom one is warranted.

Finish with a short measure of editor effort. How long does it take a marketer to create and publish one of these entries, and how many steps need a developer? If the answer is not better than the current process, the model needs more work before you scale.

Use the same pilot to test change. Ask the partner to alter the model after launch, by adding a field and a validation rule, and to promote that change from a test environment to production while an editor is mid-task. How smoothly that goes tells you whether the governance they designed is real. It also shows whether the preview experience gives editors confidence, which is the thing most likely to decide whether the platform is loved or quietly avoided in your organisation.

#What breaks when it is treated like a generic CRM project

CRM projects are driven by processes and objects. Content projects are driven by editors and reuse. Treating Contentful as just another system to integrate produces four recurring problems.

The first is a model that mirrors the page. If every landing page is one giant entry, nothing is reusable, and personalisation or agent-driven assembly becomes impossible. The second is duplicated truth: product names, prices or legal text copied into Contentful and Salesforce with no rule about which wins. The third is a missing governance layer, so anyone can change the model and quietly break the site. The fourth is neglecting localisation until late, when retrofitting languages into a model that did not plan for them is painful.

A partner who has met these before will raise them unprompted. If the first workshop concentrates on field mappings and API calls, steer it back to the editors.

#If you are moving from another CMS

Many Contentful engagements begin as a migration from a monolithic CMS, and migration has its own skill set. The partner should inventory what exists, decide what will not be carried across, and write mapping rules from old fields to the new model. They should also plan for the dull but costly details: redirects for retired URLs, media files and their metadata, authorship and publication dates, and how translated versions are linked.

Ask how they will run old and new side by side, who freezes content during cutover, and how editors will be trained before the switch rather than after. A common trap is to migrate everything because it is possible. A sharper partner will push you to retire a large share of old pages, because every migrated entry has to be modelled, checked and maintained. Ask them to estimate the volume of content that will be moved by hand, since that is where timelines slip.

#Preparing content for agents

The announcement's point about agents is worth taking seriously, but it should not become a reason to hire for hype. Agents can only assemble content well if it is structured, labelled and free of contradictory copies. That is an argument for the same disciplined modelling you would want anyway.

When a candidate talks about agent-ready content, ask three practical things. Which fields would an agent need that a human editor would not? How would you stop an agent from using an out-of-date or unapproved entry? Who reviews what an agent assembles, and how is that review recorded? A partner with real experience will talk about approval states, metadata and audit trails. One who only has a demo will talk about what is possible. You do not need to answer these questions in phase one, but the model you choose should not prevent you answering them later.

#Ten questions for the shortlist

1. Show us a content model you designed and tell us what you would change.
2. How do you decide between a reusable component and a one-off field?
3. How do you handle localisation, and when in the project?
4. Who is allowed to change the model, and how are changes promoted between environments?
5. Which system owns each shared fact, such as product name or price, and how is that enforced?
6. How does a published entry reach Salesforce, and what happens when delivery fails?
7. How do you secure and monitor webhooks?
8. How would you prepare our content for use by agents, and what could go wrong?
9. What does editor training involve, and how do you measure its success?
10. What is your plan if we decide to change the front end in two years?

The best answers are specific and mention costs. Be cautious of anyone who says that headless means anything is possible. It means you must decide everything yourself, and that is exactly the work you are paying for.

#References and evidence without logos

Ask for a reference who is an editor, not just a sponsor. Editors know whether the model works on a Tuesday afternoon with a deadline. Ask what they can do without a developer, how long a new campaign page takes, and what the partner would have done differently.

Ask for artefacts: a model diagram, a migration mapping, a governance document and a record of an environment promotion. Check whether the partner's own website is built to the standard they will ask of you, since a content agency whose site is slow or inconsistent has told you something.

#Commercial models and the statement of work

A paid discovery that produces the content audit and draft model is an excellent first purchase. After that, a fixed price per defined content type or channel works well, because each is a recognisable unit. Time and materials suits the open-ended editor feedback phase, ideally with a cap.

State who supplies licences, environments and design assets, since delays there are a common source of overruns. Pricing context sits on the licence page and in Contentful Salesforce implementation cost.

#When you can skip a partner

If you have one site, a small set of content types, an in-house developer who has used the platform, and no need for a Salesforce integration beyond a simple link, you probably do not need a partner. The same applies if the Contentful space already exists and your team is simply adding a field.

Bring a partner in when you are building the model from scratch, when many teams will publish, when multiple locales are planned, or when content must drive Salesforce data and campaigns. For related decisions read integrating Contentful with Salesforce, should I migrate from Contentful and what happened to Contentful.