What switching and adopting tools really costs

What we're tracking

• •How you are charged is shifting away from seats For most of the last decade, business software has been priced per seat. You count your users, you multiply by a monthly figure, and that is your bill. The model is easy to understand and easy to forecast, which is exactly why it became the default. It also has a quiet flaw: it ties what you pay to how many people have a login, not to how much value the tool actually delivers. A team of ten that barely touches a product pays more than a team of three that depends on it every hour.
• •Moving files to a new platform without losing who could see them Switching platforms is where the cost of change becomes concrete. Most teams underestimate it because they picture the files moving and stop there. The hard part is not the files. It is the permissions attached to them: who could open each document, who could edit it, who was explicitly kept out. Lose that structure in a migration and you have either locked people out of work they need or, worse, exposed documents that were meant to stay private.
• •Bringing conversation history across, not just files Documents are only half of a working platform. The other half is the running conversation: the channels, the threads, the context that explains why a decision was made. Google announced data import for Microsoft Teams alongside the OneDrive one, and it used almost identical language: "For enterprise organizations, migrating communication history and collaboration channels to a new platform can feel daunting and risk interrupting daily business operations." [3]
• •Proving an AI feature works before you rely on it The day's clearest reminder about AI came not from a product launch but from an engineering account of how to test one. GitHub published its lessons from evaluating large language models before putting them into production, framed around a specific job: "These are the lessons we learned evaluating LLMs for real-world secret scanning." [4] The detail that it was real-world secret scanning, and not a generic benchmark, is the point. The model was measured against a concrete task with a clear definition of right and wrong.
• •Deciding who can see who is in the room The quietest item of the day is a control, not a capability. Google Chat now lets space owners and managers restrict who can view the full member list of a space. In Google's own words: "Space owners and managers can now control who can view the full list of members in a Google Chat space, providing enhanced privacy and administrative control for sensitive, large-scale, or external collaboration spaces." [5]