MCAE (formerly Pardot) is Salesforce's B2B marketing automation platform. Architecture-first consulting across four engagements: Strategy Consult ($1.5K–$2.5K), Audit ($1.5K–$2.5K), Implementation ($5K–$20K+), and Post-Launch Advisory ($5K–$10K/mo). Every engagement ends with documentation, training, and 60-day support. After 90 days your team owns the system — no retainer trap, no junior hand-offs, no agency markup.
Unlike typical MCAE partners who optimize for retainer length, this practice optimizes for client autonomy. The deliverable is a working revenue system your in-house admin can maintain — not platform dependency. Back-tested scoring against your actual closed-won data, honest opinion on edition fit, and a clear answer on whether MCAE is the right platform at all.
Salesforce launched Marketing Cloud Next (MCN) at Connections '25 — the Data Cloud-native, Agentforce-powered successor to the broader Marketing Cloud portfolio. The official position is "convergence, not migration." Pardot/MCAE continues receiving updates with no announced sunset date. Most existing MCAE teams should not migrate in 2026. New B2B buyers should evaluate both seriously.
Read the Pardot-to-MCN 2026 Decision Framework (7-question test) before committing direction. For existing customers wanting MCN features without full migration, Account Engagement+ (AE+) is the bridge — see Model 03 on the implementation page.
Salesforce renamed Pardot to Marketing Cloud Account Engagement in 2022. Four years later you will still find both names in the same Slack thread, the same vendor contracts, the same Salesforce documentation. The naming changed. The platform did not really change. The buying decisions you face have not either.
If you are evaluating MCAE (or already running it), you need answers to four specific questions: which edition matches your B2B sales motion, when MCAE is the right call vs MCN, HubSpot, or Marketo, whether AE+ is the right move in 2026, and which architecture decisions determine whether your investment pays back. That is what this page covers.
If you have inherited a Pardot org and you are trying to figure out what it actually is — here is the practical answer most documentation skips. Four facts that determine every architectural decision downstream.
Same B2B marketing automation platform Salesforce acquired in 2013. The rebrand to Marketing Cloud Account Engagement happened in April 2022 — but the URL is still pi.pardot.com, the API still says Pardot, and your existing automations did not get changed. The naming is the only thing Salesforce actually shipped that day.
Confusingly named — MCAE is not part of Marketing Cloud Engagement (the B2C platform, formerly SFMC/ExactTarget). They are two different products with different data models, journey builders, and pricing. If a vendor says "we work with Marketing Cloud" — ask specifically which one. Most teams who say "Marketing Cloud" mean Account Engagement.
MCAE syncs with Sales Cloud via the Connector, but it has its own database, its own automation engine, and its own scoring logic. That is why sync drift is the #1 architectural failure: two systems, two truths, no governance between them by default. Per Salesforce Ben's integration guidance, sync architecture is the foundation everything else depends on.
Three editions (Growth, Plus, Advanced) with hard limits on prospects, automations, and users — plus the new Account Engagement+ (AE+) Permission Set License tier that grants Marketing Cloud Next features alongside your existing Pardot. Most teams pick the wrong edition because the pricing page hides the upgrade trap. See Section 3 for honest edition guidance.
Four principles that determine every architectural decision. They are also why some engagements succeed and others end in a $50K migration nobody wanted.
MCAE is part of your RevOps stack — not an isolated email tool. I design backwards from how your CFO reports revenue, not forwards from what features the platform has.
Data model, sync rules, and object logic defined in Salesforce first, then reflected in MCAE — not the other way around. The setup that fights Salesforce conventions is the one that breaks at the worst possible moment.
Segmentation, scoring, and Engagement Studio journeys built around real buyer intent — not opens and clicks. The work happens before I touch a scoring rule: understanding what closed-won deals actually look like in your business.
Reporting tied to pipeline and revenue — not opens, clicks, or vanity metrics. Connected Campaigns properly configured. B2B Marketing Analytics surfacing what matters. Attribution math your CFO can defend in a board meeting.
If MCAE is already live and underperforming, the right next step is a focused audit — not another platform rebuild. Audit identifies which architectural gaps are blocking pipeline and what each one costs you in dollars per quarter.
See audit details →Salesforce's pricing page lists features. It does not tell you which edition fits which sales motion — and that is where most teams overspend by $30K/year or underspend and hit upgrade hell six months in. Five tiers below, based on 20+ MCAE engagements across B2B mid-market. Plus is the mid-market default — 8 out of 10 teams should be there. AE+ is new in 2026 as the MCN bridge for existing customers.
Fits: Series A B2B SaaS, <50 sales reps, single product line, simple sales motion.
Hard limits: 10,000 prospects, no custom roles, no B2B Marketing Analytics, no dynamic content, no Einstein scoring. You will outgrow this within 12 months if you are scaling demand gen.
When it is wrong: if you have got more than one product line, you need ABM, or your sales team uses opportunity-level attribution. Upgrade to Plus.
Fits: Series B/C B2B, 50-200 sales reps, multi-product, ABM-aware sales motion. This is where 8 out of 10 B2B mid-market teams should be.
Unlocks: 10,000 prospects, B2B Marketing Analytics (the reporting layer Growth does not have), custom user roles, advanced dynamic content, Einstein Lead Scoring.
When it is wrong: if you need API limits beyond 25K calls/day, multi-business-unit segmentation, or developer sandbox isolation. Then Advanced.
Fits: Enterprise B2B, 200+ sales reps, multi-business-unit, complex compliance requirements (HIPAA, financial services), heavy MuleSoft integration.
Unlocks: Developer sandbox, multi-touch attribution beta, custom object support, API limits 100K/day, AI scoring beta features.
When it is wrong: if you are paying for Advanced but only using Plus features — that is $18K/year wasted. Audit before renewal.
Fits: Enterprise B2B with dedicated MCAE team, custom Apex integration, multiple geographic regions, strict data residency requirements.
Unlocks: Premier success, dedicated technical account manager, expanded API limits, custom feature requests.
When it is wrong: mid-market teams do not need Premium. If a vendor recommended it without a specific multi-region or compliance justification — get a second opinion.
Fits: existing MCAE customers (any edition) who want Marketing Cloud Next features without full migration. Permission Set Licenses extend your current Pardot environment with MCN capabilities.
Unlocks: Agentforce campaign creation, native SMS / WhatsApp, advanced personalization, Data 360 segmentation — running alongside your existing Pardot, not replacing it.
When it is right: for most existing Pardot customers in 2026, per the MCN Decision Framework. See implementation Model 03 for $5K-$15K enablement details.
Edition changes have a hidden cost most pricing comparisons miss. Moving from Growth to Plus requires re-architecting custom roles, lifecycle stages, and B2B Marketing Analytics setup. Moving from any edition to a different platform (HubSpot, Marketo, MCN) costs $50K–$200K and loses 30–60% of engagement history. Audit before edition change. Audit before platform change. The audit ($1,500–$2,500) prevents the $50K wrong-direction decision.
Most teams pick wrong because the Salesforce pricing page hides the upgrade trap. Book a 15-minute routing call — I will listen to your sales motion and tell you honestly which edition fits. No upsell.
Book a 15-minute routing call →This is the most common pre-engagement question I get. The honest answer in 2026: if you are already on Salesforce, MCAE is usually the right call — but not always, and the MCN convergence shifts the calculus for new buyers. Four platforms compared below across the eight dimensions that actually drive the buying decision, based on what your sales motion looks like — not what vendor pitches sound like.
| Dimension | MCAE (Pardot) | MCN (Marketing Cloud Next) | HubSpot | Marketo |
|---|---|---|---|---|
| License pricing model | Tier-based per org ($1,250–$15,000/mo) | Consumption credits + base ($1,500–$3,250+/mo) | Seat-based + contact tiers | Tier-based per database (high entry cost) |
| Data foundation | Own database, syncs to Salesforce CRM | Data 360 / Data Cloud native (prerequisite) | HubSpot CRM (own data model) | Own database, native Salesforce sync |
| AI capabilities | Einstein scoring (Plus+), basic AI | Agentforce-native, agent-driven workflows | Breeze AI assistant, generative content | Predictive content, basic AI scoring |
| Use case scope | B2B only mid-market focus | Unified B2B + B2C orchestration | B2B + content marketing inbound-heavy | B2B enterprise ABM at scale |
| Salesforce integration | Native connector-based sync (mature, known issues) | Native platform (Einstein One) | Bidirectional via integration (acceptable, not native) | Native Salesforce sync |
| Content marketing / CMS | Limited — landing pages, emails only | Limited — same B2B focus | Strong — CMS, blog, SEO tools built-in | Limited — automation-first, content secondary |
| When it is right | Existing Salesforce shop, B2B mid-market, account-based motion, mature consulting ecosystem | Greenfield buyers with Data Cloud commitment + Agentforce strategy | Content-marketing-led B2B SaaS, no Salesforce yet, inbound primary | Enterprise ABM at scale, complex multi-region orchestration |
| When it is wrong | Not on Salesforce; B2C use case; content-marketing-led GTM | No Data Cloud strategy; risk-averse to platform maturity gap | Heavy ABM with custom orchestration; deep Salesforce integration critical | Mid-market without enterprise needs (overspend by 2-3×) |
Migrating from MCAE to HubSpot or Marketo costs $50K–$200K, takes 6 months of your team's calendar, and loses 30–60% of engagement history and attribution data. Migrating to MCN costs $15K–$300K+ depending on Data Cloud readiness (see the MCN Decision Framework).
Before signing any migration contract: get a $1,500–$2,500 audit on your current MCAE setup. In 9 out of 10 cases, the problem is not the platform — it is the architecture. The audit pays for itself by preventing the wrong $50K decision.
MCAE work breaks down into five distinct engagements depending on where you are. If you are not sure which fits your situation, the 15-minute routing call sorts that out in 10 minutes. Audit and Optimization are separate engagements — diagnostic before treatment.
When you need it: Your MCAE is live but underperforming. Before deciding on edition upgrade, replatform, or major investment.
Diagnostic-only, 1-2 weeks, $1,500-$2,500, read-only access. Output: prioritized findings with dollar impact, edition-appropriate recommendations, and clear next steps. The audit answers "is MCAE the right platform, or is the architecture broken?" before you commit to a $50K+ direction.
When you need it: Audit done, you know what is broken, ready to fix. Scoring rebuild, sync repair, attribution reconstruction.
3-6 weeks, $5,000-$15,000, ends with documentation and 60-day support. Requires a recent audit (so we are fixing the right things, not what looks broken on the surface). The treatment after the diagnosis.
When you need it: Greenfield MCAE deployment, edition refresh (Growth → Plus → Advanced), full relaunch on existing org, or AE+ enablement.
$5,000-$20,000+, 4-14 weeks. Architecture-first deployment that respects MCAE's specific constraints — prospect limits per edition, sync rule limitations, Engagement Studio capacity. AE+ Model 03 is new in 2026: extends existing Pardot with Marketing Cloud Next features.
When you need it: Inbound migration to MCAE (from HubSpot, Marketo, Mailchimp), org-to-org migration (acquisition or restructure), or rebuilding integrations (ZoomInfo, LinkedIn, custom Apex).
MCAE-specific migration playbook: prospect deduplication against Salesforce contacts, lifecycle stage mapping, engagement history preservation. The differentiator is not losing engagement data — most migrations lose 30-60% of it, which kills attribution for 6+ months.
When you need it: Your MCAE scoring model produces leads Sales ignores. Or you are evaluating Einstein Lead Scoring (Plus edition+) vs custom scoring and need an honest take.
MCAE-specific scoring architecture: leveraging Score Categories (if available in your edition), grading model design, decay rules, B2B Marketing Analytics integration. The deliverable is a scoring model your edition supports — not enterprise features you do not have licensed.
Three engagement shapes depending on where you are in the decision cycle: pre-platform-commitment (Strategy), platform-live-needs-fixing (Full-cycle), or post-launch oversight (Advisory). All three end with documentation and 60-day support. Choose by maturity, not by price.
For teams making platform decisions (MCAE vs MCN vs HubSpot/Marketo, edition choice, replatform timing, AE+ vs full migration). 1-2 weeks, $1,500-$2,500. No implementation — just clarity. Output: written recommendation with reasoning, sized to your sales motion. Useful when leadership needs an independent opinion before committing to a 12-month direction.
For teams ready to fix what is broken in one engagement. Starts with the audit ($1,500-$2,500), then rolls into optimization or implementation of priority fixes ($5,000-$20,000+). Typical timeline 6-14 weeks total depending on scope. Ends with documentation, training, and 60-day post-launch support.
For teams who finished implementation and want a senior MCAE architect on call. $5,000-$10,000/mo, monthly engagement, exit any month with 30 days notice. Quarterly strategic reviews, sanity-checking new initiatives, validating changes before rollout. The opposite of a monthly retainer — I step in when you specifically need me, not by default.
Book a 15-minute routing call. I will listen for 10 minutes, then tell you honestly whether you need a strategy consult, a full-cycle engagement, or just an audit to start. No upsell.
Book a 15-minute routing call →The naming has changed twice in five years. Each change confused the market. Here is the practical history that matters when you are searching for help — and why this page uses all three terms.
Salesforce acquired Pardot in 2013 (through the ExactTarget acquisition). For nine years, the product kept its original brand. Pardot built the B2B mid-market consulting ecosystem we still rely on today — Salesforce Ben, MarCloud, Sercante, the Pardot User Group community, Trailblazer Community knowledge articles. When you search "Pardot consultant" in 2026, you find practitioners with 7-10+ years on the platform. That depth matters when you are investing $30K-$100K in implementation.
In April 2022, Salesforce renamed Pardot to Marketing Cloud Account Engagement as part of the broader "MC Easy" consolidation strategy. The rename did three things: (1) repositioned the product under the Marketing Cloud umbrella for sales positioning, (2) aligned naming with Salesforce's "Account Engagement" + "Engagement Studio" terminology, (3) signaled stronger integration with Sales Cloud account-based motions. What it did not do: change the underlying product, database structure, API, or existing configurations. Same platform, new sticker.
The naming is still in transition. Salesforce documentation uses "Marketing Cloud Account Engagement" formally but defaults to "Pardot" in the URL (pi.pardot.com), the API namespace, the Trailblazer Community, and most knowledge articles. Vendor partners use both interchangeably. Your CFO sees "MCAE" on the invoice; your marketing team says "Pardot" in standups. That is normal in 2026 — and why this page uses both terms.
At Connections '25 (June 2025), Salesforce announced Marketing Cloud Next (MCN) — the Data Cloud-native, Agentforce-powered platform intended to converge B2B and B2C marketing automation. The official position is "convergence, not migration." Pardot/MCAE continues receiving updates with no announced sunset date. New feature investment increasingly flows to MCN.
For existing customers, the bridge mechanism is Account Engagement+ (AE+) — Permission Set Licenses that grant access to MCN features (Agentforce, native SMS / WhatsApp, advanced personalization, Data 360 segmentation) alongside your existing Pardot environment. This is the path most existing customers should take in 2026 — see the MCN Decision Framework for the 7-question test, and Implementation Model 03 for AE+ enablement details.
Practically, when you are searching for help with the platform in 2026, search all three terms. "Pardot consultant" returns experienced practitioners (10+ years). "MCAE consultant" returns the cohort who started after 2022. "MCN consultant" or "Marketing Cloud Next" returns the early movers from 2025+. The experienced ones have seen architectural patterns break under load — which is what you want when you are investing $30K-$100K in implementation.
The questions B2B teams ask before committing to MCAE work in 2026 — including the MCN migration question that did not exist a year ago.
Five MCAE-specific services plus two Salesforce Cloud services. Map your situation to the right next step — audit before optimization, optimization before scaling.
1-2 week diagnostic. $1,500-$2,500. Required before optimization.
Explore →Fix what the audit found. $5,000-$15,000, 3-6 weeks. Requires audit.
Explore →Greenfield, relaunch, AE+ enablement. $5K-$20K+, 4 engagement models.
Explore →Inbound, org-to-org, or platform migrations. Engagement history preserved.
Explore →Standalone scoring rebuild — intent-based, edition-appropriate, back-tested.
Explore →Pipeline architecture and forecasting that holds up under load.
Explore →Case architecture, omni-channel routing, SLA enforcement.
Explore →Before scoping any MCAE engagement, three reads worth your time:
If you're evaluating MCAE, picking an edition, debating migration to HubSpot, or running MCAE that stopped delivering — book a 15-minute discovery call. I'll listen for 10 minutes, then tell you honestly which direction makes sense. No pitch, no obligation. If your problem isn't something I solve, I'll say so.
Book a 15-minute discovery call →