AWS just committed a billion dollars to engineers who help customers put AI into production.
On June 30, at the AWS Summit in Washington D.C., the company announced Forward Deployed Engineering. The short version: AWS is embedding thousands of its own AI engineers directly inside customer organizations to co-build and run production AI systems. The investment behind it is $1 billion.
It is a funded global organization with named customers already in production.
The Allen Institute, Cox Automotive, the NBA, the NFL, Ricoh, and Southwest Airlines are already working with FDE teams. The NFL says it shipped NFL Fantasy AI and NFL IQ into production in weeks.
Those are live systems at organizations where downtime is costly.
The billion-dollar admission
The largest cloud provider on the planet is putting a billion dollars into engineers working inside customer organizations. That investment treats deployment capacity as a constraint worth addressing directly.
AWS said it plainly. The FDE model is “agentic-first.” It compresses deployment timelines from months to days. And it is designed to leave the customer self-sufficient when the engagement ends, with knowledge graphs, runbooks, and trained internal staff able to operate independently of a recurring consulting engagement.
That last part matters. AWS describes an engagement aimed at deployment velocity and customer self-sufficiency. The deliverable is a working system and people inside your organization who know how to run it when the engineers leave.
Francessca Vasquez, VP of Frontier AI Engineering and Services, described the approach as an “AI-Driven Development Lifecycle.” Purpose-built agents help build agentic solutions, and each deployment makes the next one faster. The knowledge compounds. The semantic layer and governed knowledge graph live in the customer’s own AWS account. When the FDE team leaves, the intelligence stays.
Why AWS has an incentive to build self-sufficiency
Traditional consulting firms charge for presence. The longer the engagement, the higher the revenue. The incentive structure points away from self-sufficiency.
AWS flipped it. The incentive is adoption. Every customer running production AI on AWS generates platform revenue forever. Getting customers operational supports that platform revenue. That alignment changes everything about how the engagement works.
OpenAI and Anthropic have made similar forward-deployed moves. But AWS funded this entirely from its own balance sheet. A billion dollars of Amazon’s own money is pointed at getting companies from pilot to production.
The pattern is now undeniable
Look at what happened in the last 90 days across the three largest AI providers:
OpenAI started a consulting company. Anthropic embedded engineers with enterprise customers. Now AWS committed a billion dollars to do the same thing at scale.
Three major AI providers are investing in the people needed to deploy their technology inside businesses.
These investments make the people around AI more capable of using it. Together, they show a sustained commitment to deployment work alongside model development.
What this means if you run a team
The question business leaders have been asking for two years is “which AI should we use?” The question they should have been asking is “who is going to wire this into our actual work?”
AWS just answered that second question with a billion-dollar commitment. And the answer reveals the real competitive picture. Deployment capacity helps explain the gap between companies using AI and companies stuck in pilot: people need the skills, time, and process knowledge to put it to work.
The NFL’s account highlights engineers embedded in its operations who understood both the AI and the business process it needed to touch.
That is deployment expertise worth planning for.
If your organization has been waiting for better AI, assess what today’s systems can do in a defined workflow and who will integrate them. AWS’s commitment gives leaders a reason to examine their own deployment capacity.
AWS has made a billion-dollar commitment to an operational problem. An AI adoption plan should address that problem alongside technology evaluation: who will build the workflow, operate it, and teach the team to maintain it? Companies doing that work are establishing capabilities others will need to develop.