Encharge vs LaunchNotes
Side-by-side trajectory, velocity, and editorial themes.
Encharge grinds through reliability and security fixes, with an MCP teased next
Encharge is in a steady maintenance-and-hardening phase. The two most recent monthly updates are dominated by fixes — multi-select fields across forms and segments, HubSpot date sync, sending reliability — plus security work: signups now require email confirmation, form notifications only send from verified senders, and stronger bot and spam protection. It's an email-automation product tightening its foundations rather than expanding surface area.
The arc is deliberate stability: quarter after quarter of email-editor, forms, flows, and integration fixes, with incremental additions like a marketing-consent field and smoother sending autoscaling. The one forward signal is an Encharge MCP now in testing — the first hint of an agent-facing layer on top of the existing automation engine — alongside a Shopify connector app in progress.
The Encharge MCP is the most likely next headline; expect it to ship out of testing, with the in-progress Shopify connector close behind. Otherwise the cadence points to continued reliability and integration work.
LaunchNotes leans into AI authoring and agent access while hardening enterprise controls.
LaunchNotes is a product-update and changelog communication platform, and its recent releases split cleanly between AI-assisted authoring and enterprise governance. On the authoring side it now drafts from Jira and Confluence, unifies those paths in Smart Draft, and exposes an MCP server so assistants can operate it directly. On the governance side it has added Secure Content asset protection and finer-grained publishing permissions.
The direction is unmistakably AI-first authoring paired with enterprise readiness. Each release either shortens the path from scattered source material — Jira, Confluence, recordings — to a published announcement, or tightens who can publish and who can see what. The MCP server marks a shift from AI drafting on the user's behalf to assistants acting against the platform directly.
Expect more source connectors and deeper agent surface built on top of the MCP server, paired with continued permissions and audit work aimed at larger teams.
See more alternatives to Encharge →
See more alternatives to LaunchNotes →