AI is rewriting products and their price tags
The common thread today is that AI is not just a feature bolted onto software any more; it is changing what products are and what they cost. A new CRM entrant, a public argument about pricing, and agents that act on a customer's behalf all point the same way, while a breach at a large vendor is a reminder that the company holding your data is part of every tools decision.
A CRM built around AI from the start
Most software you buy today was designed before the current wave of AI, then had AI added to it. A product described as "AI-native" is built the other way round: the assumption is that an automated agent, not only a person, will be doing the work inside it. For a buyer, the interesting question is never the label. It is whether switching is worth the disruption of moving your contacts, your pipeline and your team's habits to a tool that is younger and less proven.
Dreamteam, founded by former Freshworks staff, has raised 53 million dollars to compete with the established names in customer relationship management, and reports that "Dreamteam has signed up more than 100 customers across 13 countries, with some businesses switching from established CRMs" [1]. The number worth noticing there is not the funding. It is that some customers are switching away from a CRM they already run. A CRM is one of the hardest tools to leave, because it holds the record of every deal and contact. When businesses move anyway, it usually means the new tool does something the old one cannot, or does it at a price that changes the maths. If you are evaluating a newer entrant, ask the vendor for the names of customers who switched and call them, because the migration is the real cost, not the subscription.
When refounding a product means making it cheaper
There is a word going around for companies that rebuild themselves around AI: refounding. It means more than adding a chatbot. It means rewriting the roadmap, often rebuilding the product so that other software can drive it, and rethinking the pricing. SaaStr makes the case that the pricing part is the one people underrate, arguing that "A lot of B2B companies are refounding themselves right now for AI" and that the right move is usually to charge less, perhaps much less [2].
The logic is straightforward once you see it. If AI lets a product do more of the work with fewer people, the cost of delivering it falls. A vendor that keeps the old price pockets the difference; a vendor that cuts the price passes it to you and makes switching away harder for your competitors. For a business choosing tools, this is a reason to renegotiate at renewal rather than assume last year's price is fixed. If a vendor has rebuilt its product around agents, it is fair to ask what that has done to their cost of serving you, and whether any of that saving reaches your invoice. The same argument sits behind the case for consolidating onto fewer platforms, which we covered in replace five business tools with one: fewer tools, each doing more, is where the pricing pressure is heading.
Agents that act on a customer's behalf
For years the automation question was whether your customers would talk to a bot. The newer question is the reverse: what happens when your customer sends their own bot to talk to you. Zoom frames this directly, writing that "Personal AI agents are completing purchases, negotiating discounts, booking appointments, and calling your service teams on behalf of customers" [3].
This is a genuine shift for anyone running sales or support. An agent acting for a customer does not get tired, does not forget a promised discount, and will compare you against alternatives in the same breath. It also does not read tone the way a person does. If your pricing depends on a human not quite doing the arithmetic, an agent will do the arithmetic. The practical response is not to block agents but to make sure your own side is consistent: the same answer to the same question every time, clear rules about what can be offered, and a record of who asked for what. That is the same discipline that makes human support reliable, which is why it is worth understanding where automated replies help and where they do not, a topic we looked at in what AI auto-reply is for. An agent on the other end raises the cost of an inconsistent answer.
Editing across Word and Docs without a conversion step
A quieter change, but one that touches almost every office, is file format friction. Teams split between Microsoft Word and Google Docs usually pay a small tax every day: export, convert, re-upload, lose some formatting, repeat. Google describes removing part of that tax, noting that "Google Docs makes it easy to work across file formats, letting you view and edit Microsoft Office files directly in Docs without converting them" [4], and extending the approach to reviewing edits across the two.
The reason this matters when choosing tools is that format lock-in is a hidden switching cost. If a document tool only works cleanly within its own format, every file you create there is a reason to stay. Cross-format editing lowers that wall, which is good for buyers in both directions: you are less trapped, and you can mix tools across a team without forcing everyone onto one. When you evaluate a document or collaboration tool, test it with a real file from the other ecosystem, including tracked changes, before you commit a team to it.
A breach at a vendor, and why it belongs here
Finally, a reminder that the vendor is part of the product. Infoblox, a large cybersecurity and automation company, has confirmed a security incident, with TechCrunch reporting that "The cybersecurity and automation giant said it's working with outside investigators to understand the scale of the breach" [5].
It is worth stating what this item does and does not tell us. It confirms an incident and says the scale is still being investigated; it does not, on its own, tell you what was taken or who is affected. For a business choosing tools, the lesson is not about one company. It is that every tool you adopt is a copy of your data held somewhere else. A vendor's security posture, and how plainly it communicates when something goes wrong, is part of what you are buying. The time to ask a vendor how they handle incidents is before you sign, not after. That due diligence rarely feels urgent on a quiet week, which is exactly why a day like this is a useful prompt to do it, and it fits the running record we keep in the daily briefing from 14 November.
Taken together, the day argues for a simple habit when you shop for software. Look past the AI label to the price, the switching cost, and the trust. Ask what the vendor's AI has done to their costs, test how hard it is to leave, and find out how they behave on a bad day. Those three questions survive whichever tool wins.
Sources
- [1] Freshworks alums raise $53M to take on Salesforce, HubSpot with AI-native CRM — TechCrunch
- [2] If You're Refounding Your B2B Company for AI, Make Your Product Cheaper. Probably Much Cheaper. — SaaStr
- [3] The rise of personal agents: is your contact center ready? — Zoom
- [4] Review edits across Microsoft Word and Google Docs without converting files — Google Workspace
- [5] Cyber giant Infoblox confirms security incident after hackers access 'company information' — TechCrunch