Industry
Professional services
Featuring
Microsoft GitHub Copilot
What we learned
First-hand experience embedding AI into engineering at scale
Nearly 1,000 engineers and technologists in our AI-first centralised engineering capability business unit, part of a broader PwC engineering network
faster full-stack engineering delivery
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.
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.
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.
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.
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