Why No One Has Enough FDEs, Why CS Can’t Fill The Gaps, And Why Agents Most Can’t Deploy Themselves — Today

Everyone rolling out AI Agents at scale is saying the same thing right now: we can’t hire enough forward deployed engineers.

And they’re right. But most companies are drawing the wrong conclusion from that fact.

The shortage of FDEs isn’t just a hiring problem. It’s a structural problem about what it actually takes to get AI deployed inside a real enterprise — and why the people and teams you’d normally lean on to do that work can’t do it anymore.

What Forward Deployed Engineers Actually Do

FDEs sit at the intersection of product, engineering, and customer success. They go on-site or deep into a customer environment, understand the actual workflows, and configure the product to work inside those workflows. They’re not building from scratch. They’re not doing basic support. They’re doing the hard middle work of making software actually land in the real world.

This role has existed for a long time. Palantir essentially built their entire go-to-market around it. You couldn’t buy Palantir’s product and self-serve your way to value. You needed their people inside your organization, configuring and training the system for your specific context.

That model worked. It was expensive and it didn’t scale the way SaaS was supposed to scale. But it worked, because complex software in complex environments requires human judgment to deploy well.

Now almost every serious AI product has the same requirement. And almost no one has enough of the people who can do it.

Why CS Can’t Fill This Gap. Please, Don’t Try.

The instinct at most companies is to solve this with customer success. CS is already post-sale, already focused on adoption and value realization. Just upskill them, right?

Wrong.

Traditional CS was built for a different era. The job was: help customers use software they’ve already decided to buy, make sure they hit their renewal metrics, escalate bugs. It was reactive, relationship-driven, and optimized for retention.

FDE work is different in almost every way. It’s proactive, technical, and optimized for deployment. You’re not waiting for a customer to have a problem. You’re going in before the problem exists and configuring the system so the problem never happens.

The skill set required is closer to a solutions engineer or a junior product manager with strong customer empathy than it is to a traditional CS rep. Most CS teams don’t have it. Retraining takes longer than most companies want to admit. And the velocity of change in AI tooling means that by the time you’ve upskilled your CS team for today’s deployment requirements, the requirements have shifted.

The Deeper Problem: Agents Can’t Deploy Themselves. Yet.

Here’s the thing that makes this especially acute right now.

The whole premise of AI agents is that they automate work. But deploying an AI agent is itself significant work — and it’s work the agent can’t do for you. Not yet.

Someone has to understand the customer’s workflows deeply enough to know where the agent fits. Someone has to train the agent on the right data, the right context, the right edge cases. Someone has to test it, catch where it breaks, and iterate. Someone has to get internal buy-in from the people whose jobs will change when the agent goes live.

That’s FDE work. And it’s manual, high-judgment, human work.

I saw this up close recently. A $6 billion AI company — one of the hottest in the market — had an agent quoting our team incorrect pricing. Telling us we’d need to quadruple our spend. When we asked how long the product had been in beta: a year. No one had properly trained the agent. The company’s own people hadn’t done the deployment work on their own product.

If a $6 billion AI company can’t train its own agent correctly after a year in beta, imagine what’s happening inside the enterprises buying these tools.