The day the tools changed hands and changed shape

What we're tracking

• •A collaboration tool changes owners When you adopt a tool, you are making a bet on the people who decide its roadmap, its pricing, and the fate of your data. An acquisition quietly rewrites that bet. The product you chose may be run by a different company with different priorities within a quarter, and you will not have been asked.
• •A file service starts feeding an outside AI The second thread is about where your documents go once you let an AI help with them. Connecting a file store to an AI assistant is convenient — the assistant can answer from the context of your actual work rather than from generic knowledge. It also means your files, or representations of them, now travel to a second system with its own retention and access rules.
• •A spreadsheet raises its ceiling Most businesses run far more on spreadsheets than they admit. The spreadsheet is the first tool for almost every job, and it keeps working right up until the day the dataset is too large, the formulas too tangled, or the shared file too contested. A higher capacity ceiling delays that day without removing it.
• •Governance moves into the admin console As more work passes through AI features, the question of who can share what, and with whom, stops being a niche concern. The useful development is when that control becomes granular and lives where an administrator can actually set it, rather than being a single on-or-off switch.
• •Checking what the AI wrote The more an assistant generates on your behalf, the more your real job becomes reviewing its output rather than producing it. That shift is easy to underrate. GitHub notes that checking agent-generated code "usually means hopping between tabs" [5] — a small friction that, repeated hundreds of times a day, quietly determines whether a team actually reviews what the AI produced or just accepts it.
• •Reliability is a feature, and vendors are starting to say so Finally, a reminder that availability is part of what you buy. GitHub's monthly report states plainly that "in August, we experienced five incidents that resulted in degraded performance across GitHub services" [6]. The number is less important than the habit: a vendor that publishes its incidents gives you something to judge, which is more than you get from a vendor that stays quiet.