360REV Newsletter
Daily Briefing
Permissions, provenance and the price of go-to-market software
Good morning. Two threads ran side by side today. One was about the money underneath AI, where acquisition prices and infrastructure spending are being questioned out loud. The other was about small, concrete controls arriving inside the tools businesses already run: who can see what, and how you check an AI's work before you trust it.
For anyone choosing software this week, that split is the useful lens. The headline deals tell you where the market is heading and what it will cost. The feature notes tell you what will change on a Tuesday morning for the people who actually use the product. Both matter, and they rarely point in the same direction. We build 360REV around the less glamorous half of this: access you can reason about and data you can trust. That is the only place our own product appears in what follows.
What we're tracking
- Access control stops being all-or-nothing Permissions are one of those topics that feels administrative until it goes wrong. The principle behind good access control is simple: a person should be able to do the job in front of them and nothing more. The accounts clerk who raises purchase orders does not need to approve payments. The contractor who needs one report does not need the whole ledger. This is sometimes called least privilege, and the reason it matters is risk. Every extra permission is a surface for a mistake or a misuse, and the cost of that surface grows quietly as a team grows.
- Checking the AI's work before you trust it The second thread is about provenance. When a tool generates data for you, the obvious question is where the data came from. For years, AI features answered that question with silence: a cell filled in, a paragraph written, no way to see the source. That is fine for a first draft and dangerous for anything you will act on.
- Paying people in other countries If your business works with suppliers, contractors or sellers abroad, cross-border payouts are a recurring source of friction. Each new country tends to bring its own banking rules, its own setup delay, and its own quiet failure rate where payments bounce or stall. The cost is rarely the fee. It is the weeks of setup and the proportion of payments that silently do not arrive.
- What the market will pay for go-to-market software Acquisition prices are a signal, even if you are not buying or selling. They tell you what sophisticated buyers think a category is worth, and that shapes which products get funded, maintained and expanded over the years you will depend on them. Today SaaStr examined go-to-market software through one recent deal, noting that "Salesforce agreed the other day to buy Braze for $5.66 billion, 6.8x trailing revenue."
- The spending boom and what it means for buyers Underneath all of this is the money. TechCrunch reported today that "Big Tech is pouring billions into AI infrastructure, but mounting debt, negative cash flow, and growing investor skepticism are raising questions about the sustainability of the AI spending boom." [6] You do not need a view on whether that skepticism is right to draw a buyer's conclusion from it.
- The through-line The day rewards a boring kind of attention. Ask what the smallest unit of access is. Ask where a generated number came from. Ask how long a payout takes and how often it fails. Ask who owns the tool and what happens if its price changes. None of these questions are about the newest capability. All of them are about whether the tool will still serve you in a year, which is the only test a business choosing software actually needs to pass.
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.
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.
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.
Sources
- Rebuilding user permissions: what’s live and what’s next Xero
- Google Workspace Weekly Recap - October 30, 2026 Google Workspace
- Stripe on Stripe: What we learned moving $1B in vendor payments to Global Payouts Stripe
- The B2B Category the Markets “Hate” the Most Today: GTM SaaStr
- Salesforce’s M&A spree continues with a reported $375M deal for defense tech startup Rune TechCrunch
- Cracks are emerging in the AI spending boom TechCrunch
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