Email industry brief: MailerLite's free-plan squeeze, Klaviyo MCP campaign staging, and beehiiv's research playbook (2026)

Scope

This brief covers developments published or materially updated from August 7 at 10:16 through August 14 at 10:15, local channel time (+02:00). The useful pattern this week is operational: small senders need to inspect plan limits before they build, AI workflows are moving into campaign assembly, and newsletter growth work is becoming a repeatable research process.

1. MailerLite's free plan is a smaller operating environment

An August 7 update from InboxArmy says MailerLite's free plan moved to 250 subscribers and 2,500 emails per month from June 16. It says the related feature limits — three automations, three forms, and one landing page — were scheduled for enforcement from August 13. 1

MailerLite's current pricing page confirms the 250-subscriber and 2,500-email caps. It also says sending is locked when active subscribers exceed 250 until the account upgrades or removes subscribers. The page does not state the August 13 date or confirm the feature-cap enforcement, so treat that part as a reported change to verify inside an account rather than as a dated first-party announcement. 2

Why it matters

A free-tier comparison now needs more than subscriber count and monthly send volume. A newsletter may fit under both caps and still hit a workflow, form, or landing-page ceiling. That changes the migration question for small teams: count the assets they actively use, not just the contacts they store.

Checks before switching or staying

Inventory active automations, signup forms, and landing pages before August traffic or a platform migration.
Check whether the account's current limits match the public pricing page and the reported August 13 enforcement date.
Keep a paid-plan estimate beside the free-plan comparison; a low contact cap can become a sending outage before it becomes a large invoice.

2. Klaviyo's MCP examples move AI closer to campaign assembly

Klaviyo published a case-led guide on August 11 describing nine use cases built by a non-technical team running Klaviyo for 15 clients through Claude Code and Klaviyo's Model Context Protocol (MCP) server. The examples cover content-calendar analysis, A/B-test reporting, pop-up funnel reporting, double-send detection, and staging drag-and-drop campaigns from Figma. 3

The most consequential step is the staging workflow. Klaviyo says the team can export from Figma, build drag-and-drop templates, create a campaign, add segments, and schedule it; the same page says this reduced roughly 30 minutes of hands-on work to about five minutes of quality assurance. Those are company-reported results from one agency workflow, not a benchmark. The underlying Figma path requires a connected Klaviyo account with permission to manage images. 4

Why it matters

The shift is from AI writing copy to AI-assisted campaign operations. That can remove export, spreadsheet, and setup work, but it also moves audience selection, exclusions, rendering, and scheduling into a faster path. Klaviyo's examples still describe a team reviewing the output; they do not establish unattended sending.

Checks before testing

Keep campaign creation and scheduling behind a human approval step.
Test segment membership, suppression rules, links, rendering, and send-time settings on a small audience.
Run a double-send audit across overlapping flows before trusting automated assembly.
Record which permissions the MCP connection and the Figma workflow actually receive.

A beehiiv guide published on August 12 recommends identifying five to ten direct and adjacent newsletters, subscribing for two to four weeks, and recording sign-up flows, send dates, subject lines, formats, calls to action, and revenue models. It suggests scoring comparable criteria from 1 to 5 and keeping a matrix of frequency, format, monetization, growth tactics, unique angle, and gaps. 5

This is strategy guidance rather than a product release, but it gives newsletter teams a concrete alternative to vague competitor watching. The dedicated inbox or label matters: without a fixed observation window, teams tend to remember the loudest examples and mistake them for the market.

Checks before copying a tactic

Separate raw observations — send date, subject line, layout — from your interpretation of why a newsletter works.
Compare newsletters serving the same reader before borrowing a format from an adjacent category.
Turn one verified gap into a testable recurring segment, then revisit the matrix quarterly or after a major competitor change.

What to inspect next

Before the next campaign, run three small audits: the plan audit for subscriber, send, and asset limits; the AI audit for permissions and approval boundaries; and the competitor audit for a defined two-to-four-week observation set. The sources point to different decisions, but they all reduce the same failure mode: scaling a workflow before its constraints are visible.