360REV Newsletter
Daily Briefing
When software stops suggesting and starts acting
Good morning. The announcements worth your attention today circle a single shift. The products are moving from telling you things to doing things, and the hard questions are no longer about output. They are about how much you let software act on its own, what that costs, and which work still belongs to a person.
That shift changes how you should read a demo. A tool that drafts a reply and a tool that sends it are not the same purchase, even when the screen looks identical. The sections below take the five items that bear most on a tool choice, in order of how much they should affect yours. We build around the same question at 360REV, so treat the framing here as a lens rather than a pitch.
What we're tracking
- How much an AI should decide on its own Start with the question that sits under everything else. When software only answers, a wrong answer costs you a moment. When software acts, a wrong action costs you whatever it touched. Zapier put the problem plainly: any product that does things, not just says things, runs into the same decision problem sooner or later [1].
- The bill arrives even as usage climbs The second item is a reality check on the first. TechCrunch, reporting on spending data from Ramp, noted that AI usage keeps climbing while spending has stalled [2]. The report ties this to price cuts and to larger buyers getting better at cost control.
- What AI agents actually changed at one company The third item gives you numbers rather than theory. SaaStr summarised what Vercel's COO reported about running AI agents in production: the company took ten sales development reps down to one, built a support agent in-house in two months, and now handles most support cases with AI. Notably, the team did not deploy blind. They ran the AI sales agent in shadow mode for six weeks first [3].
- Code is cheap, the judgement around it is not GitHub's guide to agentic engineering makes a point that generalises past software teams. Its framing is blunt: writing code got faster, and the work around it did not [4]. The post walks through planning, writing, reviewing changes and investigating production issues with Copilot, and is explicit that some of that work still needs your judgement.
- Decisions in milliseconds The last item narrows the lens to one capability. Salesforce announced a new version of its decision model, Koa Decisions, that handles single-step decisions in milliseconds [5].
- The thread, pulled tight Read together, the five items tell one story. Tools are crossing from advice to action, and that crossing moves the risk, the cost and the required judgement onto you. The buying questions follow from that. Where does the autonomy line sit, and can you move it. Is the spend metered to the work. Was the tool proven in shadow before it ran live. Does it connect to the rest of your stack. And is the speed it sells you a speed your decisions actually need. For the previous day's read, see our 5 November briefing.
From the blog
What a shared team inbox is and whether you need one
A plain explanation of what a shared team inbox does, how it changes the way a team handles messages, and the signs that tell you it is time to adopt one.
How to get every WordPress form lead into one inbox
A practical way to make every entry from every WordPress form reach one place you answer from, without rebuilding the site, changing the theme, or touching the forms that already work.
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.
Sources
- How much should an AI decide without asking you first? Zapier
- Ramp data shows AI spending stalling just as Anthropic nears its IPO TechCrunch
- Top 5 Learnings from Vercel’s COO: 10 SDRs Down to 1, a $5K-a-Year Lead Agent, and 93% of Support Cases Handled by AI SaaStr
- Beyond code generation: A developer’s guide to agentic engineering GitHub
- Less Reasoning. More Doing. Meet Koa Decisions. Salesforce
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