Accenture, Deloitte and EY All Run Forward Deployed Engineering Now: What Actually Differs
The short answer
Forward-deployed engineering companies now include Accenture, Deloitte, EY, IBM Consulting, Capgemini, Cognizant, TCS and more than thirty Salesforce partners, so the label no longer tells delivery partners apart. The question that still separates them is structural rather than semantic: ask which vendor relationship funds the pod, because that answer, not the job title on the team, tells you whose roadmap the work will end up serving.
A year ago, “we work forward-deployed” was a usable filter on a shortlist. Today it is a category label the largest system integrators, the Big Four and a platform vendor’s partner program have all adopted, in most cases co-branded with the platform paying for the practice. The method did not get worse. It stopped carrying information.
Key takeaways
- The label went mainstream in under a year. Deloitte named a forward-deployed engineering practice in December 2025 (Deloitte), Accenture launched one with Microsoft in March 2026 (Accenture), and EY launched the roles in the UK and Ireland in April 2026 (EY).
- The new names come with a platform attached. Accenture’s own term, according to Anthropic’s announcement, is “reinvention deployed engineers” (Anthropic). Capgemini’s Outcome Deployed Engineers work alongside Google’s own engineers on Gemini Enterprise (Capgemini). IBM’s Forward Deployed Units run on IBM Consulting Advantage (IBM).
- Most of these practices are co-branded with a platform. Accenture sells the label through eight platform relationships, including separate programs with ServiceNow, SAP and Workday (Accenture and ServiceNow, Accenture and SAP, Accenture and Workday). Deloitte’s careers site names lead roles after vendors, such as a Lead Anthropic Forward Deployed Engineer (Deloitte careers).
- EY’s practice now works alongside Microsoft’s. On 21 May 2026 EY and Microsoft launched a global initiative that pairs Microsoft’s own forward-deployed engineers with EY professionals (EY and Microsoft), and EY says it is building its own FDE capability through training with Microsoft (CIO.com).
- A vendor now runs its own partner network for the model. Salesforce launched a Forward Deployed Engineering Partner Network in April 2026 with Accenture and Deloitte as launch partners, explicitly to scale Agentforce (Salesforce).
- Even the open version starts on one stack. Deloitte’s Open Model Engineering practice, launched in September 2026, argues sovereignty and control over data, IP and inference transparency, and initially builds on NVIDIA Nemotron open models and NIM microservices (Deloitte).
- The diligence question changed. Not “do you work forward-deployed,” which everyone now answers yes to, but “which vendor relationship funds this pod, and what happens to the build when we change models.”
Nine months, six practices, one label
The timeline is short enough to read in one pass.
Deloitte named a forward-deployed engineering practice in December 2025, structured, according to a June 2026 job listing, as pods of two to five engineers who own execution, resourcing, escalation and delivery health. Accenture launched a practice with Microsoft on 18 March 2026, with Microsoft supplying the platform and Accenture leading change management, process redesign and deployment. Salesforce followed in April 2026 with a Forward Deployed Engineering Partner Network: Accenture and Deloitte as launch partners, alongside Capgemini, Cognizant, IBM Consulting, KPMG, PwC, Slalom, Tata Consultancy Services and more than thirty firms in total. EY launched the roles in the UK and Ireland the same month. On 6 May 2026 at Knowledge 2026, ServiceNow and Accenture launched a joint program placing ServiceNow’s own engineers alongside Accenture’s inside shared customer environments.
Then the pattern produced its first concrete instance. On 12 August 2026 Deloitte announced it had become the first global system integrator to staff and deliver a Salesforce forward-deployed engineering engagement, embedding its engineers inside solution delivery teams to build Agentforce work (Deloitte). Three weeks later, on 2 September 2026, Deloitte launched an Open Model Engineering practice and said it would hire, train and certify forward-deployed engineers through fiscal 2027 to staff it.
None of this is a criticism of the firms involved. It is a market doing what markets do with a delivery model that works. But a CIO who put “forward-deployed” on an evaluation scorecard in early 2026 now has a column where every vendor scores full marks, which is the same as having no column.
Six practices have since become more than a dozen firms. Cognizant set up a Gemini Enterprise practice on 22 April 2026 and a Gemini Frontier Capability Group of more than 18,000 engineers on 19 October. Capgemini named its Outcome Deployed Engineers on 23 April, and IBM Consulting launched Forward Deployed Units on 14 May. EY and Microsoft launched a joint initiative pairing their people on 21 May. Accenture launched a program with SAP on 8 June, Wipro opened a Claude centre with its own forward-deployed engineers on 16 June, and TCS’s chief executive put a headcount target on the role on 12 July. On 8 September Accenture formed a Gemini Enterprise group with Google Cloud, and on 13 October it added a program with Workday. The firm-by-firm table further down sets out what each one announced, in its own words.
Forward deployed engineering companies, side by side
The table below uses only what each firm has published. Where a firm has not stated a pod size, the cell says so rather than guessing.
| Firm and practice | Launched | Platform the practice is tied to | Pod or team shape, as published |
|---|---|---|---|
| Deloitte, Forward Deployed Engineering (Deloitte) | 1 December 2025 | Vendor-named roles, such as a Lead Anthropic Forward Deployed Engineer | Pods of 2 to 5 onshore and offshore engineers under a lead engineer (Deloitte careers, archived June 2026) |
| Accenture and Microsoft (Accenture) | 18 March 2026 | Microsoft, with joint teams using Microsoft’s Frontier Suite | “Thousands of AI-skilled engineers” across the practice; no pod size stated |
| Salesforce FDE Partner Network (Salesforce) | 15 April 2026 | Salesforce Agentforce | Over 30 partner firms with Salesforce-trained engineers; no pod size stated |
| EY, UK and Ireland (EY) | 28 April 2026 | None named in April; Microsoft’s own FDEs work alongside EY’s people since 21 May (EY and Microsoft) | Senior engineers working inside client delivery teams; no pod size stated |
| Accenture and ServiceNow (Accenture and ServiceNow) | 6 May 2026 | ServiceNow AI Platform | A purpose-built pod per engagement, with ServiceNow and Accenture engineers together; no size stated |
| Deloitte, Open Model Engineering (Deloitte) | 2 September 2026 | NVIDIA Nemotron open models and NIM microservices, initially | Forward-deployed engineers to be hired and certified through fiscal 2027; no pod size stated |
| Independent partner | Not applicable | None funding the pod | Assembled around the client’s stack and architecture |
Read down the third column. All six named practices now name a platform, or name roles after one. EY was the open case until 21 May 2026, three weeks after the April roles, when it and Microsoft launched their joint initiative. EY says it is building its own FDE capability through close collaboration and training with Microsoft (CIO.com). That column, not the second or the fourth, is where the practices actually differ.
Which consulting firms and system integrators sell forward deployed engineering?
Accenture, Deloitte, EY, Capgemini, IBM Consulting, Cognizant, Wipro, Infosys and TCS have each announced forward-deployed engineers or a renamed equivalent, and PwC and KPMG are named in Salesforce’s and Microsoft’s FDE partner programs. The table sets out what each firm or its platform partner said, the name it uses, the platform the announcement ties it to, and the date. The labs’ and hyperscalers’ own deployment arms are compared in OpenAI’s DeployCo and Anthropic’s Ode versus an independent forward-deployed partner and are not repeated here.
As of 28 October 2026, from the firm’s own release or careers page, or its platform partner’s, unless marked as press-reported:
| Firm | What it calls it | Announced | Platform | Source |
|---|---|---|---|---|
| Accenture | Forward deployed engineers; “reinvention deployed engineers”, per Anthropic | Anthropic, Palantir (Dec 2025); Microsoft (Mar 2026); Salesforce (Apr); ServiceNow (May); SAP (Jun); Google Cloud (Sep); Workday (Oct) | One group or program per platform | Anthropic, Palantir, SAP, Google Cloud, Workday |
| Deloitte | Forward Deployed Engineering; Open Model Engineering | Practice (Dec 2025); Salesforce FDE engagement (Aug 2026); Open Model Engineering (Sep 2026) | Vendor-named roles; NVIDIA for open models | Deloitte, Deloitte careers |
| EY | Forward Deployed Engineers | UK and Ireland roles (Apr 2026); Microsoft initiative (May 2026) | Microsoft, through the 21 May alliance initiative; April roles cite EY.ai | EY UK, EY and Microsoft |
| Capgemini | Outcome Deployed Engineers (ODE) | Google Cloud AI Enterprise Hub (Apr 2026) | Google Cloud Gemini Enterprise, beside Google’s FDEs | Capgemini |
| IBM Consulting | Forward Deployed Units, a pod | Units (May 2026); OpenAI Practice (Aug 2026) | IBM Consulting Advantage; OpenAI Partner Network | IBM, IBM and OpenAI |
| Cognizant | Forward-deployed engineers, then Frontier Certified Engineers | Gemini Enterprise Practice (Apr 2026); Gemini Frontier Capability Group (Oct 2026) | Google Gemini | Cognizant, Google Cloud press corner |
| Wipro | Forward Deployed Engineers | Claude Center of Excellence (Jun 2026) | Anthropic, inside Wipro Intelligence | Wipro |
| Infosys | Forward deployed engineers | Topaz Fabric FDEs (Nov 2025); 6,000 hires, press-reported (Jul 2026) | Infosys Topaz Fabric, its own platform | PR Newswire via AAP, Deccan Herald |
| TCS | FDEs | Named FDE partner by Salesforce (Apr 2026); Google Cloud FDE teams sent to work with TCS (Apr 2026); headcount target, press-reported (Jul 2026) | None named by TCS; Salesforce and Google Cloud, through the vendors’ programs | Salesforce, Google Cloud, Reuters via Khaleej Times |
| PwC and KPMG | No branded practice; KPMG hires under the FDE title | Named FDE partners by Salesforce (Apr 2026) and Microsoft (Jul 2026) | Salesforce and Microsoft, through the vendors’ programs | Salesforce, Microsoft, KPMG careers |
| Independent partner | Not applicable | Not applicable | None funding the pod | Not applicable |
Of the firms that have announced anything themselves, only TCS names no platform, and two platform vendors name TCS instead. It sits in Salesforce’s FDE partner network, and at Cloud Next on 22 April 2026 Google Cloud said it was sending teams of its own forward-deployed engineers to work closely with teams from seven integrators, TCS among them (Google Cloud). As with PwC and KPMG, the platform behind a TCS pod is set by whichever vendor program staffs it. Accenture sells the same label through eight platform relationships at once: Anthropic, Palantir, Microsoft, Salesforce, ServiceNow, SAP, Google Cloud and Workday. Reply, the Italian integrator, had announced no forward-deployed engineering practice of its own by 28 October 2026. The Salesforce network reaches the Nordics as well, with Twoday Oy among its named regional members. Whether one of these firms or an independent team fits your problem is a separate question, and it has its own decision rule.
What are IBM Forward Deployed Units, and what do the other new names mean?
IBM’s Forward Deployed Unit is a pod, not a person. IBM Consulting launched the model on 14 May 2026: business domain specialists, architects and engineers, with agents in the middle handling coding, evaluation, testing and documentation under human direction (IBM). IBM says a six-person pod does the work of a 30-person team. That is IBM’s own figure, not an independent measurement. IBM’s own diagnosis: “The rise of the FDE is not the solution, it is the signal.”
The units run on IBM Consulting Advantage, IBM’s own delivery platform of reusable assets, agents and industry accelerators. Three months later, on 13 August 2026, IBM said it would bring forward-deployed units trained through the OpenAI Partner Network to clients, alongside a dedicated OpenAI Practice (IBM and OpenAI). The pod sits on IBM’s platform and, from August, on OpenAI’s partner program too.
Capgemini’s name is Outcome Deployed Engineers. Its release of 23 April 2026 describes ODE teams in dedicated pods inside client environments, working alongside Google’s own forward-deployed engineers on Gemini Enterprise (Capgemini). Accenture’s own term for forward-deployed engineers, according to Anthropic’s announcement, is “reinvention deployed engineers” (Anthropic).
Each new name changes the shape of the team: a pod with agents in the middle at IBM, a pod named for the outcome at Capgemini, a renamed engineer at Accenture. None of them changes who funds the pod. IBM’s units sit on IBM’s platform and OpenAI’s network, Capgemini’s sit next to Google’s engineers, and Accenture’s sit in one group or program per platform.
Do PwC and KPMG have a forward deployed engineering practice?
Neither PwC nor KPMG had announced a branded forward-deployed engineering practice by 28 October 2026. Both appear as named partners in at least two vendor programs. Salesforce’s FDE Partner Network, launched on 15 April 2026, lists KPMG and PwC among the global firms joining launch partners Accenture and Deloitte (Salesforce). Microsoft’s Frontier Company launch post of 2 July 2026 names Accenture, Capgemini, EY, KPMG and PwC among the global system integrators it works with on forward-deployed engineering (Microsoft). PwC is also one of the seven integrators Google Cloud said at Cloud Next on 22 April 2026 it was sending its own forward-deployed engineers to work with (Google Cloud).
KPMG also hires under the title. Its US careers site lists a Director, Technical Lead Forward Deployed Engineer in the Advisory practice, responsible for “setting technical expectations and standards for FDE delivery pods” (KPMG careers). That listing asks for cloud experience across Azure, GCP or AWS rather than one vendor.
Without a branded practice to read, the pod a buyer meets is shaped by whichever program staffs it: Agentforce in one, Microsoft’s stack in the other. If the proposal is Salesforce-led, read why Salesforce’s own partners are not seeing Agentforce ROI before you sign.
TCS, Infosys, Cognizant and Wipro forward deployed engineers: what offshore scale changes
The offshore-scale integrators state forward-deployed engineering as headcount, and the numbers run to thousands. TCS’s chief executive K Krithivasan told Reuters, in an interview published on 12 July 2026, that he wants “as many as 1% to 1.5% of our associates” working as FDEs, which Reuters put at up to 8,900 people (Reuters via Khaleej Times). Infosys will hire 6,000 forward-deployed engineers over the next few years, according to a Deccan Herald report of 23 July 2026 (Deccan Herald). Cognizant’s Gemini Frontier Capability Group dedicates “more than 18,000 engineers” (Google Cloud press corner). Wipro describes a global pool of Claude-trained forward-deployed engineers and gives no size. For comparison, Accenture’s Gemini group plans a “1,000-person FDE workforce”.
Two of those figures are press-reported rather than taken from company releases. The TCS number comes from a Reuters interview carried by Khaleej Times, and the Infosys number from the Deccan Herald’s account of the company’s results remarks. We found no company release carrying either figure.
At four- and five-figure headcounts, “forward deployed” describes a training and certification program applied to a large delivery workforce. Cognizant draws part of that line itself: it says its Frontier Certified Engineers are distinct from a generic FDE (CIO Dive). A large workforce can still deploy in small pods, as Deloitte’s model of two to five engineers under a lead does. What a headcount cannot tell you is how deep the training runs across thousands of people, or how senior the few who arrive in your pod will be.
So ask for three facts before the label does any work in the evaluation. How many people sit in the pod assigned to you, and for how long? How senior are they, measured in years of production work rather than in certifications? And where is the work done: in your building, in your time zone, or in a delivery centre the pod hands work to? An onshore lead with an offshore build team can be the right model for some systems. It should be described and priced as that.
Read the org chart, not the job title
The useful signal moved from the label to the structure underneath it, and the structure is public.
Deloitte’s own careers listings name roles after vendors. Its Lead Anthropic Forward Deployed Engineer leads forward-deployed pods and must bring hands-on experience with Anthropic’s platform (Deloitte careers), and Deloitte announces its Salesforce FDE engagements separately. That is engineering organised per model or platform partnership, not one team assembled around a client’s architecture. Accenture’s practices are individually co-branded: Anthropic and Palantir in December 2025, then Microsoft, ServiceNow, SAP, Google Cloud and Workday in 2026. Salesforce’s partner network is explicit about its purpose: it exists to scale Agentforce, and members get a direct line into Salesforce product teams.
Each of those is a rational commercial design, and each tells you something before the first workshop. A pod created inside a Microsoft practice is staffed, trained and measured against Microsoft’s platform. A pod inside the Salesforce network is measured on Agentforce reaching production. If the answer to your problem sits on that platform, you get specialists with roadmap access, which is genuinely valuable. If it does not, you are asking a team to recommend against the relationship that funds it.
This is the same argument we made about the labs’ own delivery arms in OpenAI’s DeployCo and Anthropic’s Ode versus an independent forward-deployed partner. The argument has not changed, only its surface area. It used to apply to two model vendors. It now applies to most of the named field.
Accenture and Microsoft forward deployed engineering: one practice, one stack
Accenture’s Microsoft practice is the clearest case, because Accenture’s own release states the division of labour: Microsoft provides the platform and technology, and Accenture leads change management, process redesign, industry workflows and deployment at scale. Joint teams work with clients using Microsoft’s Frontier Suite (Accenture). Nothing in that is hidden or misleading. It describes a practice whose architecture is decided before the engagement starts.
It is also not Accenture’s only one. Seven weeks later Accenture and ServiceNow launched a separate forward-deployed engineering program built on the ServiceNow AI Platform, offering more than 300 prebuilt agent skills and workflows on that platform (Accenture and ServiceNow). The pattern runs one level deeper too. Accenture’s own AI Refinery platform uses the NVIDIA stack, including NVIDIA AI Enterprise (Accenture), and Deloitte’s Zora AI is built on the same NVIDIA AI Enterprise layer (Deloitte).
Those two sit in a longer list. Accenture formed business groups with Anthropic on 9 December 2025 and with Palantir on 16 December 2025, and joined Salesforce’s network as a launch partner in April 2026. On 8 June 2026 it launched a program with SAP on SAP Business AI Platform, in which Accenture FDEs work “while aligning with SAP’s product roadmap and engineering standards” (Accenture and SAP). On 8 September 2026 it formed a Gemini Enterprise Business Group with Google Cloud, which will establish a “1,000-person FDE workforce” (Accenture and Google Cloud). On 13 October 2026 it added a program with Workday for HR and finance, in which Accenture engineers also work with Workday’s product and technology teams to build new agentic capabilities on the Workday platform (Accenture and Workday). Anthropic’s announcement states the structure plainly: “Accenture Business Groups are dedicated practices built around Accenture’s most important technology partnerships”, each with its own teams (Anthropic). How the Palantir group is staffed, and what that means for cost, is covered in what Palantir AIP and Foundry cost a European mid-cap.
So “Accenture forward deployed engineering” is not one delivery model. It is a portfolio of platform-specific practices under one name. For a DACH mid-cap that runs on SAP, the SAP program is the one to read closely, because its pod is aligned to SAP’s roadmap by design. What SAP’s own AI reaches, and what it misses outside SAP, is set out in SAP Joule’s limits. A buyer comparing it with an independent partner should first ask which of those practices is on the proposal, then ask what it would cost to move the finished system off that platform in two or three years, when the model or the licence terms change underneath it.
“Open” at the model layer is not the same as neutral
Deloitte’s Open Model Engineering practice deserves a closer look, because its vocabulary is close to the one we use. The announcement talks about flexibility, cost predictability, sovereignty and enhanced control over data, intellectual property, model behaviour and inference transparency, and about helping clients build sovereign AI stacks on open-source frameworks across North America, Europe and Asia Pacific.
That is a serious position, and its arrival from a firm of that size says where enterprise buyers are pushing the market. It is worth naming precisely what it does and does not settle. The practice initially builds on NVIDIA Nemotron open models and NIM microservices. Open weights remove one dependency: you can inspect the model, run it where your rules require, and you are not renting the intelligence inside someone else’s API. They do not remove the dependency one layer down, on a specific inference stack and the tooling around it.
So the buyer’s question splits in two. Can I change the model without rebuilding, and can I change where and how it runs without rebuilding? A partner can answer yes to the first and no to the second, and both answers matter over a system’s life. Model-agnostic delivery is a property of the architecture, of where the context, the retrieval, the evaluations and the guardrails live and who holds them. It is not a property of the model licence.
Is any integrator’s forward deployed engineering model-agnostic?
Some integrators say so, and each claim sits inside a platform. Cognizant told Channel Dive, as reported by CIO Dive, that its Frontier Certified Engineers are “model-agnostic builders”, in contrast to a traditional forward-deployed engineer focused on deploying one company’s AI platform (CIO Dive). Those engineers sit in a group named for Gemini and built with Google Cloud. Infosys’s chief executive Salil Parekh says clients “are able to work with any foundational model”, through Infosys’s own Topaz Fabric (Deccan Herald). IBM’s units run on IBM Consulting Advantage.
Model choice and platform choice are separate questions, and these claims answer the first. They expose a third lock-in, after the model and the cloud: the integrator’s own delivery platform, sitting between your data and whichever model you pick. The pattern repeats beyond IBM and Infosys. EY set its April roles within its investment in the EY.ai platform (EY), and Wipro integrates its Claude work across its own Wipro Intelligence stack (Wipro). If your context, your retrieval and your evaluations live inside Topaz Fabric or IBM Consulting Advantage, swapping the model is easy and leaving the integrator is not.
So test any model-agnostic claim against the exit. Do the context, the evaluations and the code leave with you, in a form you can run without the integrator’s platform? Who holds the licence to that platform layer once the engagement ends? The longer version of this argument is in what it actually takes to own your intelligence.
What Nucleo builds is the context engine: the intelligence layer your company runs on, owned by you, in your estate and model-agnostic. There is no delivery platform of ours between your data and the model, so there is nothing of ours to export on the last day.
Independent analysts arrived at the same question
The concern is not confined to firms with a competing interest. Constellation Research published an assessment that credits the model’s value and names two risks: that forward-deployed engineers get used as a crutch to smooth over immature vendor product, and that the market lacks vendor-neutral options. Its CEO Ray Wang draws a hard line on the role itself, saying a real forward-deployed engineer takes the requirement back into the product and ships, and is not a sales engineer, a field CTO or an architect in a new costume (Constellation Research).
Forrester framed the same thing from the buyer’s side, describing forward-deployed engineers as training wheels for AI reinvention (Forrester). Training wheels are useful, and they are also something you are meant to take off. A delivery model that leaves you permanently dependent on the pod that built the system has failed at the part that matters most to a company with an IT team it intends to keep.
Gartner adds a pricing warning. CIO Dive reports Gartner cautioning buyers about providers that package traditional IT consulting as FDE-level assistance and charge a premium for it (CIO Dive), a point we take further in what a forward-deployed engineer is. The scorecard below is built to tell forward-deployed work from relabelled consulting, whoever is selling it.
What to put on the scorecard instead
Four questions survive the label going mainstream. All four are answerable in a first meeting, and none of them can be answered with a job title.
Which vendor relationship funds this pod? If the practice is co-branded, the answer is on the letterhead. If it is not, ask how much of the team’s certification and training budget is tied to a single platform. There is no wrong answer, only an answer you should know before you sign.
Who owns the context layer when you leave? The models will change. The reconciled, governed knowledge your systems read from is the asset that outlives them, and it should sit in your estate, portable, with provenance and freshness tracked. If the intelligence lives in the partner’s platform or the vendor’s model, you have rented it. That is the whole of our argument in what it actually takes to own your intelligence. If the integrator’s own platform sits in the middle, as IBM Consulting Advantage does for IBM’s units and Infosys Topaz Fabric does for Infosys’s engineers, ask for its export terms as well as the model’s.
Is the team assembled around your architecture or around a certification? Pods built per vendor relationship are staffed by what the vendor certifies. Pods built per client are staffed by what the client’s stack needs, which in a European mid-cap usually means someone who can read a mainframe integration and someone who can argue with a works council, not a second platform specialist.
What is the number, and when? Every engagement should name a business figure agreed before the build starts, with a production date rather than a demo date. A pod that cannot commit to one is a discovery project wearing an engineering title. On a day-rate contract that risk stays with you, as we set out in what Accenture’s worst day on the market tells a CIO.
We should be equally clear about our own shape. Nucleo is not neutral about everything: we hold that the intelligence layer belongs to the client and that AI is a re-architecture rather than a tool, and we will argue for it. What we do not have is a platform relationship paying for the engineers, which is a narrower and more checkable claim than “independent.” We run no certification network and no partner tier, so if your problem is genuinely best solved inside one platform, one of the practices above will beat us on depth and roadmap access, and you should hire them.
The label is gone as a filter. The structure it used to stand for is still the thing worth buying, and it is still visible if you ask who funds the pod.
FAQ
Is forward deployed engineering from Accenture or Deloitte the same thing as from an independent partner? The working method is similar: engineers sit inside your environment and build until something runs. The structure is not. Accenture’s practices are co-branded per platform, with Anthropic, Palantir, Microsoft, ServiceNow, SAP, Google Cloud and Workday. Deloitte names forward-deployed engineering roles and engagements after vendors, including a Lead Anthropic Forward Deployed Engineer role on its careers site and a Salesforce FDE engagement. An independent partner has no vendor relationship funding the pod, so the architecture question stays open.
What should I ask a firm that pitches forward deployed engineering? Ask which vendor relationship funds the pod, whether the engineers are certified on one platform or assembled around your stack, and what happens to the work if you swap the underlying model in eighteen months. The job title answers none of those. The funding structure answers all three.
Does Deloitte’s Open Model Engineering practice make delivery model-agnostic? It moves in that direction at the model layer and states sovereignty, cost predictability and control over data, IP and inference transparency as goals. At the outset it builds on NVIDIA Nemotron open models and NIM microservices, so the model weights are open while the inference stack starts with one company. Open at the model layer and single-vendor at the inference layer are different properties, and a buyer should price them separately.
Is Accenture’s Microsoft forward deployed engineering practice platform-neutral? No. The announcement does not address model choice, but it ties the practice to one platform. Accenture’s own release says Microsoft provides the platform and technology while Accenture leads change management, process redesign and deployment, and that joint teams work with clients using Microsoft’s Frontier Suite. Accenture runs separate forward-deployed engineering programs with ServiceNow, SAP and Workday, each built on that vendor’s platform, and separate business groups with Anthropic, Palantir and Google Cloud. The question for a buyer is which of those platform-specific pods they are buying, and what it costs to leave that platform later.
Which companies offer forward deployed engineering in 2026? Deloitte announced a forward-deployed engineering practice in December 2025. Accenture launched one with Microsoft in March 2026, then programs with ServiceNow in May and SAP in June, a Gemini Enterprise group with Google Cloud in September and a Workday program in October 2026. Salesforce launched a Forward Deployed Engineering Partner Network in April 2026 with Accenture and Deloitte as launch partners and over 30 firms in total. In April 2026 EY launched the roles in the UK and Ireland, Capgemini named its Outcome Deployed Engineers and Cognizant set up a Gemini practice, which it expanded in October 2026. IBM Consulting launched Forward Deployed Units in May 2026, the month EY and Microsoft paired Microsoft’s forward-deployed engineers with EY professionals. Wipro followed in June 2026 and TCS set a headcount target in July 2026. Infosys uses forward-deployed engineers on its own Topaz Fabric platform, and Deloitte added an Open Model Engineering practice in September 2026. Independent partners with no platform relationship funding the pod make up the other side of the field.
Is the forward deployed engineer label now meaningless? As a shortlist filter, yes. As a description of how work gets done, no. Embedding engineers in the client’s environment is still the right method. It has simply stopped being evidence of anything, so the diligence moves from the label to the org chart and the contract.
What are IBM Forward Deployed Units? IBM Forward Deployed Units are IBM Consulting’s delivery pods, launched on 14 May 2026 in place of a single engineer. Business domain specialists, architects and engineers work with agents that handle coding, evaluation, testing and documentation. IBM says a six-person pod does the work of a 30-person team, which is IBM’s own figure. The units run on IBM Consulting Advantage, IBM’s delivery platform, and on 13 August 2026 IBM said it would bring units trained through the OpenAI Partner Network to clients, alongside a dedicated OpenAI Practice.
What does Accenture call its forward deployed engineers? Accenture calls them reinvention deployed engineers, according to Anthropic’s announcement of December 2025. The role sits in a portfolio of platform groups and programs: Anthropic and Palantir from December 2025, Microsoft from March 2026, Salesforce’s partner network from April, ServiceNow from May, SAP from June, Google Cloud’s Gemini Enterprise from September, where Accenture plans a 1,000-person FDE workforce, and Workday from October 2026.
Does Accenture have a forward deployed engineering program with SAP? Yes. Accenture launched a forward-deployed engineering program with SAP on 8 June 2026, built on SAP Business AI Platform. Accenture says its FDEs will align with SAP’s product roadmap and engineering standards. Like its Microsoft, ServiceNow and Workday programs, it ties the pod to one vendor’s platform, so for a mid-cap running SAP the question is whether the problem sits inside SAP or across the systems around it.
Do PwC and KPMG have a forward deployed engineering practice? Not a branded one, as of 28 October 2026. Both are named forward-deployed engineering partners in Salesforce’s FDE Partner Network, launched in April 2026, and in Microsoft’s Frontier Company launch post of July 2026. KPMG also hires under the title: its US careers site lists a Director, Technical Lead Forward Deployed Engineer in its Advisory practice. With no practice announced, the platform behind any pod either firm proposes is the first thing to establish.
Is EY’s forward deployed engineering tied to Microsoft? Partly. EY’s April 2026 announcement of the UK and Ireland roles named no vendor and set them within EY’s investment in its own EY.ai platform. On 21 May 2026 EY and Microsoft launched a global initiative that pairs Microsoft’s own forward-deployed engineers with EY professionals, investing US$1b+ over five years. EY’s global Microsoft alliance leader told CIO.com that EY is building its own forward-deployed engineer capability through close collaboration and training with Microsoft.
Are Cognizant’s, Infosys’s or TCS’s forward deployed engineers model-agnostic? Cognizant calls its Frontier Certified Engineers model-agnostic builders, and they sit in a group built with Google Cloud for Gemini. Infosys’s chief executive says clients can work with any foundational model, through Infosys’s own Topaz Fabric platform. TCS itself has named no platform for its forward-deployed engineers, but two vendors place it in their FDE programs: it is a member of Salesforce’s FDE Partner Network, and in April 2026 Google Cloud said it was sending its own forward-deployed engineers to work with TCS teams. Model choice and platform choice are separate questions: an integrator can let you change the model while its own delivery platform stays between your data and that model.
Related reading
- What is a forward-deployed engineer, and why enterprise AI needs one
- Forward-deployed engineer vs consultant vs system integrator: a decision rule for buyers
- Build, buy or embed: choosing an enterprise AI delivery model
- OpenAI’s DeployCo and Anthropic’s Ode versus an independent forward-deployed partner
- Microsoft Frontier Company: whose intelligence does it protect?
- What Palantir AIP and Foundry cost a European mid-cap
- The Big Four AI report errors, and what they mean for who builds your intelligence layer
Nucleo is an AI-native enterprise transformation company for European mid-caps. Our forward-deployed engineers build the context engine your company runs on, model-agnostic and in your estate, with no platform relationship funding the pod, and put agents into production on top of it. See how an engagement works, or tell us which vendor funds your current pod.
Sources: Deloitte, announcing Forward Deployed Engineering; Deloitte careers on the Lead Anthropic Forward Deployed Engineer role; Deloitte becomes first GSI to deliver a Salesforce FDE engagement; Deloitte launches Open Model Engineering practice; Deloitte unveils Zora AI; Accenture on its Microsoft forward-deployed engineering practice, the ServiceNow program, the SAP program, the Workday program, the Palantir business group, the Gemini Enterprise Business Group and AI Refinery with NVIDIA; Anthropic and Accenture partnership; Salesforce launches FDE Partner Network; EY launches FDE roles in the UK and Ireland; EY and Microsoft global initiative; CIO.com on Microsoft and EY; Microsoft Frontier Company launch post; KPMG careers, Director, Technical Lead Forward Deployed Engineer; IBM on Forward Deployed Units and its OpenAI partnership; Welcome to Google Cloud Next ‘26; Capgemini Google Cloud AI Enterprise Hub; Cognizant’s Gemini Enterprise Practice and, in the Google Cloud press corner, the Gemini Frontier Capability Group; CIO Dive on Cognizant and Gartner; Wipro Applied AI Center of Excellence for Claude; Infosys Topaz Fabric, PR Newswire via AAP; Deccan Herald on Infosys hiring; Reuters on TCS, via Khaleej Times; Constellation Research on forward-deployed engineers; Forrester, forward-deployed engineers are the training wheels for AI reinvention.