ConvertKit vs Pardot
Side-by-side trajectory, velocity, and editorial themes.
Kit ships an MCP server so AI tools can run email campaigns, while the rest of the surface gets quiet polish.
The headline release is Kit MCP in beta — an MCP server that lets Claude, ChatGPT, Cursor, or any MCP-compatible client manage Kit lists, tags, broadcasts, and sequences from natural-language prompts. Around it, the team shipped routine UX work: searchable Rules and Visual Automations libraries, a typo-catcher on signup forms, a unified Recommendations view, and Shopify sync added to the Free plan.
Kit is making a serious bet that creators will manage their email programs through external AI assistants rather than (or alongside) the Kit dashboard. The MCP server is a meaningful surface move; everything else in this batch reads as housekeeping intended to make individual primitives more discoverable for both humans and agents.
Expect MCP coverage to widen from analysis/tagging to outbound campaign creation by GA, and the Shopify-on-Free move to be repeated for Stripe or Gumroad to widen the creator-commerce funnel.
Pardot's Summer '26 release shows the bridge to Marketing Cloud Next is being built feature by feature.
The substantive signal in this window is the Salesforce Summer '26 release for Marketing Cloud Account Engagement (the artist formerly known as Pardot): consent data now syncs between Account Engagement and Marketing Cloud Next via static public list mapping, plus expanded email capabilities (CC recipients, archiving) inside Marketing Cloud Next. The rest of the captured feed is broken scrapes of Salesforce help pages - mostly CSS errors and JavaScript exceptions.
Salesforce is gradually wiring Pardot into Marketing Cloud Next rather than sunsetting it abruptly - consent sync and shared email primitives are the kind of integrations that smooth a long-running migration. Expect each seasonal release to add another shared object (subscriptions, audiences, journeys, attribution) until the practical difference between the two products narrows. The ingestion problem on the source side is severe; most product-relevant context is buried under broken page captures.
Next likely beats: shared audience and segmentation primitives between Account Engagement and Marketing Cloud Next, plus journey-stitching across both. On data quality, the Salesforce help center scraping needs a different ingestion approach - likely the official release-notes RSS or PDF rather than the JS-rendered help portal.
See more alternatives to ConvertKit →
See more alternatives to Pardot →