On Tuesday, Accenture and Google Cloud announced a new business group built around 1,000 forward-deployed engineers. Their job is to sit inside client offices and get agentic AI working in real operations.
It isn’t a one-off. By The Next Web’s count it is the fifth version of the same idea this year. Microsoft committed $2.5 billion and 6,000 engineers to deployment. AWS announced its own. Anthropic and Blackstone built a venture that sells implementation rather than models. OpenAI set up a standalone services firm. TCS is turning thousands of its people into deployment engineers.
The consistency is the story. Every major platform has reached the same conclusion: the software does not land on its own. Julie Sweet told the Wall Street Journal what clients are saying to Accenture: “except it’s not happening, help us make it happen.”
They’re right about the problem
The model was never the bottleneck. The work is.
Most of the cost in an operation lives in work with a particular shape. It repeats — thousands of the same request, measured in volume, not milestones. It crosses departments — an order touches sales, finance, the warehouse and service, and loses context at every handoff. And it has always scaled with headcount. More volume, more people. Two lines rising in lockstep.
A copilot in every department doesn’t bend that line, because the work doesn’t live inside any one department. Someone has to sit with the operation, map it, connect the systems and decide where the agent stops and a person starts. That is exactly what a forward-deployed engineer does. On the diagnosis, the market has it right.
Look at the shape of the engagement
The Next Web described how one of these pods works. It goes into a company for eight to twelve weeks. It maps the process, integrates the data, builds an agentic system and writes a plan for scaling it. Then it hands the work to other staff to scale.
That is a sensible project. It is also a project.
Which leaves the one question a CEO needs to ask: what happens in week thirteen?
By then, everyone has done their part. The platform vendor’s obligation ended at go-live. The integrator’s ended at the invoice. The number the whole thing was bought to move — cost to serve, resolution rate, cycle time — belongs to nobody but you.
Software is accountable for software. Delivery is accountable for delivery. Nobody is accountable for the outcome.
Three questions before a pod walks in
What number moves, and is it in the contract? Not in the business case. In the contract. And if it doesn’t move, who goes back in, and at whose cost?
What stays behind? A scaling plan is a document. Your approval limits, your return window, your exceptions — written down as rules the system enforces, not prose inside a prompt — are infrastructure. One leaves with the consultants. The other runs on Monday.
Who runs it in week thirteen? If the answer is more of their people, you have bought headcount under a new name. The right answer is one of yours: your own operations lead, supervising agents and people on one queue, changing the rules without filing a ticket.
The part worth getting right
Forward-deployed engineers are the right answer to the first ninety days. Nobody gets agents into a live operation without people who understand both the operation and the agents.
They are not the answer to the next nine hundred. What decides those is what the engineers leave behind — and whether anyone signed up to be accountable for the number.
We don’t leave a report behind. We leave infrastructure that knows how the enterprise runs.
Sanjay Sethi is the founder and CEO of CygnusAlpha. We turn AI ambition into AI operations.