
How Forte Group helped a leading UK GovTech provider turn a stack of acquired platforms into one accelerating delivery engine, while serving 100 million citizens.
10× engineering capacity: 2 to 22 engineers in 6 months, zero disruption to live services
+32% sprint throughput in two quarters, with a shrinking backlog and predictable releases
50%+ faster integration of acquired platforms: from ~6 months to under 3
Client: A leading UK GovTech software provider (name withheld)
Industry: Public Sector / GovTech
Engagement: Dedicated nearshore engineering teams (Eastern Europe, full overlap with the client's UK teams)
Timeline: January–June 2025
Team: From a 4-person seed team to 22 engineers across 3 cross-functional squads
Our client grows by acquisition. Every deal brings a new product, a new tech stack and a new layer of technical debt. In January 2025, the company asked Forte Group to add engineering capacity fast, without putting live public services at risk.
Six months later, a 22-engineer nearshore team was running across three squads. Throughput was up 32%. Newly acquired platforms were integrating in half the time. And Forte Group had moved from vendor to strategic modernisation partner.
The client’s software runs services for more than 5,000 public bodies and over 100 million citizens, across local and central government, health and care, education, elections and justice. That scale is the result of steady acquisitions, and each one arrived with its own architecture, tools and habits.
The cost showed up in four places:
The business needed more engineers, quickly. But adding headcount to a fragmented system usually adds coordination overhead, not speed. The real ask was capacity that would raise the bar on architecture, quality and Agile delivery as it grew.
Forte Group ran four workstreams in parallel: seed the architecture, scale the squads, pay down debt, and unblock the roadmap. Each one came with a number to hold it to.
Day-one figure: architecture lead and senior engineers on board in Week 1, averaging 9+ years' experience.
Forte Group started with an Engineering Manager, two senior .NET engineers and an SDET. Their first job was to define architecture standards and delivery frameworks that every later hire would inherit. Because they fitted into the company's existing Agile practices rather than replacing them, the team was contributing to high-priority work from the first sprint.
Scale figure: 2 → 22 engineers in 6 months, across 3 domain-aligned squads.
Growth followed a deliberate sequence. Engineering managers and senior backend engineers came first, then front-end engineers and SDETs. The team organised into three squads: Product Modernisation, Platform Services and DevOps Enablement. Each squad worked as an "atomic" product team of 5–7 roles, led by an Engineering Manager alongside a Technical Product Owner.
All engineers are based in Eastern Europe, giving full working-day overlap with the client's UK teams. Coordination happened in real time, not in overnight handoffs.
Stability figure: legacy code refactored with zero disruption to live services.
A dedicated strike team mapped, prioritised and refactored the highest-risk legacy code. As it went, it added automated tests and CI/CD pipelines, so every fix also raised the quality floor. Modernisation ran alongside new feature work instead of waiting for it, which is how the company kept both moving.
Delivery figure: +32% sprint throughput in the first two quarters.
Forte Group shared roadmap ownership with the client's product leads. Fortnightly metrics reviews tracked scope, quality and velocity, so blockers surfaced early and decisions were made on data. Plugged directly into the client's product planning, the squads cut cycle time, unblocked stalled releases and brought Agile quality gates to every team.
In six months, the client gained a team ten times larger and a delivery engine measurably faster, with no impact on the services citizens rely on.
Beyond the numbers:
↗️ Architecture before headcount.
Senior engineers set standards in Week 1, so every hire after them scaled the system rather than fragmenting it further.
↗️ Debt and features in parallel.
The strike team modernised legacy code while the squads kept shipping. Neither waited for the other.
↗️ Shared numbers, every two weeks.
Fortnightly metrics reviews with the client's product leads kept scope, quality and velocity visible to both sides.
.NET, SQL Server, Azure (IaaS and PaaS), RESTful APIs, a proprietary front-end design system, Azure DevOps CI/CD with automated test suites, infrastructure-as-code, containers.