Claudeforce, and what's now possible in financial services

Michael Rouleau

Chief Executive Officer

I watched the Claudeforce announcement on Tuesday like everyone else in this industry. The number people grabbed onto was 37, the count of prebuilt sales skills shipping in the plugin. What I wrote down was four words from Marc Benioff. "The UI is the AI."

Salesforce spent 27 years building the interface that defined enterprise software. On Tuesday they said out loud that it's optional. Your people can stop navigating software and start asking it questions.

I've spent this year arguing that customer experience, data, and AI only pay off when you run them as one connected system. Tuesday was the strongest evidence yet for that argument.

What it means for financial services, plainly

Claudeforce is Salesforce and Anthropic connecting Claude directly to your Salesforce data, so people can work by asking instead of clicking through screens. It launched with a plugin for sellers, built on top of a broader capability, called AIforce, that lets any AI tool reach Salesforce data and take action under the same permissions a person already has.

Three things changed for a credit union, bank, insurer, or a wealth firm:

Claude now runs inside the Salesforce Trust Boundary, and it's the first model provider fully inside it. This means your risk team isn't opening a file on a new vendor, they're reviewing an extension of a platform they already cover.
The agent signs in as the person using it and inherits their permissions. If a relationship manager can't open a record, neither can the agent working for them. That's the question that stalls most agent pilots at the security review, and it now has an answer that doesn't require standing up a new permissions model.
The bill moves from seats to usage. Patrick Stokes at Salesforce said the token consumption isn't zero, though it sits well below what a development workload burns. Your CFO approved a per seat number and will see a consumption number.

None of that makes what you've already built worth less. The customer data, product logic, approval chains, rules your teams encoded one project at a time, is still vital. Stokes made the point himself, that the value of Salesforce always sat in the data and the metadata underneath it. What changed on Tuesday was the front door.

It does change how you think about adoption. You've spent years training teams on screens and measuring log ins. When the interface is a question, you're training people on what to ask and whether the answer holds up. And every workflow sitting in your backlog because the volume never justified building a decent screen for it just became reachable.

What Claudeforce actually unlocks for financial services

What was announced Tuesday was primarily a sales tool. But the implications for financial services is much deeper than that.

Every job in financial services that involves opening several screens to answer one question is currently designed around the old interface, not around the question. A credit analyst doesn't want 12 files. They want to know what changed. A servicing lead doesn't want a queue. They want to know who's about to call and why. Nobody built it that way on purpose. They built it because the screen was the only way in, so the screen became the job.

Take the screen away and the job changes shape without anyone redesigning it. That's what I mean when I say the interface is optional. Half the roles in this industry just had their job quietly redefined.

What I'd watch closely is how long it takes institutions to notice their job descriptions were written for a screen that no longer has to exist.

What we learned building headless

The wealth advisor's job was designed around a screen too, and we found out what happens when you take it away.

We recently built an advisor facing agent for a wealth management client on Financial Services Cloud, using the headless capability Salesforce shipped in March. It goes to production shortly.

An advisor asks which accounts need cash raised and how much. Today that means opening each account, checking holdings against the model, and moving to the next one. The agent does that across the whole book in one pass, scoped to what that advisor is allowed to see.

Three things that made it work:

The data had to agree with itself. Before the agent answers anything, it has to know exactly which client it's looking at. Portfolio, household and service history read as one picture because someone made those systems agree on the customer first.
The experience had to start from the question, not from the screen we were replacing. We started from what an advisor needs to know on a Monday morning and worked back from there.
The governance had to be engineered in. The agent can flag an account and open a rebalance request. It can't approve one. An advisor does that, the trade runs where trades run, and the system records what came back. That separation is built into the architecture. No one has to remember to enforce it.

The lesson I'd pass on is about where the time went. Most of it went into deciding what the agent must never do without an advisor in the loop. When your risk committee asks what this thing could do to us, that's the list they want, and it needs to be short.

It’s still all about CX + data + AI

Take that example apart and you get three separate things that had to be true. The data had to agree with itself before anything else worked. The experience had to be designed around the advisor's actual question, not translated from an old screen. And the governance had to be built into the architecture, not written down somewhere and hoped for.

Every institution reading Tuesday's news is going to reach for one of those first. Almost always the AI. It's the part with the announcement attached to it, and it's the part that feels like doing something.

It's also the easiest of the three, and the one that matters least on its own. An agent with clean permissions and no data underneath it is fast and wrong. An agent with good data and no governance is fast and unaccountable. The advisor's question only got a good answer because all three were already true before Claude ever saw it.

That's the argument I've been making all year, and Tuesday’s announcement confirmed it. Customer experience, data, and AI are one connected system. Treat them that way and you'll get more out of this news than institutions still running three separate programs.

Where does your institution stand?

Most institutions have gotten one of the three right. Data, experience, or governance, rarely all at once. Our AI Governance advisory takes an honest look at what's actually running in your environment today and hands back the architecture and roadmap to close the gap.

GET STARTED