Ask buyers who chose, ran and replaced a marketing automation platform what they would tell their past self, and the answers return to the same places: who actually runs the platform, how a Salesforce CRM shapes the choice, what makes leaving hard, how the bill grows, whether the tool fits the team and the audience, and where the platform is headed.
The six lessons
Enterprise marketing automation often needs specialists alongside marketers
One recurring lesson in these interviews is about who runs the platform. Buyers of the enterprise platforms describe needing dedicated experts, developers or consultants for work they expected marketers to do. One says of Eloqua, “you really need a team of Eloqua experts in order to run the system. It's not like a marketer self-service system.” Another calls Salesforce Marketing Cloud “a very dev-heavy resource, so it requires a lot of cost and effort to be able to deploy workflows and email content.” A Marketo buyer finds it “not intuitive or easy for a newcomer to get used to the platform,” and a Pardot buyer says “We obviously need a certified consultant for the initial setup.” The cost shows up downstream, in teams “spending a lot of time pulling basic reports instead of providing insights,” and in platforms used “pretty archaically where we're pulling in CSVs.” The implication — ours, not a buyer's — is that the team to run the platform is part of what you are buying.
Named in this context: Eloqua · Salesforce Marketing Cloud · Marketo · Salesforce Account Engagement
Salesforce pulls the decision toward its own tools — but same-vendor does not guarantee integration
Buyers running Salesforce as their CRM describe it pulling the automation decision toward Salesforce's own tools. One weighing a move from HubSpot wants “the data lives in one ecosystem rather than attempting to synchronize it across two systems that don't have the same underlying data architecture.” Another, moving from Marketo to Salesforce Marketing Cloud, cites native integration and Salesforce's pace on AI. The same gravity cuts the other way: a Pardot buyer says “Salesforce dependency is a lock-in.” And a shared brand is not the same as integration. One buyer says of Salesforce's own products that “there are certain APIs, there are certain modules which do not talk even though they are coming from the same brand or the same stable,” and another finds Marketo and Salesforce numbers that do not match “even though there's a bilateral sync.” Some report the opposite: one Marketo setup “synced extremely well with Salesforce, especially the lead scoring model.”
Named in this context: Salesforce Marketing Cloud · Salesforce Account Engagement · Marketo · HubSpot
Your own campaigns, code and integrations create the switching cost
Buyers describe lock-in less as a contract term than as everything accumulated inside the platform. One Eloqua team has “five years of campaign history, email templates, and data basically in there. So we want to make sure that we do not lose that.” A Marketo buyer has “a ton of static code built on Marketo, which is the backbone of our marketing stack,” and chose to build AI agents on top rather than replace it. Another says “it's hard to make the switch when your program is already connected and ingrained into so many things,” and a third may be “stuck with Marketo for the long term” because its website forms are not supported by the vendor it would prefer. Trained staff count too: one buyer says retraining on another platform “takes a lot of cost.” Not everyone agrees — a Salesforce Marketing Cloud buyer with a certified team says “I believe they could get trained in another tool.”
Named in this context: Eloqua · Marketo · Salesforce Marketing Cloud
Pricing can climb with records, profiles and scale
Several buyers describe costs that scale with what they store rather than what they send. A Marketo buyer: “So it's priced by the number of records you have in the system, not by the volume of email that you send, which is weird.” A Braze buyer: “as we add more data to user profiles, we end up having to pay more, which seems counterintuitive.” A HubSpot buyer describes the same curve at a different point — “the moment you go at the enterprise level scale, the price gets increased very quickly.” Some respond by splitting audiences: one would keep Marketo for business contacts and move consumer contacts to “a different solution that is more cost-effective.” For one Salesforce Marketing Cloud buyer the goal is simply “to avoid surprises.” The mechanisms differ by platform; the implication — ours, not a buyer's — is to model the bill against growth in records and profiles, not just today's licence.
Named in this context: Marketo · HubSpot · Braze · Salesforce Marketing Cloud
Fit breaks in two places: operating complexity and audience
Buyers describe two mismatches. Easier platforms hit a ceiling: HubSpot “is good for a small-sized office, but the moment the complexity and interconnection of the workflows increases, then it's not giving you enough,” says one buyer, and another worries it is “not robust enough to handle the volume of marketing that we do.” Enterprise suites overshoot the other way: one buyer notes that “lighter costing tools with lesser maintenance can be useful compared to Salesforce, which is a full corporate or enterprise level solution.” The second mismatch is audience. A membership organization moved to Salesforce Marketing Cloud because “We needed a Marketing Automation tool that could serve both broad scale B2C and B2B Marketing use cases,” and is now weighing separate platforms because others “offered more tailored solutions for B2B and B2C audiences.” HubSpot has its defenders on adoption: one buyer's team “picks it up quickly.”
Named in this context: HubSpot · Salesforce Marketing Cloud
For some replacement buyers, the roadmap enters the decision
In several decisions to replace a platform run for years, the roadmap — especially on AI — enters alongside features. One replacing Eloqua says “Eloqua's roadmap is falling behind its competitors”; another “did not want to replace Eloqua with another legacy Marketing Automation Platform (MAP) like Marketo or HubSpot or Salesforce Marketing Cloud,” and shortlisted newer platforms instead. A Marketo buyer moving to Salesforce Marketing Cloud sees Salesforce's AI and agentic features “evolving much faster than Marketo in that aspect.” Buyers are wary of the newcomers too: of AI-native platforms, one asks “They can do a good demo, but is it what people are actually using on a day-to-day basis?” The implication — ours, not a buyer's — is to ask which roadmap items are already in customers' hands.
Named in this context: Eloqua · Marketo · Salesforce Marketing Cloud · HubSpot
How buyers rate the platforms
Every figure is the platform's average across verified buyer interviews, on published transcripts, from every buyer in the corpus who rates it — not only those shopping for marketing automation. Several of these tools are bought as email or lifecycle platforms as much as for automation, which is why consumer and B2B tools sit in one table.
| Platform | Rating | What buyers describe |
|---|---|---|
| Klaviyo | 7.7 | Ecommerce-rooted; buyers here use it for consumer lifecycle automation rather than lead management. |
| Braze | 7.5 | Cross-channel engagement for consumer lifecycles; one buyer finds its data-point pricing climbs as profiles grow. |
| HubSpot | 7.4 | Automation and CRM in one suite; praised for adoption, questioned at enterprise complexity and price. |
| Mailchimp | 7.2 | Some buyers here moved up from it to HubSpot or Marketo as their needs grew. |
| Iterable | 7.1 | Lifecycle automation for consumer businesses rather than lead management. |
| Marketo | 6.8 | B2B automation; buyers here describe specialist dependence and accumulated code that makes leaving hard. Blends three duplicate records. |
| Salesforce Marketing Cloud | 6.8 | Enterprise marketing suite; buyers here describe Salesforce fit in selection decisions, alongside SQL-heavy builds and dedicated teams in operation. |
| Eloqua | 6.5 | B2B automation; buyers here cite strong Salesforce sync and a steep learning curve. Blends two duplicate records. |
| Salesforce Account Engagement | 6.2 | Formerly Pardot; chosen for native Salesforce integration, criticized for its interface and the dependence it creates. |
The stories behind the lessons
The counter-current: for some teams the platform simply works
Not every buyer here is fighting their platform. One Eloqua team describes a Salesforce sync that “feels real-time even though it syncs every 15 minutes; the data feels real-time, and inaccuracies are completely minimal.” A Marketo buyer puts it plainly: “We're very happy with it.” Another says Eloqua “has grown with us” as its database expanded several-fold, and a HubSpot buyer says that, unlike other legacy systems, “sales reps actually use HubSpot.” The positive cases are different: strong CRM sync, satisfaction with an established setup, successful database growth, and user adoption all appear.
Want this read against your own stack?
Get my read →What this means for your marketing automation evaluation
Across these interviews, buyers repeatedly describe decisions that extend well beyond email features: who will run the platform, how it sits next to the CRM, what it costs as the database grows, and how hard it becomes to leave after the team builds on it. Our recommendation, not a practice buyers describe: price the team and the database alongside the licence, and test the CRM sync on your own records before signing. For what marketing automation is and how it differs from an email platform, see What is marketing automation?; for what the bill is made of, what buyers actually pay for marketing automation; for where buyers go when they leave, Marketo alternatives, Eloqua alternatives, Pardot alternatives and HubSpot alternatives; and for the head-to-heads, Marketo vs. HubSpot and Eloqua vs. Marketo.
Common questions
What do marketing automation buyers wish they had known before buying?
Six things recur in these interviews. Enterprise platforms often need specialists alongside marketers, so the team is part of the purchase. A Salesforce CRM pulls the decision toward Salesforce's own tools, though same-vendor products do not always integrate. A team's own campaigns, code and integrations create the switching cost. Pricing can climb with records, profiles and scale. Fit breaks in two places: lighter platforms hit complexity ceilings while enterprise suites add maintenance, and one tool may not serve business and consumer audiences equally. And some buyers replacing a long-running platform weigh its roadmap, especially on AI.
Which marketing automation platform do buyers rate highest?
Among the platforms in the table, Klaviyo rates highest at 7.7/10, but it is an ecommerce-rooted tool buyers put to consumer lifecycle work. Among platforms built around business lead management, HubSpot rates 7.4/10, Marketo 6.8/10, Eloqua 6.5/10 and Salesforce Account Engagement, formerly Pardot, 6.2/10. Salesforce Marketing Cloud, the enterprise suite, rates 6.8/10. These are overall product ratings from buyers across the corpus, not only from buyers shopping for marketing automation.
Is HubSpot good enough for enterprise marketing automation?
Buyers split. Several describe it as easy to adopt and genuinely used — one says sales reps actually use it, unlike other legacy systems — but several say it hits a ceiling as workflows grow more complex or volumes rise, and that its price climbs quickly at enterprise scale. The enterprise platforms buyers compare it with draw the opposite complaint: power that needs specialists to run.
How hard is it to switch marketing automation platforms?
Harder than the contract suggests, in these interviews, and the switching cost is built by the buyer as much as by the vendor: years of campaign history, templates, custom code, website forms, integrations and trained staff tied to the platform. Some keep an incumbent for that reason alone. The switches buyers here describe mostly run between business-focused platforms, such as Eloqua to Marketo, Marketo to Salesforce Marketing Cloud and Pardot into HubSpot, for CRM fit, consolidation or covering both business and consumer audiences.
Should your marketing automation platform come from your CRM vendor?
Buyers on Salesforce describe a strong pull toward Salesforce's own automation tools, to keep data in one ecosystem rather than syncing two. The same buyers name the downside: dependence on that CRM, and products under one brand that do not always integrate with each other. Some buyers report clean syncs between independent platforms and Salesforce, so the interviews do not settle it either way.
Get this research made for your stack
Choosing a marketing automation platform, or weighing a move off the one you run? Do a 15-minute interview about your CRM, your audience and your team and get this personalized — who would run it, what it would cost as your database grows, and which of these lessons would land on you.
Get my personalized read — 15-min interviewNo password · your interview is anonymized before it ever informs a page like this one.