Updated 48 minutes ago
Cognizant forms OpenAI delivery group for code, legacy systems and customer operations
The October 30 practice announcement brings together more than 25,000 professionals. Its three initial workstreams include modernization with consequential engineering review.
Three initial delivery workstreams
Cognizant [formed its OpenAI Frontier Capability Group on October 30](https://en.prnasia.com/releases/apac/cognizant‑commits‑more‑than‑25‑000‑professionals‑to‑openai‑delivery‑as‑enterprises‑move‑frontier‑ai‑into‑production‑553976.shtml), bringing together more than 25,000 professionals to deliver OpenAI products for clients. Its initial scope covers:
- Software engineering Codex‑assisted development.
- Application modernization Legacy mainframe analysis through cloud‑native code generation, using Cognizant Application Modernizer powered by OpenAI models.
- Customer operations Sales, service and support.
Modernization retains consequential engineering review
The [announcement](https://en.prnasia.com/releases/apac/cognizant‑commits‑more‑than‑25‑000‑professionals‑to‑openai‑delivery‑as‑enterprises‑move‑frontier‑ai‑into‑production‑553976.shtml) says engineers review every consequential decision in the modernization workflow. It also says Cognizant already uses an OpenAI‑based solution in its own sales and customer‑success operations.
For a team commissioning a legacy‑system migration, this makes the scope of a proposal consequential. A request to explain an existing program is different from a request to replace it. A useful work order identifies the input system, the behavior to preserve and who accepts the replacement. Generating code is one step in that handoff.
The [agent‑skills engineering guide](https://opentools.ai/resources/agent‑skills) describes specification, testing and review gates for coding agents. It offers a vocabulary for defining acceptance, rather than evidence about Cognizant’s internal process.
A delivery‑group headcount is not a customer outcome
The announced organization is a commitment of people to a practice; it does not report 25,000 new hires, a particular customer’s staffing allocation or an independently measured delivery result. Buyers still need the scope and acceptance evidence for their own work.
OpenTools’ [coverage of Cognizant’s earlier code‑assistance disclosure](https://opentools.ai/news/cognizant‑q3‑ai‑assisted‑code‑credentials‑revenue‑measurement) examines a different question: what the company’s adoption and credential counts measure. The new practice announcement identifies the work it intends to deliver; it does not turn those earlier measures into proof of client performance.
Cognizant’s Teaneck, New Jersey office photographed on January 9, 2013, shown as archival company context—not a current AI deployment. Photo: [Cognizant / Wikimedia Commons](https://commons.wikimedia.org/wiki/File:Cognizant_Technology_Solution%27s_office_in_Teaneck_,_New_Jersey.jpg), [CC BY‑SA 2.0](https://creativecommons.org/licenses/by‑sa/2.0/). Cropped and resized.
Related News
Oct 30, 2026
Triskell SP2 adds MCP actions and provider-data exclusions
The October 30 release connects external assistants to project work, adds attribute exclusions and supplies uploaded-document context. These describe different decisions.
TriskellMCPProject management
Oct 29, 2026
OpenAI’s subscription API credits have separate eligibility and expiry rules
The October 28 benefit connects eligible Pro or Business subscriptions to an owned API organization. Subscription eligibility, credit expiry and Codex exclusions are separate checks.
OpenAIChatGPTAPI Credits
Oct 29, 2026
Cognizant says over half its code is AI-assisted. What does that measure?
The October 29 results disclose AI assistance in over 50% of code and more than 95,000 credentials. Neither figure defines autonomous delivery, unique trained staff or AI-only revenue.
CognizantAI CodingEnterprise AI