AI Readiness & Agentforce

Agentforce has moved fast. Salesforce has spent the last two years rebuilding its platform around autonomous AI agents — agents that don't just suggest an action, they take it: reading a case, checking your data, deciding what to do, and only handing back to a human when they genuinely can't finish the job. Sales Cloud, Service Cloud and Marketing Cloud are all being rebuilt around this shift.

That's a real change in what a CRM does. It's not a new button to click — it's a new way of working.

Speed is the opportunity — and the risk

The pace of change in Salesforce right now is unlike anything I've seen since I started working with customer databases in the mid-80s. New Agentforce capability is landing every release, several times a year. For most organisations, the constraint isn't "can we get this technology" — it's "can we get ready for it fast enough to use it properly."

An agent is only as good as the data, process and governance underneath it. Turn Agentforce on before that foundation is solid, and you get an agent that's confidently wrong, or one that nobody trusts enough to actually use.

What "AI readiness" actually means

Before any organisation switches on Agentforce, I look at:

  • Data readiness — is the data an agent would rely on accurate, complete, and actually structured the way the agent needs it?

  • Process readiness — are the processes an agent would take over well-defined enough to hand to something that acts autonomously?

  • Governance and guardrails — who's accountable when an agent acts, and what happens when it gets something wrong?

  • People readiness — does your team understand what the agent is doing well enough to trust it, question it, and improve it over time?

Getting these right isn't glamorous work, but it's the difference between an Agentforce rollout that delivers and one that quietly gets switched off six months in.

How I help

As a hands-on Salesforce Administrator working solo with organisations across New Zealand, I help you get from "curious about Agentforce" to "confidently using it" — assessing where your org actually stands, tidying up the data and processes agents will depend on, configuring and testing agents within Salesforce's admin tools, and mentoring your internal team so you're not reliant on an outside consultant to keep it running.

I'm not a developer, and for most Agentforce and Flow-based automation, you don't need one — a lot of what makes agents work well is genuinely admin-level configuration, done properly.

Want an honest read on where your organisation actually stands? [Get in touch.]

A few notes before you place this:

  • I've kept it deliberately measured rather than hype-driven, given how fast Agentforce is evolving — safer for a page that needs to stay accurate for a while.

  • I haven't included specific stats or case studies (e.g. adoption numbers, ROI figures) since those are Salesforce's own marketing claims, not yours — happy to add real examples if you have client outcomes you can reference.

  • Want this as a standalone top-level nav page, or nested under "Salesforce Expertise" as we discussed?