The Layer Underneath Agentforce

The ecosystem spent the last year hiring for Agentforce. But did anyone think to hire for the layer underneath it?

The agent demo works because the data in the demo is clean.

In your reality, the production org isn’t likely pristine. Salesforce Ben’s 2026 careers guide found that only 2% of admins describe their org as clean and well maintained. Technical debt is the biggest problem they report.

Order history lives in an ERP. (When was order history checked for accuracy?) Billing status lives somewhere else. Support history sits in a platform that was never built to talk to Salesforce. The agent reaches for all three, gets a partial answer, and tells your customer something that isn’t true.

So someone patches it with a point-to-point connection. Then another one. Documentation is a couple of iterations out of date. Six months later nobody can explain how data gets from the warehouse into Data Cloud, and the person who built it has moved on.

The market already figured this out. The same guide has the hiring numbers. Admin supply grew 47% last year. Developer demand shrank 12%, the only role in the ecosystem with negative demand growth. Technical Architect demand grew 27% against just 4% supply growth.

Hiring managers stopped looking for more builders. They’re looking for people who can design and get their arms around the landscape the agents run on. They need specialists who know the specific tools that build the data and integration layers.

Those layers are in MuleSoft and Data Cloud. Then there is the person who can develop your Salesforce governance rules and build the visualization layer in Tableau.

The plumbing is not glamorous. But it is necessary.

What I’ve seen is typically, these layers are set up by a systems integrator, then left to a skilled architect to manage. Then people and business needs change. That plumbing gets fixed to align with current needs in a single use case update. The overall data flow works, but like stringing together power strips, there are risks.

You’re not behind on AI because you picked the wrong agent platform. You’re behind because the integration layer belongs to whoever touched it last.

If you’re working out who should own your integration layer, I’m happy to talk it through. https://oakcresttalent.com/15mins

Share this article

Go to Top