From $12B to $3.68B: The New Logic of SaaS Consolidation
When Your SaaS Vendor Changes Hands, What Can You Take With You?
The real test of a SaaS architecture isn’t whether you can integrate a new tool in an afternoon. It’s whether you can replace it without losing the business knowledge you’ve accumulated over five years.
Bending Spoons has agreed to buy Mailchimp from Intuit for $3.68 billion, roughly five years after Intuit paid about $12 billion for it. The proposed sale is expected to close in early 2027, subject to regulatory approvals and other conditions.
The price gap makes for a striking headline, but it doesn’t tell a CTO what to do on Monday morning. The ownership change raises a more useful question: Which parts of your business can a vendor decision force you to redesign?
A data export is not a recovery plan
Take a routine customer onboarding sequence. The contact list tells you who signed up. It may not tell you which customers have already received their welcome message, which ones have withdrawn consent, or which ones are midway through a sequence. If that context lives only in the platform, a successful export can still lead to a failed migration. You might reach people who opted out or restart journeys that customers already completed.
That’s the difference between moving records and preserving business state. It applies just as much to a support queue or an approval workflow as it does to email. The longer a team uses a SaaS product, the more decisions it encodes in filters, rules, templates and exceptions. Some of those decisions are documented. Many are known only to the person who configured them three years ago.
Own the decisions you can’t afford to lose
I don’t think the answer is to build everything in-house. A small team shouldn’t spend six months building a generic workflow engine to insure against a hypothetical acquisition. The better architectural choice is to decide, explicitly, what the vendor can manage on your behalf and what your business must be able to reconstruct independently.
For a customer communications system, that might mean keeping an authoritative record of customer identity and consent outside the delivery platform, while letting the vendor handle scheduling and delivery. If an automation is central to revenue or compliance, document its rules and make sure you can tell where each customer is in the process. If it’s a low-stakes monthly newsletter, a reliable export and a short runbook may be enough.
There’s a cost on both sides. Duplicating every workflow creates maintenance work and two places for rules to drift. Leaving every rule inside the platform makes a future migration a reverse-engineering project. The right boundary depends on what would happen to customers if the workflow stopped tomorrow.
Put portability on the renewal agenda
Before renewing a critical SaaS contract, I’d ask the team to do three things:
- Review what actually comes out. Export a representative dataset and check whether it includes the timestamps, identifiers and consent history you would need to resume operations.
- Rehearse one critical workflow. In a test environment, rebuild it from the export and documentation. Measure how long it takes and note which steps depend on someone remembering how the original was configured.
- Price the exit alongside the subscription. Include engineering time, any period of running both systems, and the operational cost of mistakes during a cutover. Review contractual access to data after termination, too.
A change of ownership isn’t a reason to migrate by default. It’s a reason to find out whether staying is still a choice. The strongest vendor relationships are the ones you renew because they work for your business, not because leaving would mean forgetting how your business works.
About the Author: Sanjeev Sarma is the Founder Director and Chief Software Architect at Webx Technologies. With a core focus on Generative AI integration, Cloud-Native Scalability, and Enterprise Software Architecture, he has spent over two decades driving digital transformation across Northeast India and beyond. Beyond his corporate leadership, Sanjeev is deeply invested in shaping the future of the IT industry. He serves as an Industry Expert on the Board of Studies for Assam Don Bosco University’s School of Technology, advises state technology committees, and actively mentors emerging tech startups at STPI. He brings a unique, dual perspective of high-level enterprise execution and future-ready academic curriculum development.