Salesforce's Agent Play Is a Procurement Problem
Salesforce Headless 360 is being framed as an AI innovation story. It's actually a vendor lock-in story, and UK financial services technology leaders need to read it that way. The shift from 'system of record' to 'system of execution' sounds neutral, even exciting. What it means in practice is that Salesforce wants its platform to be the thing that *does* things on behalf of your customers, not just stores data about them. Once your AI agents are executing loan decisions, affordability checks, or customer communications through Salesforce's orchestration layer, your switching costs don't double. They multiply. We've been here before with CRM. Firms that let Salesforce become their core customer data store in the 2010s are still paying for that decision. Agent orchestration is a deeper dependency than data storage because it's embedded in your operational logic, your audit trails, your FCA compliance architecture. The FCA's operational resilience rules are directly relevant here. PS21/3 requires firms to map important business services and set impact tolerances for disruption. If a third-party agent platform becomes your execution layer for credit decisions or collections workflows, that vendor relationship sits inside your resilience framework, not outside it. The contractual SLAs Salesforce offers are almost certainly not written to meet your impact tolerances. Two things technology leaders should do now: - Treat agent orchestration platforms as critical third-party infrastructure from day one, not after you've integrated them - Push hard on contractual specifics: what are the SLAs, what does remediation look like, and what does exit actually cost The interesting question isn't whether agentic AI has a future in consumer finance. It does. The question is whether you want a single US vendor controlling the execution layer of your regulated business processes, and whether your board and risk function understand that's what's being proposed.