14 Apr 2026

Salesforce TDX going fully free for virtual attendance is a smart move, and the session lineup tells you exactly where the company is placing its bets. AI agents, APIs, and what they're now calling 'vibe coding' — that last term alone deserves scrutiny from anyone running a serious technology function in financial services.

Vibe coding is the practice of describing what you want in natural language and letting an AI generate the underlying code. It's genuinely useful for prototyping. For a regulated credit broker or lender, it's a workflow that needs very clear guardrails before it gets anywhere near production. The FCA cares about model risk, audit trails, and explainability. A codebase assembled through conversational prompts and accepted without rigorous review is not going to survive scrutiny when something goes wrong. That's not a reason to ignore it — it's a reason to build the review process before your developers start shipping with it.

The Agentforce angle is where I'd focus. Salesforce is pushing hard on autonomous agents handling workflows end-to-end, and the consumer credit use cases are obvious:

• Application triage and document chasing
• Arrears outreach and payment arrangement conversations
• Broker portal queries handled without human intervention

The challenge in UK consumer finance is that several of these touch regulated activity or vulnerable customer interactions. An agent that handles a payment arrangement conversation needs to recognise financial difficulty signals and escalate appropriately. Building that into an Agentforce workflow is doable, but it requires compliance and operations people in the room during design, not as a sign-off step at the end.

TDX being free removes the excuse for technology leaders not to have someone in those sessions. The question worth sitting with is whether your organisation is building the governance capability to match the pace at which these tools are moving.

A 54% reduction in token usage from one engineering decision. That's what Callstack achieved by swapping screenshots for trimmed accessibility-tree snapshots in their mobile automation agent. The mechanism is specific and clever, but the broader point matters more: AI running costs are an engineering problem, and most teams aren't treating them that way yet.

In UK consumer finance, we're at an early but accelerating stage of embedding AI agents into operational workflows. Loan origination, document verification, affordability checking, complaint handling. The demos work. The prototypes impress. Then someone runs the numbers on what happens at scale and the enthusiasm cools fast.

The Callstack approach is a useful forcing function. Before you worry about which frontier model to use, ask what you're actually feeding it. Their agents were consuming tokens on visual noise, full UI hierarchies with invisible elements, redundant context. Stripping that out cut costs in half without touching the model or the task. The same logic applies directly to any agentic system reading documents, navigating internal systems, or summarising case notes.

• Context window hygiene is an engineering discipline, not an afterthought
• Token spend compounds quickly once agents run autonomously at volume

The compliance angle is worth flagging too. Regulators expect firms to understand and control their automated decision-making. If your AI agent is burning context on irrelevant inputs, that's an explainability problem as much as a cost one. What the agent sees shapes what it does.

Most technology leaders I speak to are focused on capability: can the agent do the thing? The smarter question is: what are you paying per decision, and does that unit economics work at the volume your business actually needs?