Who holds your work, and what it costs to leave

Most software decisions are really decisions about where your work will live. The announcements of the day pull in two directions at once: some vendors lowered the cost of moving work into their system, while others grew larger by buying the tools your work already sits inside.

That tension is worth holding onto when you choose a tool. The question is never only what a product does today. It is what happens to the hours you pour into it if the vendor is acquired, if its priorities shift, or if you simply decide a year from now that something else fits better. A tool you can leave is a different kind of commitment from one you cannot.

Consolidation changes what you are buying into

The clearest signal of the day came from the deal side. Bending Spoons announced an agreement to acquire Miro, and had agreed to buy Airtable five weeks earlier [1]. Both are widely used B2B products — a whiteboard and a flexible database that a lot of small teams run real operations on.

An acquisition is not, by itself, bad news for a customer. But it does change what you are buying into. When a tool you depend on becomes part of a larger portfolio, the people setting its roadmap change, and so can the pricing model, the support, and the pace of new work. None of that is visible on the pricing page you read when you signed up.

The practical lesson is not to avoid acquired products. It is to know, before you commit, how much of your operation would be stranded if the product you rely on changed hands and then changed shape. If the answer is "a lot, and I could not get it out," that is a cost you are carrying whether or not you have named it. This is the same reasoning behind being able to export your data on any ordinary day: the point of an export is not that you plan to leave, but that you could.

Moving in is getting cheaper — moving out is the harder number

On the same day, Google Workspace made general the ability for small businesses to bring their people and their data across from Microsoft during setup [2]. The announcement frames it as a simplified import tool used while a business is first setting up Workspace.

This is genuinely useful. The friction of switching office suites has always been less about the software and more about the migration — the accounts, the files, the mailboxes. Lowering that friction means more businesses can actually act on a decision they had already made in principle.

But notice the direction. A smooth path *in* is not the same as a smooth path *out*, and vendors have every reason to invest in the first more than the second. When you evaluate any tool, it is worth asking the question the import announcement answers in only one direction: if I later want to go the other way, what does that look like, and does the tool give me my data in a form another system can read? The ease of arriving tells you nothing about the ease of leaving. Both matter, and only one tends to get marketed.

When your chat tool becomes a work surface

Slack introduced Surfaces, which it describes as a way to "turn Slack conversations into live dashboards, reports, and decks" [3]. The idea is that the place where your team already talks also becomes the place where team data is shown and acted on.

There is a real convenience here. Fewer tools to open, and information sitting next to the conversation about it. The trade-off is the one worth thinking through before you build on it: the more of your reporting and your interfaces live inside one communication tool, the more that tool holds. A dashboard built inside a chat product is convenient precisely because it is bound to that product. That binding is the feature and the cost at the same time.

This is the broader pattern behind why your tools often do not talk to each other: work tends to accumulate inside whichever surface made it easiest to create, and it does not always come back out cleanly. Convenience in the moment and portability later are often in direct tension, and a team that never weighs them ends up choosing by default.

AI that sits beside your other windows

Google also launched a Gemini desktop app for Windows 10 and 11 [4]. The pitch is an assistant that runs alongside the tools you already use, rather than something you have to switch away to.

The shift here is about placement. An assistant in a browser tab is a destination you visit. An assistant on the desktop is something that sits beside your work and is available without a context switch. For a business, the deciding question is less "is the model good" and more "where does it fit in how my people already work, and what does it see." An assistant that lives next to everything else is more useful day to day, and it also has a wider view of what you are doing. Both are consequences of the same design choice, and it is fair to weigh them together.

Automation starts with writing the work down

GitHub published an account of automating its APAC marketing team's events, from planning through follow-up, and opened with a line worth keeping: "If you can write down how you do your work, you can automate it" [5].

That sentence is the useful part for most readers, independent of the tooling around it. Before any automation is worth building, the work has to be legible — a sequence someone could follow written down in plain steps. Teams that cannot describe their process cannot automate it, and often discover, in trying to write it down, that the process was never as settled as they assumed. The writing-down is most of the value. The automation is what you do once the steps hold still.

What to take from the day

Read together, these announcements are all about the same thing from different angles: how bound your work is to the tool that holds it. Consolidation raises the stakes of that binding, a good import tool lowers the cost of one direction of travel, and every convenience that keeps work inside a single surface is also a small commitment to that surface. When you choose software, choose it the way you would sign any agreement you might need to end — knowing what you could carry out with you, and what you could not.