Omnicom has shifted much of the product and engineering workforce behind its Omni marketing platform to Endava, a technology services contractor. Omnicom describes the arrangement as a multi-year partnership intended to add engineering scale and speed, while keeping the platform, client relationships, data science and AI intellectual property under its control.
The structure is commercially plausible, but it places a sharper boundary between ownership and execution around a system Omnicom presents as central to its integrated agency proposition. For clients and communications leaders, the important question is not whether contractors can build enterprise software. It is whether responsibility for roadmap decisions, service quality and data governance remains clear when the engineers supporting a proprietary platform sit with another employer.
Key Takeaways
- Omnicom says it retains ownership of Omni, its AI innovation, client relationships and intellectual property after transferring engineering personnel to Endava.
- The workforce move turns service continuity and governance into practical client questions because Omni connects work across multiple marketing disciplines.
- Rival holding companies are also building unified AI platforms, but their operating models differ in how they combine internal expertise with external technology partners.
Table of contents
Jump to each section:
- What Omnicom moved and what it kept
- Why the operating model matters
- How the move compares with rival holding companies
- What clients should ask next
What Omnicom moved and what it kept
The transfer took place across product and engineering teams supporting Omni, Omnicom’s marketing intelligence platform. The affected workforce spanned the United States, United Kingdom, India and Malaysia, while a separate group in the United States was laid off.
At least 468 employees transferred to Endava, while roughly 50 US employees were laid off. The reported changes affected Omni product and engineering operations across several markets.
Omnicom’s distinction is that it has externalized a substantial part of engineering delivery without selling the product or its underlying rights. The company says it continues to own AI innovation, data science, intellectual property and client relationships. That leaves Endava responsible for adding technical capacity within a product strategy that remains, at least formally, under Omnicom’s direction.
The positioning matters because the latest version of Omni was introduced as the connective layer across strategy, creative, media, commerce and measurement. This is not a peripheral internal system. It is part of how the holding company explains integration to clients after combining Omnicom and Interpublic capabilities.
Why the operating model matters
Outsourcing engineering can give Omnicom access to a broader delivery bench and more flexible technical capacity. Endava’s core business includes product engineering, cloud, data and AI work, which makes it a credible operating partner rather than a generic staffing supplier. The arrangement may also make it easier to standardize delivery across legacy teams and systems.
The trade-off is organizational distance. Product knowledge is not held only in source code or documentation. It also sits in the judgment of engineers who understand why integrations were designed a certain way, how client exceptions are handled and where data dependencies can fail. Moving those people under a contractor can preserve the knowledge, but it changes incentives, reporting lines and retention risk.
For a client choosing an agency partner this week, the transfer does not automatically reduce Omni’s capability. It does, however, make governance more material to the buying decision. Clients should expect Omnicom to explain who has authority over the roadmap, which party is accountable during an incident and how subcontracted personnel access client data.
How the move compares with rival holding companies
Large agency groups increasingly describe proprietary AI platforms as their operating core, not as optional tools. Omnicom’s decision stands out because engineering scale is now more visibly separated from platform ownership. WPP and Publicis also rely on major technology partners, but their public positioning emphasizes how those partnerships connect into group-wide systems and internal expertise.
| Holding company | Core platform | Public operating-model signal |
|---|---|---|
| Omnicom | Omni | Omnicom retains the product, client relationships and intellectual property, while Endava adds engineering scale through a multi-year partnership. |
| WPP | WPP Open | WPP presents the platform as a shared workspace connecting its talent, proprietary intelligence, client systems and outside technology partners. |
| Publicis Groupe | CoreAI and Marcel | Publicis positions its internal data and Publicis Sapient expertise as the foundation, with partners such as Microsoft supplying technology and integrations. |
The table does not establish that one model is inherently stronger. It shows why talent location has become part of platform credibility. Holding companies are selling clients an integrated combination of data, tools and people, so decisions about who employs the builders can affect how buyers judge control and resilience.
What clients should ask next
The near-term test will be operational rather than rhetorical. Omnicom will need to show that delivery speed improves without weakening institutional knowledge or creating ambiguity between its product leaders and Endava’s engineering managers.
- Roadmap ownership: Clients should know which Omnicom executive has final authority over product priorities and how Endava teams receive those decisions.
- Service accountability: Contracts should identify who owns response times, remediation and client communication when the platform fails.
- Data controls: Buyers should ask how contractor access is provisioned, monitored and revoked across markets and client environments.
- Team continuity: Omnicom should be able to explain how it will retain product knowledge if transferred employees leave Endava or move to other accounts.
If those controls are clear, the partnership may operate as a conventional way to scale a complex enterprise platform. If they are not, the move risks weakening the integration story Omni is meant to support. For communications teams, the practical conclusion is measured: the transfer is not proof of a platform problem, but it is a reasonable trigger for more precise due diligence.