Today's briefing
Your business software is learning to answer back
Salesforce has moved its CRM inside Claude and says you may never open the app again. What that actually changes for a school, a clinic or a workshop.
The one that matters
Salesforce moves its CRM inside Claude — and bets you will stop opening the app
What happened. Salesforce, the customer-records software that a large share of mid-sized sales and service teams run on, can now be operated from inside Anthropic's Claude assistant. Rather than opening Salesforce and clicking through tabs, a salesperson types or dictates a request in ordinary language — pull up this account, log what the customer said, draft the follow-up — and the assistant acts on the live records. Salesforce is selling this hard: one write-up summarised the pitch as customers never needing the Salesforce app again. In the same week the company raised its annual forecasts and said it was expanding the Anthropic partnership, which is why around ten outlets covered it, mostly as a share-price story.
What it actually means for you. Set the two brand names aside. The pattern underneath is that business software is starting to arrive as a conversation rather than as a screen, and the first place that pays is wherever your staff spend the day hunting through tabs instead of thinking. A 600-student school with two people handling admission enquiries and fee follow-ups probably loses an hour a day each to looking the same things up in three places. A 30-bed clinic's front desk retypes the same patient details into a scheduler, a billing sheet and a reminder message. A workshop with 40 staff has a supervisor who already knows which job is late but opens four screens to prove it. Retrieval and retyping is the work a conversational layer genuinely removes. It does not remove judgement, negotiation, or the decision itself — and those are the parts that were actually slowing you down, if you are honest about it.
What it does not mean
It does not mean you can stop paying for the underlying system. The assistant reads and writes the same database; permissions, admin settings, reporting and the audit trail still live in the app, and someone still has to own them. Anyone telling you the app is now optional is describing their product, not your Monday. Two further limits are worth naming. First, a chat box makes it much faster to get a confident wrong answer out of messy records — if three staff spell the same customer three different ways, you have bought a quicker route to the wrong invoice. Second, unless you are a Salesforce customer, nothing happened to your software this week. If you run Zoho, Odoo, Tally, a hospital information system or a well-loved spreadsheet, the honest answer today is: nothing yet. Your vendor will almost certainly announce something of this shape within a few months. Waiting for that is a respectable plan, not a failure of nerve.
What a sensible owner does this month
- Pick one workflow, not a rollout. One team, one task they repeat twenty times a week. Measure the before and after in minutes, not impressions.
- Test with a junior account. An assistant connected to your records inherits whatever that user can see. Run it under your most restricted login first and confirm it cannot surface salaries, margins or patient data it should not.
- Get three answers in writing from the vendor. Where does our data go, is it used to train anything, and can we switch it off for a single user.
- Budget it as an addition. Assume the assistant is billed on top of what you already pay per seat. Treat any pilot as a new line item, not a replacement for the old one.
- Clean the four fields you would actually ask about. Customer name, phone, status, amount owed. That unglamorous month of tidying is what decides whether any of this works.
- Skip it entirely if fewer than about ten people touch the system daily. The setup and training cost will not clear the savings. Revisit in six months when it is switched on by default and free.
Also worth knowing
-
Claude's memory now carries across chat and Cowork
Anthropic has unified Claude's memory so what a user told it in one product is available in the other. For a business that is convenience for staff and a quiet governance question for you: a price list, a patient note or a salary figure pasted into a conversation now persists across tools rather than dying with the chat. Worth one plain line in whatever AI-use note you give employees.
Adgully.com ↗ -
Claude gets a browser of its own, aimed at the boring portal work
Anthropic has released a browser built so the assistant can move around websites rather than only talk about them. The practical promise is the drudgery: logging into a supplier portal, pulling a statement, filling the same form for the fortieth time. Treat early versions as a supervised intern — fine on low-stakes lookups, nowhere near your banking or a tax portal login.
The New Stack ↗ -
OpenAI's teacher product reaches 55 more US school systems
ChatGPT for Teachers is expanding to 55 more US school systems, covering over 100,000 educators and staff, with training and support attached. None of it applies to schools in India or Canada yet, but it sets the template your board will be asked about: institutional accounts with admin controls, instead of teachers quietly using personal logins. If you run a school, decide your policy on personal-account use now, before a vendor decides it for you.
OpenAI ↗ -
Another cheap open model lands, and the price floor drops again
GLM-5.3-Flash arrived to heavy developer attention, one of several fast, cheap, openly released models from Chinese labs this month. You will never touch it directly, but it is the reason the cost of putting an AI feature inside a piece of software keeps falling. If a vendor quotes you a steep per-seat AI premium, that number has less ground under it every quarter — negotiate accordingly.
Hacker News ↗ -
Anthropic commits $45 billion to rented computing power
Anthropic has agreed to rent roughly $45 billion of computing capacity from infrastructure provider Nscale, the latest in a run of enormous compute commitments across the industry. Nothing here changes your bill this month. It matters only as a signal: the companies you may end up building on are taking on very large fixed costs, so avoid designs that only make financial sense if AI stays this cheap forever.
TechCrunch AI ↗ -
OpenAI publishes findings from the Hugging Face security incident
OpenAI has set out what it found after a security incident involving Hugging Face, the site where AI models are shared, plus the steps it is taking on model security and monitoring. The public detail is thin, so read it narrowly. The point for a non-technical buyer is simple: the AI inside the software you purchase comes through a supply chain, and that chain can be tampered with — add one question about it to your vendor checklist.
OpenAI ↗ -
A fake thinktank was reportedly built partly to influence what AI says
Reporting says a fake US thinktank, set up and funded by Israel, was designed in part to shape the answers AI systems give. Whatever you make of the politics, the mechanism is the part that touches your business: chatbots repeat what has been published about a subject, so anyone willing to publish enough can steer the answer. Never use a chatbot as your only source on a supplier, a regulation or a competitor.
Hacker News ↗ -
A travel firm let non-engineers build their own internal tools
Loveholidays describes using OpenAI's Codex to let staff outside engineering build small software themselves. This is the most underrated use of AI in a mid-sized company: your operations manager finally building the rota tool she has wanted for three years, instead of waiting in an IT queue. The catch is ownership — agree up front who maintains these tools when the person who made them leaves.
OpenAI ↗
How this briefing is put together
Every morning we read the day's AI announcements and reporting from the companies themselves and from the technology press, then pick the handful that actually change something for a working business. The analysis is ours and it is written for owners and managers, not engineers. Every story links to its original source above — read them, and disagree with us where we've got it wrong.