AI becomes a cost to manage and a workflow to connect

What we're tracking

• •Know what your AI habit costs before you standardise on anything Most companies have already bought AI without deciding to. It arrives one seat at a time, on personal cards and expense claims, because an individual found a tool that helped and did not wait for a policy. That is how you end up with a dozen overlapping subscriptions and no single view of what any of them earn back. In a report today, Rippling's Parker Conrad described one employee using an AI assistant to plan around their calendar and email at a run rate of thirty thousand dollars a year for a single person [1].
• •Model choice is becoming a procurement question, not a technical one For years, picking an AI coding tool meant picking a model, and the two were the same decision. That is loosening. GitHub published results today for its Copilot agentic harness, describing strong performance across several benchmarks together with token efficiency while keeping the ability to choose among more than twenty models [2].
• •Your content is only useful where your AI can reach it The value of a document is not in the file. It is in whether the person, or now the assistant, doing the work can get to it at the moment they need it. Content that lives in one system and AI that lives in another means someone spends their day copying between the two. Dropbox announced today three integrations that connect its stored content directly to Claude, describing them as a way to close the gap between teams, their content, and the AI they use [3].
• •Shipping fast is a sequence you can copy, not a feature you can buy Speed of delivery is often admired and rarely understood. At SaaStr, the story today was that Booking.com for Business built a free expense product in six weeks [4]. The obvious reading is to want the tool. The more useful reading is the one the write-up insists on: the thing worth copying is the sequence that produced the tool, not the tool itself.
• •Agents that do real work, not agents in a demo The gap between an agent that demonstrates well and one that carries a real workload is wide, and it is where most disappointment lives. At SaaStr AI, Replit's Amjad Masad reacted on stage to the agents the conference runs its own operations on, described as the actual agents doing the actual work rather than a demo deck [5].