Agentforce Operations just landed, and the scope of what a Salesforce architect is expected to own quietly got a lot bigger.
Supply chain, procurement, finance. These aren’t new problems, but they’re now Salesforce problems. Someone has to design the logic, govern the data, and make sure the handoffs between agents don’t create new chaos where the old manual chaos used to be.
In my early days in consulting I ran ERP implementations before I ever touched Salesforce. I know firsthand how much complexity lives in those back-office flows. And I was talking to an architect just today who made a point that stuck with me: the back-office team dismisses the Salesforce front-office team because they see themselves as owning the more complex systems. This isn’t just a technology expansion. It’s a political turf war.
The architects implementing Agentforce Operations now have to navigate both. That takes technical depth and real communication skills, and not everyone who’s great at one is great at the other.
If you’re scoping a Salesforce architect role the same way you did in 2023, you might be building for a platform that no longer exists.
Curious what you’re seeing — has the scope expanded faster than you expected?
