Kit (formerly ConvertKit) vs Stensul
Side-by-side trajectory, velocity, and editorial themes.
Kit pushes past email tooling toward audience intelligence and AI-tool access.
Kit (formerly ConvertKit) is layering two new capabilities on top of its email and automation core: subscriber intelligence and AI-tool integration. Alongside those, it shipped a navigation redesign, a rebuilt landing page editor, and a rename of Creator profile to Newsletter site. The base product keeps getting incremental search and editor polish while the headline bets are data and AI.
The direction is from send-and-automate toward understand-your-audience and operate-Kit-from-anywhere. Subscriber Signals adds an audience data layer that competes with standalone enrichment tools, while the Kit MCP exposes the platform to external AI assistants. Together they reposition Kit as creator infrastructure rather than just an email sender.
Expect Subscriber Signals to move from early access toward general availability and the MCP to graduate from beta with broader write actions across lists, sequences, and broadcasts.
Stensul is betting its roadmap on governing AI-generated marketing content before it ships.
Stensul sells a governance layer that sits between AI-assisted content creation and the send platforms marketers already run, chiefly Salesforce Marketing Cloud and Pardot. Its recent moves — an MCP server, an Accessibility QA agent, and now a July release spanning Figma, WRITER, and Salesforce Marketing Cloud Next — all push one thesis: generation is solved, approval and compliance are the bottleneck. The blog cadence leans heavily on regulatory-risk thought leadership (FTC, FDA, SEC, EU AI Act), which doubles as demand-gen for that positioning rather than reflecting shipped product.
Stensul is expanding from an email-creation tool into a control plane for AI content across more surfaces — first email, now design via Figma and AI writing via WRITER — with governance 'agents' like Accessibility QA as a repeatable product primitive. The MCP server signals it wants to be the compliance checkpoint wherever generation happens rather than a destination app. Expect the 'Governed Creation' framing to keep absorbing adjacent creation tools instead of competing on generation itself.
The next move is likely more Governance Agents (brand, regulatory, localization checks) and broader MCP coverage beyond email, extending the same approve-before-send gate to the newly added Figma and WRITER surfaces.
See more alternatives to Kit (formerly ConvertKit) →
See more alternatives to Stensul →