The job nobody decided
The follow-up on a quote. The call that locks a date. The second message to the customer who went quiet. Almost no service company has the order of those tasks written down, or the name of the person who decides. It runs anyway, because the people doing it improvise well.
The trouble starts the day you want that work off your plate. You cannot delegate a process that was never written. Software does not infer the order your company never set down, and if you delegate it that way, what you hand over is the mess.
A coworker with email
On October 8, 2026, at a Google Cloud event, Google announced an agentic version of Gemini aimed at businesses first, before any later rollout to consumers. Thomas Kurian, the CEO of Google Cloud, said the agent can be given objectives, not just instructions: it plans the work, uses custom skills and tools, and connects to a company's internal systems. From a tasks inbox you watch it think, load skills, write code, and delegate tasks to subagents.
The part worth reading twice is a different one. The agent gets its own Workspace account with an email address. It knows organizational hierarchies, team assignments, time zones, approval requirements and calendar information. That stops being a feature list at some point. It is an onboarding document, and your company is the one that has to write it.
Where its authority stops
By default the agent picks the best model to complete the task, and a user can instead select a specific model, including Anthropic's Claude. It connects to business data and systems and works with Model Context Protocol servers. Google described flexible spending options and real-time spend caps, with no specific pricing stated and no exact launch date beyond the announcement.
The spend cap is the tell. A cap is something you put on whoever can spend. So the question stops being what the software can do and becomes which work you are willing to let it own, up to what amount, and who signs off past that line.
What changes this week
Sit down for one hour this week with whoever runs operations, and take the three jobs that eat the most time. For each one, write the order of the steps, the point where somebody has to approve, and the name of the person who approves. One page. No software yet.
What you notice by Friday is that the arguments get shorter, because the order is on paper instead of in three people's heads. And when the day comes to hand the first job over, you hand over something already decided, its authority ending where you drew the line, with everyone in the company able to see where that is.