Daily Briefing

The AI bill at the top, finished work at the bottom

Good morning. The announcements worth your attention today split neatly into two layers. At the top, the companies that rent out computing are describing spending on a scale that will eventually show up in what you pay; at the bottom, the tools you open every morning are quietly learning to produce finished work rather than just suggestions.

That gap is the story. It is easy to read the trillion-dollar headlines and conclude that nothing has changed for a small team choosing software. The opposite is true. The infrastructure numbers tell you where pricing and lock-in are heading, and the feature releases tell you what your staff will actually be doing next quarter. A sensible buyer reads both.

Read the full briefing →

What we're tracking

Files you can edit inside the assistant Google Workspace said it is adding ways to create, preview, and edit files and code directly inside the Gemini app, including the ability to expand to full screen and highlight text to ask questions [1]. This is a smaller change than it looks, and a more important one.
There is no single AI strategy, even inside one company Salesforce published a piece making a point that is easy to miss in a year of confident pronouncements: that AI is still jagged, and that your enterprise strategy should be jagged too [2].
The bill behind the AI boom At the infrastructure layer, Amazon's chief executive said on Thursday that Amazon wants to be the king of AI cloud computing and become the first $1 trillion revenue business, and that getting there means continuing to spend heavily on capital expenditure [3].
What booming revenue cost in cash The same set of results carried a second number worth holding onto. Amazon reported strong cloud revenue but otherwise missed expectations, and the report included negative free cash flow of $2.4 billion [4].
Automation as the layer that connects the rest Finally, Zapier published a guide to using Gemini through its integration, opening by noting that anyone who lives in the Google ecosystem has probably used Gemini for a quick draft or a fast answer [5]. The piece itself is practical, but the category it sits in is the one that ties today's two layers together.
What to take from the day The thread running through all five items is the distance between what is being spent and what is being shipped. The spending is enormous and will, in time, reach your invoice. The shipping is modest and immediately useful: a file you can edit in place, an integration you can wire up this afternoon. A business choosing tools this week should let the small changes guide what it adopts and let the large numbers guide how carefully it keeps its data its own. We covered a similar split in yesterday's briefing, and the pattern is holding.

From the blog

Why every customer message belongs in one inbox
A shared inbox pulls chat, email, forms, social messages and reviews into one place your whole team works from. Here is what that changes about the work, and how to tell whether your business has outgrown scattered tools.
20 October 2026
How to keep a team of five aligned without meetings
A team of five does not need daily meetings to stay aligned. It needs a short list of things written down in one place everyone can reach. Here is what to write, and where it should live.
12 October 2026
What to do about a customer who leaves
A churn rate tells you how many customers left. It cannot tell you why. Here is how to capture the reason, one departure at a time, so the number becomes something you can act on.
11 October 2026

Sources

Share this issue

Facebook · X · Reddit · LinkedIn · WhatsApp · Email · Bluesky

Every briefing is on the site the morning it is written, with the announcement behind each item. All briefings