
Mailchimp sold: Bending Spoons buys the platform from Intuit
Intuit has confirmed the sale of Mailchimp to Bending Spoons for $3.68 billion, in a cash-and-stock deal expected to close in early 2027. The change of owner raises questions about pricing, deliverability and the tooling choices of email teams.
Siècle Digital reports that Intuit has agreed to sell Mailchimp to Bending Spoons for $3.68 billion. The transaction, confirmed by the group, involves both cash and shares, and is expected to be finalised in early 2027. The announcement does not specify how the platform's roadmap, staff or pricing will be handled during the transition.
A different owner, a different playbook
Bending Spoons is known in the industry for acquiring consumer software and consumer apps and running them with a tight operational model. That is general context, not a detail from the announcement: the release reported by Siècle Digital says nothing about the post-acquisition plan for Mailchimp.
For marketing teams, the practical question is not who signs the cheque. It is whether email keeps its place as a predictable, cheap channel for owned audience, or whether it becomes a line item that gets renegotiated. Mailchimp has long been a default entry point for small and mid-sized businesses building a first list. Any shift in packaging or pricing hits those teams first.
What a team can check this week
You do not need the deal to close to reduce your exposure to one vendor. The months before a transition are a good time to audit what you actually depend on.
- List the automations, forms and integrations that run through your email provider, and note which ones have no equivalent elsewhere.
- Compare your current send volume and contact count with what you actually use; unused contacts are pure cost.
- Export a clean copy of your lists and suppressed addresses so you own the asset independently of the tool.
- Review deliverability metrics (bounce and complaint rates, inbox placement) now, so you have a baseline if results move later.
None of this requires migrating. It requires knowing your switching cost before someone else decides it for you.
Email sits inside a wider funnel
Mailchimp's value to a business is rarely the email editor. It is the relationship between the list, the signup flow, the checkout and the retention loop. When ownership of the tool changes, the parts of the funnel that feed it become more important, because they are the parts you control.
That is the angle worth watching: not the valuation, but whether the incentives of the new owner push toward higher per-contact pricing, consolidation into bundles, or tighter limits on the free tier that many early-stage companies rely on. The report does not say. Until the deal closes and the terms are published, treat any prediction as speculation.
What is certain is the timeline: completion expected in early 2027, with a mix of cash and shares. That leaves a window in which teams can document their setup, benchmark costs per subscriber, and decide which parts of their email programme would survive a change of provider. Doing that now is cheaper than doing it under pressure.
Also worth reading
-
A weekend of 403 errors: catching SEO regressions early
A French SEO publication reports that a client's e-commerce site returned 403 errors over a weekend, with around forty pages dropping out of Google by Monday. The case highlights how a release or server change can quietly undo months of indexing work.
-
Google adds brand filter and multimodal data to Search Analytics API
Google announced on 16 November 2026 that the Search Analytics API now includes three features already available in the Search Console Performance report. The brand filter only applies to eligible properties, which raises questions for teams that automate their reporting.
-
CDN migration: why Googlebot hits your origin server harder
Abondance reports that faster CDN response times can lead Google's robots to raise a site's crawl capacity limit, increasing crawl volume soon after a migration. Because a CDN starts with an empty cache, each first request on a URL goes back to the origin server.


