How PwC UK built an AI-first engineering organisation

Collaborative coding in modern office space
  • Case Study

This is the story of how PwC UK's engineering and client teams worked with Microsoft GitHub Copilot to build an AI-first engineering capability at enterprise scale, in a regulated environment, responsibly.

PwC logo

Industry

Professional services

Featuring

Microsoft GitHub Copilot

What we learned

First-hand experience embedding AI into engineering at scale

1000

Nearly 1,000 engineers and technologists in our AI-first centralised engineering capability business unit, part of a broader PwC engineering network

30%

faster full-stack engineering delivery

Video

How PwC UK built an AI-first engineering organisation

3:43
More tools
  • Closed captions
  • Transcript
  • Full screen
  • Share
  • Closed captions

Playback of this video is not currently available

Transcript

Euan Cameron: So, Ben, AI software development has been a really hot topic over the last couple of years. Can you tell us a little bit about how PwC has been embedding it into the organisation?

Ben Lingwood: Yeah, so we've been through quite the journey ourselves. We formed a new innovation unit called Tech Catalyst internally, where all the builders are within the organisation. So that happened about 18 months ago, a rather serendipitous moment that it meant that we could go through and do an AI-enabled organisation right out of the gate, right? So we went through an activity to select the best tooling for that and landed on Microsoft GitHub Copilot.

Euan Cameron: And as a technology leader, how has Microsoft GitHub Copilot changed the way that you think about innovating and developing new solutions?

Ben Lingwood: So, firstly it's a control plane. So, it allows us to move quickly. So ,when a new model or a new agent or a new release comes out, it's a safe way for us to release it through the Microsoft GitHub Copilot environments. We've got our controls, our guardrails, all of our capabilities sitting inside that to make sure that's being accountably used. Secondly, it's a leg up. So, things like foundation models, things like coding standards. We've got those baked in, so we don't have to do those every single time. So it’s a series of accelerators in there. And then lastly, because it is a family of tools, links to our code libraries where we put our monitoring, allows us to do the full software development lifecycle all the way through, not just at the coding environment.

Euan Cameron: Got it. And in terms of speed and breadth of innovation, has it had an impact there as well?

Ben Lingwood: We have to move at a safe speed. We are an auditor. So, we're regulated. So, if you look at some of the new models and some of the new agents that have been released, it’s allowed us to move at speed, bringing some of those new models in and again, releasing them through the control framework.

Euan Cameron: Absolutely. And it’s a very powerful tool, but also, I guess quite different from previous generations, has it required any behavioural change amongst the team in order to adopt it successfully?

Ben Lingwood: So a number of learnings from our perspective, we had to train up our engineers. They had to learn how to use the tools accountably.

Euan Cameron: Have we been able to use any of those learnings as we seek to help our clients on similar journeys?

Ben Lingwood: Yeah. So it's great when you go in and talk to a customer and share where we got it wrong, right? And we got it wrong in a number of places, managing multiple libraries was a bit of a disaster, to be honest. So having a single model as we go through software development lifecycle, sharing our learning journeys. So great developers, that we've got in the organisation, but learning how to do software development lifecycle with these new tools has been a learning, right? We predominantly lean on AI for the main coding, doing the coding reviews afterwards, changing the innovation cycle, and also the journey we've been through even more recently as we've started to build a forward deployed engineer team, where we've brought engineers close to customers so we can do rapid development with customers.

Euan Cameron: And have GitHub been able to provide us with support as we've gone down this road?

Ben Lingwood: They have been absolutely fantastic. And a number of things that we've been through and as we've learned, as we've started moving down our Microsoft GitHub journey here. So, firstly training, new versions coming out every five minutes, it feels like. New capabilities, new baseline models, a constant learning journey has been really important to us. So that's training engineers, training developers, new models, new capabilities. Coming through the stack, advising us on things like best practice for management operations there. And really working with us as a partner as we've been through the innovation cycles as well, so the proximity of coders and customers coming together in a room to fix business problems, right, has been particularly powerful in helping us build that into the organisation.

Euan Cameron: Fantastic. Ben, thank you very much.

Ben Lingwood: Pleasure.

Introduction

Why we built a world-class engineering team

As clients increasingly expect AI-first delivery, PwC UK's engineering organisation needed a way to scale software development responsibly across hundreds of technologists, multiple delivery teams, and the governance demands of a regulated environment. Our centralised engineering capability, made that possible with Microsoft GitHub Copilot as the platform we chose to power it.

The starting point was a foundational need: a consistent way to build, productionise, scale, and operate technical assets across our engineering teams. That meant a unified approach to the software development lifecycle with security, responsible AI, and governance embedded from the outset, and with Microsoft GitHub Copilot integrated at the core.

We also had an internal challenge to overcome: multiple engineering teams, multiple delivery models, and fragmented ways of working. Scaling AI-first engineering across that footprint consistently, accountably, and at speed, required more than a tool. It required a new operating model, built around the right partnership.

That's why we formed a centralised engineering capability bringing together nearly 1,000 technologists, software engineers, data scientists, and AI specialists to help translate emerging innovations into practical business outcomes.

The timing was deliberate. The team was designed to be AI-first from day one not to retrofit AI onto legacy ways of working. It sits within a broader network of engineers across PwC and powers our Forward Deployed Engineering (FDE) business, enabling teams to prototype at velocity alongside clients.

 

Why Microsoft GitHub Copilot: meeting enterprise demands with enterprise-grade tools

Enterprises don't just need AI tools. They need enterprise-grade tools and the ability to manage them as the landscape evolves. That means being able to manage a broad and fast-changing model garden, update to the latest models without rebuilding the surrounding controls every time and support a range of users from professional developers to business users building lightweight tools all within consistent observability and guardrails.

After evaluating multiple solutions, we chose Microsoft GitHub Copilot. It offered the best ecosystem for our needs integrating across our development environments and control frameworks, while providing continuous access to new models as they come out.

Most importantly, Microsoft GitHub Copilot gave us what we call "Safe Speed", the ability to develop at scale across a broad model garden, supported by PwC's governance and oversight framework. Speed without sacrificing governance. Innovation without compromising accountability. For a regulated business and auditor, that combination wasn't a nice-to-have. It was essential.

The solution

Engineering the shift: tools, standards and a new way of working

Adopting AI coding assistants was the starting point, not the strategy. The tools alone don't transform an engineering organisation. What does is the operating model, standards, and culture you build around them. We approached the challenge through three pillars: Capability, Control, and Culture, underpinned by observability and risk management. Together, they define how we've made AI-first engineering work at scale — responsibly, consistently, and accountably.

  • Capability — Equipping our people to lead the shift
    AI-first engineering is as much a human shift as a technical one. Our priority from day one was making sure our engineers could use the tools confidently, accountably, and at the standard our clients expect. We invested in structured training and certification, not only on the technology itself, but on how to apply it responsibly. We established a consistent set of engineering principles and ways of working designed for an AI-first environment. And we started to redefine how software gets built, moving from traditional sprint cycles to a continuous flow of build, test, and deploy that matches the pace AI now enables.
  • Control — Engineering speed, responsibly
    As a regulated business and an auditor, we have to move both quickly and responsibly. That constraint shaped every decision we made. We built Microsoft GitHub Copilot into a unified control plane: when a new agent, model, or release becomes available, we have the protocols and guardrails in place to ensure it is adopted appropriately and accountably. These controls extend across the full software development lifecycle, not just the coding environment, giving us confidence that speed never comes at the expense of governance. Consolidating our codebases into a single GitHub organisation was a critical early step. It improved access, reduced duplication, made governance enforceable at scale, and reduced costs, turning a fragmented landscape into a foundation we could build on with confidence.
  • Culture — Learning by doing, and sharing what we learn
    We didn't get every decision right first time and that's exactly why this experience is valuable. Managing fragmented platforms early on slowed us down before we consolidated. Adapting to a continuous build-test-deploy model required engineers to unlearn habits built over years. Building confidence that AI was there to support, not replace, our people required clear intent and communication. Establishing trust in AI-generated code required deliberate effort, not assumption. Each of these lessons is now embedded in how we operate and in how we guide our clients through the same journey.
  • Observability and risk management — Keeping “Safe Speed” honest
    Underpinning all three pillars is a discipline of observability and risk management designed for the AI-first era. By capturing baseline metrics from the outset, we track adoption, usage, and impact in real time across the engineering organisation. We apply consistent guardrails as new models and agents enter the garden, gauge return on investment with precision, and maintain auditability end-to-end supporting the governance standards expected of a regulated business.

The results

Turning AI-first adoption into tangible benefits

The shift to AI-first engineering is no longer theoretical for us. It's measurable in speed, quality, and the way our engineers spend their time. We can now deliver full-stack engineering up to 30% faster, with more value delivered sooner across both our internal platforms and our clients. Our engineers are now able to focus on enhancements, value adds, and new features, with Microsoft GitHub Copilot now generating the majority of the boilerplate code in our platforms, which frees them to drive the future innovations.

Our Forward Deployed Engineering (FDE) business can now prototype with clients at a faster pace than before, helping to turn AI-first capability into tangible client outcomes on the ground.

Crucially, this speed has not come at the expense of quality or control. The standards and guardrails we embedded during adoption mean we can integrate new agents, models, and releases confidently and apply governance across the full software development lifecycle, not just the coding environment.

But the impact goes deeper than productivity metrics. We no longer hand-code everything. Microsoft GitHub Copilot now handles the bulk of coding development and first-reviews, freeing our engineers from repetitive work and transforming our innovation cycle. The most valuable shift: our engineers now spend more time alongside clients, designing better business outcomes, not buried in code. Embedding AI-first coding standards has enhanced both agility and control.

And finally, by capturing baseline metrics, we've been able to track progress and gauge return on investment with greater precision and insight.

The opportunity

We've walked the journey. Now we're ready to walk with you.

That's our advantage — and it can also be yours.

From technology selection and architectural decisions to governance frameworks, to the cultural and behavioural shifts that determine whether AI adoption succeeds or stalls, we've been through it. We know what works, what doesn't work, and why. Whether you're at the start of your AI-first journey or already in motion, we can help you move faster, avoid the missteps we encountered, and realise the full benefit of enterprise-grade, AI-augmented engineering. Talk to us about your AI-first engineering journey.

“The lessons we've learned from embedding Microsoft GitHub Copilot in our engineering and client teams go far beyond technology. They're about the skills, behaviours, and cultural shifts that determine whether AI adoption succeeds or stalls. We're now passing that experience on so our clients can move faster, avoid the missteps, and realise the full value of AI-first engineering.”

Ben Lingwood,Partner and CTO Tech Catalyst, PwC UK

“One thing we learnt early on is that it isn't purely a technology challenge; your engineering processes and team dynamics must shift too. Success with AI Coding Assistants is as much of a cultural challenge as it is a technical, risk, and commercial one. Forgetting to let your developers lead the charge is mistake number one.”

James Chorlton,Director and Engineering Leader in Tech Catalyst, PwC UK

Contact us

Ben Lingwood

Ben Lingwood

CTO, Tech Catalyst, PwC United Kingdom

Tel: +44 (0)7983 446723

Euan Cameron

Euan Cameron

AI and Emerging technology leader, PwC United Kingdom

Tel: +44 (0)7802 438423

Follow us