ConvertKit vs Lytics
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.
Lytics retires the legacy audience builder, ships zero-copy Salesforce Data Cloud sync, and pushes integrations weekly.
Lytics is a CDP shipping at a steady weekly cadence. Recent work cuts across three vectors: a forced migration off the legacy audience builder (sunset May 4, 2026) toward a redesigned builder with geolocation rules; heavy expansion of cloud-warehouse and ad-platform integrations (Salesforce Data Cloud, The Trade Desk, Microsoft UET, Pushly, Algolia, GCS); and admin-side governance — naming conventions, metric threshold alerts, easier OAuth recovery.
Two arcs are visible. First, the integration catalog is being deepened toward server-side conversion APIs and zero-copy data movement — Salesforce Data Cloud's bidirectional sync with zero-copy bulk via GCS is the architecturally interesting move and likely a template for what's next. Second, the platform itself is being made more legible to large operators: naming conventions, threshold alerts, and reconnect-in-place auth all target customers running Lytics at scale rather than acquiring net-new ones.
Expect the next quarter to bring more zero-copy/streaming export jobs patterned after the Salesforce Data Cloud blueprint (Snowflake or Databricks are the obvious next targets), plus additional governance features — likely per-team audience permissions or audit-log enhancements — as the natural follow-on to naming conventions.
See more alternatives to ConvertKit →
See more alternatives to Lytics →