Depending on the software you buy

What we're tracking

• •When the service you depend on goes down Every tool you adopt is a dependency. While it is running you forget it is there; when it stops you discover how much of your own operation was resting on it. GitHub published an update describing a recent outage and the steps it is taking afterwards, framed as "An update on the August 17 outage and the steps we're taking to improve reliability." [1] For a business choosing tools, the detail of any single incident matters less than the posture a vendor takes once one has happened.
• •The pricing playbook is changing Stripe published a piece on monetisation trends drawn from pricing leaders around the world, opening with the observation that "As AI transforms software economics, the standard revenue playbook is breaking down." [2] It is worth sitting with why.
• •When the product is an agent, not a screen SaaStr wrote about a vertical B2B company that grew past $100M in annual recurring revenue on the back of agents. Its starting point is that the debate about whether to build with AI is settled: "Everyone agrees you have to build with AI now." [3] The sharper idea sits in the piece's own headline, which frames the goal as a product where every time a customer logs in, the company has failed.
• •Admin controls decide who can do what Google announced that an administrative tool in Workspace has moved from manual management to a programmable one: "The Google Workspace Allowlisted Domains API is now generally available." [4] The change sounds narrow, and for a very small team it is. The reason to notice it is what it represents.
• •Building instead of buying Xero wrote about small businesses and their advisers customising their own tools, opening on the old trade-off: "For years, when a small business or advisor hit a workflow problem, the answer was to find an app that solved it or live with a workaround." [5] The piece's premise is that this is shifting, as building a solution gets cheaper.
• •The thread Reliability, pricing, agents, controls, and the choice to build — five different stories, one underlying question. When you bring a tool into your business you are not buying features; you are taking on a dependency whose terms you should understand before, not after. Read the incident history. Forecast the bill. Ask what the product measures as success. Check who can enforce the rules. And know the full cost of anything you decide to build yourself. None of these are glamorous questions, and all of them are cheaper to ask now than to learn later.