Skip to main content
Engineers from OpenAI’s DeployCo collaborating on-site with clients to optimize AI-driven workflows and enhance automation ef

Editorial illustration for OpenAI's DeployCo will embed engineers at client sites to tailor workflows

OpenAI's DeployCo will embed engineers at client sites...

OpenAI's DeployCo will embed engineers at client sites to tailor workflows

Updated: 2 min read

OpenAI has rolled out a new subsidiary called DeployCo, backed by more than $4 billion from investors that include TPG, Goldman Sachs and SoftBank. The unit will embed roughly 150 Forward‑Deployed Engineers on client sites, wiring OpenAI’s models into existing data, tools and workflows. While the technology itself may become interchangeable, OpenAI is betting that deep, on‑the‑ground integration will become the real barrier to competitors.

DeployCo mirrors Palantir’s approach: engineers act as consultants, building custom systems that tie AI to a company’s day‑to‑day operations and feeding those insights back into future model work. The launch also brings the acquisition of British consultancy Tomoro—known for work with Tesco, Virgin Atlantic and Supercell—into the fold, pending regulatory sign‑off. A roster of 19 investors, system integrators and consulting firms—from Bain & Company to McKinsey—has been tapped to support the effort.

In short, OpenAI is moving beyond pure model development into a full‑scale implementation business, hoping that the “moat” will be the workflow it embeds rather than the model it ships.

OpenAI Chief Revenue Officer Denise Dresser says AI is increasingly capable of doing meaningful work within organizations, and the challenge now is helping companies integrate these systems into the infrastructure and workflows that drive their business.

Why this matters

Will on‑site engineers make AI integration feel less abstract for businesses? OpenAI’s DeployCo, backed by more than four billion dollars from investors such as TPG, Goldman Sachs and SoftBank, is betting that a hands‑on approach can lock in client workflows that are difficult to replicate in a lab setting. By borrowing Palantir’s playbook, the subsidiary plans to start each engagement with a diagnostic phase, then dispatch engineers to connect its models with a company’s data, tools and control mechanisms.

For developers, this could mean new opportunities to build niche adapters rather than generic APIs. Founders may see a path to faster, customized AI adoption, yet the model’s reliance on bespoke engineering raises questions about scalability and cost. Researchers might wonder whether the focus on proprietary workflows will divert resources from broader model improvements.

It is unclear whether the moat created by these tailored systems will prove durable, or if clients will prefer more modular, self‑service solutions. Our community should watch how DeployCo’s strategy unfolds, balancing the promise of deeper integration against the practical limits of on‑site deployment.

Further Reading