Control over your data and what a stalled tool is worth

· 5 min read
AI-generated image: Control over your data and what a stalled tool is worth
AI-generated image

Most of what the large productivity suites shipped today points one way: control over data — who can read it, where it is kept, and what record survives a conversation. Underneath all of it sits a market question made concrete by a single sale: what is a software tool actually worth once it stops growing.

For a business picking tools, both ends matter. The governance work decides how much trouble a tool saves you with auditors and regulators. The market story decides how much faith you should put in a vendor staying the course. We cover both below, in the order a buyer should weigh them. For the running thread across the week, see the previous briefing.

A price for a tool that has stopped growing

When you choose software, you are betting on two things at once: that the tool fits now, and that whoever owns it keeps investing in it. Acquisitions reset the second bet. A buyer does not pay for the past; they pay a multiple of current revenue, and that multiple collapses when growth flattens. A profitable, widely used product can still change hands for a fraction of what it once cost, and new owners may run it to harvest cash rather than expand it.

Today gave that abstraction a number. Intuit paid $12 billion for Mailchimp in 2021 [1], and has now agreed to sell it for $3.68 billion — roughly 2.9 times revenue at zero growth. The lesson for a buyer is not about any one product. It is that scale and profit do not guarantee continued investment, and that a tool deep in your stack can quietly pass to an owner with a different plan. When you commit to a platform, check that your data exports cleanly and that your core workflow would survive a change of ownership.

Keeping a record of conversations you do not fully own

If your business sits in a regulated field — finance, health, law, public money — you are usually required to retain messages, place legal holds, and be able to search and export them on demand. This is records retention and eDiscovery. The hard part is coverage. A compliance system that captures internal chat but misses the rooms where you talk with outside parties leaves a gap exactly where disputes tend to start.

Google is narrowing one such gap. It is expanding Google Vault support in Google Chat to give organisations more consistent visibility and help support their compliance requirements [2], extending retention, holds, search and export to external spaces and group conversations. The trade-off is familiar: every surface you bring under retention is another surface an administrator has to govern and another store of messages that now lives on under policy. For a business, the gain is that cross-company chat stops being an untracked blind spot. The cost is a slightly larger compliance footprint to manage.

Where your workflow data is stored and processed

Data residency is the question of which country or region your data physically sits in, both at rest and while it is being processed. For many organisations this is not a preference but a legal line — contracts, national law, or a customer's own policy may forbid data leaving a defined area. The catch is that automation tools quietly move data around as they run, so a workflow builder can undo a residency promise that the rest of your suite keeps.

Google has closed part of that hole. Google Workspace Studio now supports Data Regions, giving organisations greater governance over where their workflow data is stored at rest and processed in use [3]. For a buyer comparing automation platforms, this is the kind of detail that decides eligibility rather than preference. If you operate under residency rules, a builder that respects your region is usable and one that does not is simply off the table, however capable it is otherwise. It is worth asking any automation vendor the same plain question: where does my data go while a workflow runs.

Encryption you can still work inside

Client-side encryption means the content is scrambled before it reaches the provider, so the provider cannot read it and the keys stay under your control. The long-standing cost of that guarantee has been collaboration. If no one but you holds the key, live co-editing is awkward, because the usual trick of the server merging everyone's changes assumes the server can see the text.

Google is chipping at that limitation. It has made real-time collaboration on client-side encrypted (CSE) Google Docs available in beta [4]. The significance for a business is that the old choice — strong confidentiality or smooth teamwork, pick one — softens. You may be able to keep documents indecipherable to the provider and still have several people edit them at once. The trade-off does not vanish: client-side encryption puts key management on you, and losing keys means losing access. But it moves the decision from "can we even work this way" to "are we set up to manage the keys", which is a more answerable question.

Short breaks built into the calendar

Not every useful change is about governance. Meeting hygiene is a smaller lever that quietly shapes a team's day. When meetings are booked wall to wall, there is no time to move between rooms, take notes, or simply pause, and the cost shows up as fatigue and meetings that start late.

Google is addressing this at the default level. Its reasoning is blunt: back-to-back meetings can leave no time for a break in your day [5]. It is expanding the "Speedy meetings" setting in Google Calendar so new meetings can carry a default five-minute buffer. This is a minor change with a real effect, because a default applied across an organisation changes behaviour far more reliably than asking people to shorten meetings by hand. For a business, the point is that scheduling defaults are a policy, and small ones compound.

What to take from the day

The connecting thread is custody. Three of today's updates are about keeping control of data as it spreads across more surfaces — outside chat, automation runs, and encrypted documents — and the fourth is about keeping control of attention. The Mailchimp sale is the reminder that sits underneath all of it: control includes an exit. A tool is only as safe as your ability to leave it with your data intact if its owner changes direction. If you are weighing whether to consolidate tools at all, our note on replacing several business tools with one walks through the same trade-off from the buyer's side. Pick for the work in front of you, but check the exits before you commit.

Sources

  1. [1] Intuit Sells Mailchimp for $3.68 Billion, 30 Cents on the Dollar: 2.9x Revenue, 0% Growth, and the Biggest Deal Yet for Bending Spoons — SaaStr
  2. [2] Expanded Google Vault support for external spaces and group conversations in Google Chat — Google Workspace
  3. [3] Google Workspace Studio support for Data Regions is now generally available — Google Workspace
  4. [4] Now available in beta: Collaborate in real-time on client-side encrypted (CSE) Google Docs — Google Workspace
  5. [5] Google Workspace Weekly Recap - November 20, 2026 — Google Workspace

Want a person to look at your website and social pages? Get a free check-up, written by a real person within 2 business days.

The 360REV newsletter

What is actually changing across productivity software, written for operators and cited to sources. No more than one email a day.

Double opt-in — we send one confirmation link and nothing else until you click it. Unsubscribe from any edition. We never sell or share your address.