17 Apr 2026

The framing of this announcement as a coding upgrade is wrong. What OpenAI is actually describing is an agent that can sit across your entire desktop and SaaS stack, execute multi-step workflows, and remember context between sessions. That is an automation platform with a coding origin story.

For UK consumer finance, this matters more than most sectors want to admit. Our technology teams spend enormous time on the connective tissue between systems: extracting data from one platform, reformatting it, pushing it into another, triggering downstream processes. That work is often too bespoke for off-the-shelf automation tools and too low-value to build properly. An agent layer that understands business context and can operate across applications without custom integration code could absorb a significant chunk of that overhead.

The enterprise memory feature is worth paying attention to specifically. An agent that retains knowledge of your workflows, your naming conventions, your edge cases, starts to look less like a tool and more like institutional knowledge that doesn't leave when someone hands in their notice.

Two things should give technology leaders pause though:

• Compliance and audit exposure. An agent that operates across systems and executes tasks creates a new class of action that needs to be logged, reviewed, and attributable. Most firms' governance frameworks were not designed for this.
• Vendor concentration. Routing automation logic through a single AI provider, on top of existing OpenAI dependencies, creates a concentration risk that the FCA's operational resilience rules were designed to make firms think hard about.

The competition with Anthropic's Claude Code is less interesting than the broader shift it signals. The major AI labs are no longer competing to be the best assistant. They are competing to be the operating layer that everything else runs through.

Whether your technology strategy has an answer to that question yet is worth asking.

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.