The vendor decisions you do not get a vote on
A business does not only choose a product. It chooses a dependency on the decisions of the people who make that product, and three stories reported today are a reminder of how far those decisions can move without asking you first. An integration can be switched off, a report can be widened so you finally see who has your files, and the company you are betting on may never reach the outcome its investors are hoping for. None of these are things you control directly. All of them are things you can plan for when you choose tools.
When a partner can switch off your integration
Most software does not work alone. You buy one tool for scheduling, another for messaging, another for payments, and you rely on them passing data to each other through an integration. It is easy to treat that integration as plumbing — a permanent pipe between two systems. It is not. An integration is an agreement between two companies, and an agreement can end.
That is what makes today's report worth reading closely. SaaStr describes a long-running partnership that came apart: "Podium co-founder and CEO Eric Rea posted last week that ServiceTitan gave roughly 1,000 shared customers about 30 days' notice that the Podium integration was being switched off" [1]. Set aside the two names for a moment and look at the shape of it. Around a thousand businesses had built a daily workflow on a connection between two products they had each chosen on purpose. One of those vendors decided, for its own reasons, to end the connection, and gave a month to adjust.
For a business, the lesson is not that integrations are dangerous. It is that an integration you depend on is a dependency on a relationship you are not party to. When two of your vendors decide to compete rather than cooperate, the join between them is the first thing that breaks. The practical response is to know, for every connection that matters, what you would do if it disappeared next month. Which data lives only in the pipe? What would you have to re-enter by hand? This is the quieter half of the problem we wrote about in why your tools do not talk to each other: tools that do talk can stop talking, and the switch is not yours to hold.
Seeing who can actually reach your files
The second story is calmer but points at the same nerve: control over your own data. One of the hardest questions to answer in any growing organisation is simply who can see what. Files get shared with a colleague, then a contractor, then someone outside the company for one project, and the permission outlives the reason it was granted. Nobody is being careless. The sharing just accumulates faster than anyone reviews it.
Google Workspace's weekly recap describes a change aimed at exactly that blind spot: "Administrators using Drive Inventory Reporting in Google BigQuery can now access granular external sharing fields" [2]. The detail that matters for a business is the word external. The risk in shared files is rarely the person sitting next to you. It is the access that reaches outside the organisation and is then forgotten. A report that lets an administrator list those external permissions turns a vague worry into something you can read, sort and act on.
The concept to take away is that visibility is not the same as security, but you cannot have the second without the first. You cannot close a door you did not know was open. When you evaluate any system that holds your documents, customer records or messages, ask what it will let you see about its own sharing — not just how it protects data, but whether it will tell you, plainly, who currently has reach into it. That is the same instinct behind the audit trail nobody thinks about: the record of who did what, and who can see what, is boring until the day you need it, and then it is the only thing that matters.
Choosing a vendor that may still be here
The third story seems to be about founders, not buyers, but it carries a message for anyone choosing software. SaaStr's advice on exit strategy opens with a blunt figure: "The vast majority of startups will never get one strong acquisition offer" [3]. That is written for people building companies. Read it as a customer and it says something useful about the companies you buy from.
When you adopt a tool, you are not only choosing its features today. You are making a quiet bet that the company behind it will still be running, supported and improving in two or three years. Most software vendors are small companies, and most small companies do not reach a tidy, well-funded exit. Some are acquired and folded into something larger, which can change a product beyond recognition — as the first story in today's briefing shows, an owner's strategy can turn a partner into a competitor overnight. Some simply run out of road.
This is not a reason to avoid younger products. It is a reason to ask continuity questions before you commit. Can you get your data out in a usable form, at any time, without asking permission? If the company changed hands tomorrow, what would you lose? A tool that lets you leave cleanly is a tool you can adopt with less fear, because your exposure is bounded. We made that case in choose software worth using, and the ability to walk away with your records intact is the same principle we set out in the data you should be able to export on any Tuesday.
The thread, and what to do about it
The three stories are different in tone — a broken partnership, a reporting feature, a line of advice to founders — but they rhyme. In each one, a decision that affects your business is being made by someone other than your business. A vendor ends an integration. A platform decides how much its reports will reveal. A company's future is shaped by markets and acquirers you never meet.
You cannot take those decisions back. What you can do is reduce how much a single outside decision can cost you. Keep a clear map of which connections you depend on and what breaks if each one ends. Insist on being able to see who has access to your data and to export that data whenever you want. Favour tools that make leaving easy, because easy to leave is the same as safe to adopt. At 360REV we build with that in mind — your records stay yours to see and to take — but the habit matters whatever you use. The goal is not to predict which vendor will surprise you. It is to make sure that when one does, the surprise is survivable.
Sources
- [1] ServiceTitan Just Shut Off Podium's Integration for ~1,000 Shared Customers. Why? Agents Turned a 9-Year Partner Into a Direct Competitor. — SaaStr
- [2] Google Workspace Weekly Recap - August 21, 2026 — Google Workspace Updates
- [3] Dear SaaStr: How Do You Build a Real Exit Strategy? — SaaStr