Best way to choose Salesforce Marketing Cloud consultants, and the certification name that tells you which product they actually know
Marketing Cloud is several separately licensed products whose names have changed, and so have the certifications. Ask which credential a consultant holds by its current name, then look it up.
Published by AI Knows Us · Updated 22 October 2026
Pick a Salesforce Marketing Cloud consultant by naming the product first and the credential second. "Marketing Cloud" is a brand over several separately licensed products, so two consultants can both say they specialise in it and know different software. The current consultant credential for the high-volume consumer platform is the Salesforce Certified Marketing Cloud Engagement Consultant, read as the credential title at trailhead.salesforce.com on 22 October 2026. The business-to-business side has its own and separate consultant credential, and a firm staffed entirely on one of the two is the wrong firm for a project on the other.
That single question, which credential, by its exact current name, filters a shortlist faster than any case study, because the answer is checkable and the names moved recently enough that a stale proposal gives itself away.
Decide which product you are buying the consultant for
The three engagements people describe with the same sentence are genuinely different projects with different skills, different timelines and different failure modes.
| If the project is | You are hiring for | The scarce skill |
|---|---|---|
| High volume consumer email, SMS and push with complex journeys | Marketing Cloud Engagement, the platform that grew out of ExactTarget | Data modelling in its own model, scripting, and deliverability. This is the one that genuinely needs a developer |
| Business to business capture, scoring, nurture and handover to a sales team | Marketing Cloud Account Engagement, previously called Pardot | A marketing operations person who knows the CRM object model, not a developer |
| Connecting the two, or connecting either to the CRM properly | An integration project, not a configuration one | Whoever has done the connector work before and will say what broke last time |
Our page on the products under the Marketing Cloud name and which one you need maps the licensing decision in full, including how to find out which pieces your own organisation already owns, and it is worth settling before a consultant quotes anything. For the prior decision of whether to run automation on a Salesforce platform at all, our page on the three routes and how to pick between them sets out the third option, which is a connected third-party platform and is the right answer more often than it is offered.
The criterion this page ranks on, and what it could and could not read
The criterion is what a buyer can verify about a consultant before any call, applied to every route including the ones Salesforce runs itself. On this criterion the individual credential comes first, and the reason is that it was the only part of the chain that rendered.
First, the named credential held by the named person who will do the work. It is specific, it belongs to a human rather than to a logo, and the credential title is published. Ask for the names of the two or three people who will be on the project and the credential each holds, then check the current title matches. A firm that answers with a company badge rather than named people has answered a different question.
Second, a reference from a project on your product. Not a client logo and not a sector. A conversation with somebody who ran the same product at roughly your data volume, because volume is what breaks these implementations.
Third, the public partner directories, which this page cannot rank because they did not render. Fetched on 22 October 2026, appexchange.salesforce.com/consulting returned only its document title with no listing content, so its filters, tiers and review ratings could not be read. A credential URL for the Account Engagement consultant exam issued an HTTP 301 to a different host and that destination served an empty body on the same date. A partner-programme brochure in circulation carries "(DRAFT)" in its own document title and its body did not render as text. Those three fetch records state what each server returned on that date and are not evidence that the directories are empty or that any tier name is wrong. They are the reason no tier name appears on this page: the tier labels passed around in this market are worth less than the credential you can look up yourself, and several of them belong to programme generations that have since been restructured.
If a proposal rests on a partner tier, ask which page it was read from and on what date, and read that page yourself. It costs five minutes and it is the same discipline a good consultant will apply to your data.
The four routes, and who each one is right for
The large systems integrator. Right when the Marketing Cloud project is one workstream inside a wider programme and governance matters more than speed. Carries the bench depth to survive somebody leaving, which is the real argument for it. Ask who is on the account in month four, because the people in the pitch are frequently not the people in the build.
The Marketing Cloud specialist firm. Ten to sixty people, this platform and little else. Usually the best value for a single implementation or a rescue, and the most likely to tell you the honest answer about deliverability. The trade is concentration risk: a firm of that size that loses its one Engagement developer has lost Engagement.
The independent contractor. Highest seniority per dollar, least capacity, and genuinely the right purchase for a defined piece of work such as a data model review, a deliverability audit or a rescue of a stalled build. Wrong for anything that has to be supported for two years.
Salesforce's own professional services. Right where the problem is contractual or where you need the vendor accountable for its own product behaviour. Priced accordingly and quoted through a sales conversation.
What to settle in the statement of work
- Named people and named credentials, in the document, with a change-of-staff clause. This is the whole point of the criterion above and it is worth nothing if it lives only in the pitch.
- Which system is the source of truth for the customer record. Agree it in writing on day one. Almost every expensive failure in this category traces back to two systems that were each allowed to believe they were the master.
- The data volume the build is sized for, two years out. Contact count growth is what moves both the licence invoice and the architecture, so size for the number you expect rather than the one you have.
- Who owns the configuration knowledge. A named person on your side trained during the build, not after it, and documentation as a deliverable rather than a favour.
- Deliverability ownership. Sending reputation is operational and permanent. Name who watches it after the consultant leaves.
- An exit that leaves you able to send. Credentials, sending domains and the automation inventory in your own accounts.
When a Marketing Cloud consultant is the wrong purchase
If nobody internally will own marketing operations afterwards, the implementation will be correct and unused, and the first hire is a person rather than a project. If the requirement is business-to-business nurture on a CRM you already run, the Account Engagement route needs a marketing operations person far more than it needs a consultancy. And if you are still choosing between platforms, a Marketing Cloud consultant is the wrong adviser for that question by construction, because the answer that recommends a different vendor costs them the work. Take the platform decision first, separately, and ideally from somebody who is not selling the build.
Questions a marketing operations lead asks before appointing a Marketing Cloud partner
How long does an Engagement implementation take? A simple sending setup on a clean data source runs in weeks. A build with a real data model, several sources and journeys that cross channels is a quarter at minimum, and the data work is most of it. A plan that puts the first journey live in week two is describing a send, not an implementation.
Do we need a developer or an operations person? Engagement work usually needs both, because scripting and data extensions are development. Account Engagement usually needs neither, and hiring a developer for it buys skills the platform cannot use.
Is a certification enough on its own? It proves the product knowledge and says nothing about judgement or deliverability experience. Treat it as the filter that gets a firm onto the list and the reference call as the thing that gets it off.
Should we hire the firm that sold us the licences? Sometimes, and settle one thing in writing first: that the implementation fee is not contingent on buying further licences. It is incentive rather than dishonesty, and naming it early costs nothing.
What does a rescue engagement look like? A short paid audit against a fixed scope, delivered as a written assessment you own, with no commitment to the rebuild. Any firm unwilling to sell the audit on its own is selling the rebuild.
The shortlist a buyer never sees you on
This page has argued that you should check a credential rather than take a claim, which raises the obvious question about the stage before any of it. Note how the shortlist you are on gets built. A marketing operations lead short of time asks an assistant which firms implement Marketing Cloud for a company like theirs, and two or three names come back with a reason attached, assembled from trade coverage, community answers, published documentation and third-party write-ups rather than from a partner profile or the firm's own site. That is the one stage of a consultancy's pipeline with no login and no report behind it, and it happens before anybody evaluates anything. If you run one of these firms, AI Knows Us records which names the assistants give on that question and which pages each answer leaned on, which is the same evidence-first habit this page has been recommending, pointed at your own business. The scan on your own domain is free and needs no account, and Growth at $299 a month is the cheapest plan that reads all five of ChatGPT, Gemini, Perplexity, Claude and Google AI Overviews, read on our pricing page on 22 October 2026.
Two things a consultancy evaluating us should know, because both count against us here. Profound publishes "SSO/SAML + SOC 2 compliance" on its Enterprise tier, read at tryprofound.com/pricing on 22 October 2026, while our own rendered pricing text carries no SSO, no SAML, no SOC 2, no ISO, no white label and no data processing agreement. A firm whose clients run enterprise security reviews will be asked for exactly that pack, and we do not publish one. Second, our pricing page states both that the Agency plan covers 10 brands and, in its own comparison table, that "More than one business" is No for every plan including Agency. Both of those render on the page today, so if you intend to watch several client brands, settle which one applies before you buy, and read our page on marketing automation for agencies and the client workspace question, which works through the same multi-client constraint in the automation tools themselves.