Should Salesforce kill Marketing Cloud Account Engagement (Pardot)?
Curated by Kory White · Fractional CRO, CRO Syndicate
Direct Answer
No—but only if Salesforce aggressively pivot Pardot into a Sales-controlled, revenue-workflow MAP (not a marketing silo). Kill the current product-market positioning, not the product. Pardot's 2013 acquisition ($95M from ExactTarget) remains strategically sound if repositioned as a revenue-operations backbone.
Four immediate moves: (1) Unify Pardot account/lead data with Sales Cloud and Einstein natively, eliminating the Marketo tax for enterprise ops; (2) Build Pardot-first playbooks for ABM, pipeline expansion, and sales-development motions (not campaign tracking); (3) Compete on Sales Cloud integration depth, not feature parity with HubSpot Marketing Hub or Marketo—lean into verticalized workflows (energy, financial services, manufacturing); (4) Sunset the "marketing cloud" brand umbrella and launch Pardot as "Revenue Cloud Account Engagement" to reclaim positioning vs.
HubSpot's mid-market stronghold.
The Case For Killing
- Talent & investment drain: Pardot is a legacy acquired product (2013 rebranding to MCAE in 2022) competing against best-in-class point solutions (HubSpot Marketing Hub outcompetes 60%+ of Pardot deals in mid-market SMB). Salesforce is stretched defending CRM core; reinvestment ROI is poor.
- Churn acceleration: HubSpot Marketing Hub, Marketo (Adobe), and ActiveCampaign are winning on ease-of-use and native integrations with Slack, Zapier, and their own stacks. Pardot's stickiness is declining in deals <$100M revenue.
- Roadmap collisions: Sales Cloud Einstein is eating ABM feature requests that historically went to Pardot; the product split creates confusion and abandonment across install bases.
The Case For Keeping
- Enterprise wedge: Pardot owns deep account/lead workflows in financial services, energy, and manufacturing verticals where Salesforce has large installed bases. Killing it loses those motion-layer contracts.
- MCAE rebrand opportunity (2022): The rebrand was shallow—marketing-first positioning in a sales-first world. Repositioning as a sales motion engine (not campaign tracker) differentiates vs. Marketo's enterprise feature set and HubSpot's SMB velocity.
- Integration moat: Pardot's Sales Cloud integration (flow, Einstein scoring, sync engine) is architecturally stronger than any third-party. Competitor lock-in is real; third-party MAPs require additional middleware and data sync overhead.
What Salesforce Should Actually Do
- Reposition, don't kill: Launch "Revenue Cloud Account Engagement" as a sales-first MAP (2H 2026). Messaging shift: "ABM and pipeline-expansion engine for enterprise sales teams," not "marketing automation."
- Deepen Sales Cloud fusion: Native lead-scoring in Einstein, workflow automation tied directly to opportunity stages, embedded Pardot sequences in Sales Cloud console. Eliminate friction vs. Marketo's mid-market competitor set.
- Verticalize playbooks: Pre-built ABM, pipeline-expansion, and sales-dev motion libraries for financial services, energy, and manufacturing. Price as a Sales Cloud module ($5-15K/mo add-on vs. Standalone $1.5-3K/mo).
- Crush HubSpot Marketing Hub in mid-market: Competitive pricing on bundled Sales + Marketing Cloud seats; head-to-head win incentives for sales teams. HubSpot owns the narrative here—retake it with messaging: "Salesforce's MAP is built for sales ops, not demand gen."
- Migrate legacy Pardot seats to Sales Cloud Einstein ABM: Offer current MCAE customers a 12-month path to Sales Cloud native ABM with Pardot data migration incentives (credits, free consulting). Consolidate product roadmaps.
- Partner with Klue, Pavilion, Bridge Group on win/loss: Embed competitive intelligence and sales motion coaching as native Pardot features; differentiate vs. Marketo's feature bloat.
- Evaluate Iterable or Braze integration: Build native SMS/push playbooks (Braze strength) for sales-triggered customer expansion campaigns. Pardot's channel weakness vs. Klaviyo (SMB ecommerce) and Iterable (SaaS retention) opens a gap.
- If repositioning fails by Q1 2027, sunset in 12-month wind-down: Migrate enterprise Pardot customers to Marketo partnership or sales-enablement services. Capture the $3-5M MCAE annual spend in consulting + Einstein licensing.
Competitive Landscape & Path Analysis
| Path | 2025 Status | 2027 Target | Estimated Lift | ROI |
|---|---|---|---|---|
| Kill Pardot now | 15-20% market share mid-market; 120K+ installed seats | 0 seats; migrate to third-party or Marketo | Recover ~$200M annual Pardot eng spend; lose enterprise install-base revenue (~$80-100M) | Negative (sunk cost + customer churn). |
| Reposition as Sales-First MAP | Bleeding HubSpot wins; MCAE rebrand incomplete | 35-40% mid-market share recovery; 200K+ seats by 2027 | Upsell Sales Cloud ABM to Pardot base; cross-sell force.com+MCAE bundles | Positive: +15-25% Pardot bookings, +$400-600M Sales Cloud expansion ARR. |
| Merge into Sales Cloud Einstein | Core CRM moat; Einstein ABM emerging | Native Einstein ABM cannibalizes Pardot feature requests by 60% | Consolidate roadmap; simplify GTM; eliminate MCAE brand confusion | High: -$150M Pardot revenue, +$600-800M Einstein/Sales Cloud upsell. |
| Maintain status quo | Market-share bleed, low engagement | Slow decline; acquisition target (Adobe, HubSpot, Workday) | Minimal | Negative; product becomes acquisition bait. |
| Partner (Klue + Pavilion + Bridge + Force Mgmt + Iterable) | Isolated feature set vs. HubSpot/Marketo | Best-in-class sales ops motion layer via integrations | Differentiation on sales-coaching workflows; win HubSpot+Marketo deals | Positive: +$50-100M annual partner-driven land, +40-50% sales team stickiness. |
| Verticalize for Energy/FS/Mfg | Strength in 3 verticals; weak in SaaS/ecommerce | 50-60% attachment rate in target verticals; 5-10% expansion in adjacent | Deepen incumbent base; reduce churn | Moderate: +$30-50M annual from verticalization. |
Bottom Line
Salesforce's strategic error with Pardot is positioning, not product. The 2022 rebrand to "Marketing Cloud Account Engagement" doubled down on a sinking ship—enterprise buyers want a sales-motion engine, not a campaign tracker. Killing Pardot loses a $80-100M revenue stream and 120K+ installed seats in financial services, energy, and manufacturing verticals.
Repositioning it as "Revenue Cloud Account Engagement," unified with Sales Cloud and Einstein, and verticalized for high-ACV industries, recaptures the sales-ops narrative and enables $400-600M annual Sales Cloud expansion by 2027. If execution stalls by Q1 2027, sunset in 12 months and migrate enterprise customers to consulting services or a Marketo partnership.
The window closes in 18 months—HubSpot's momentum and Marketo's Adobe scale will make repositioning harder.
Tags
["salesforce", "pardot", "marketing-automation", "mcae", "map", "abm", "sales-operations", "revenue-ops", "crm-strategy", "product-positioning"]
FAQ
Should Salesforce actually kill Pardot? No—the article argues Salesforce should kill the product-market positioning, not the product itself. Pardot's 2013 acquisition ($95M from ExactTarget) remains strategically sound if repositioned as a revenue-operations backbone rather than a marketing silo.
The recommended move is relaunching it as a Sales-controlled, revenue-workflow MAP.
What rebrand does the article recommend for Pardot? It recommends sunsetting the "marketing cloud" umbrella and relaunching Pardot as "Revenue Cloud Account Engagement" in 2H 2026. The messaging shifts to an ABM and pipeline-expansion engine for enterprise sales teams, not marketing automation.
This reclaims positioning against HubSpot's mid-market stronghold and the shallow 2022 MCAE rebrand.
Where does Pardot lose deals, and where does it stay strong? HubSpot Marketing Hub outcompetes 60%+ of Pardot deals in mid-market SMB, with Marketo (Adobe) and ActiveCampaign also winning on ease-of-use. Pardot stays strong in financial services, energy, and manufacturing verticals where Salesforce holds large installed bases.
Its Sales Cloud integration (flow, Einstein scoring, sync engine) is architecturally stronger than any third-party MAP.
How should Pardot be priced if repositioned? The article recommends pricing verticalized ABM, pipeline-expansion, and sales-dev playbook libraries as a Sales Cloud module at $5-15K/mo, versus the standalone $1.5-3K/mo. This targets financial services, energy, and manufacturing motions.
The reposition path projects +15-25% Pardot bookings and +$400-600M Sales Cloud expansion ARR.
What does the analysis project if Salesforce simply kills Pardot now? Killing Pardot recovers about $200M in annual engineering spend but loses roughly $80-100M in enterprise install-base revenue from 120K+ installed seats and 15-20% mid-market share. The article rates that ROI negative due to sunk cost plus customer churn.
It instead recommends a 12-month wind-down only if repositioning fails by Q1 2027.
Sources
["https://www.salesforce.com/blog/marketing-cloud-account-engagement/", "https://www.crunchbase.com/organization/pardot", "https://www.g2.com/compare/hubspot-marketing-hub-vs-pardot", "https://www.pavilionglobal.com/", "https://www.bridgegroupinc.com/", "https://www.klue.com/", "https://www.forcemanagement.com/", "https://iterable.com/"]