HM Revenue and Customs has defended its planned HMRC Salesforce contract worth up to £4.4 billion, arguing in an economic assessment published on 30 October 2026 in London that building an in-house platform would be too expensive, slow and risky for Britain’s national tax administration.
Key points
- HMRC released a summary business case outlining a 15-year strategy to replace more than 70 aging customer systems with commercial cloud software.
- The full programme carries estimated costs between £1.7 billion and £4.4 billion, including tax and a 40 percent optimism bias adjustment.
- Officials dismissed bespoke in-house software and multi-vendor integrations because of delivery hazards and coordination friction.
- The procurement comes despite government statements urging public bodies to curb reliance on major US software vendors.
The revenue authority set out its rationale in a newly published summary business case for the Enterprise Customer Relationship Management programme. The document sets out how the agency plans to modernise customer handling for 34 million citizens and five million businesses across the country.
HMRC published details of the commercial tender on 15 October, releasing a contract notice for software licenses and tools valued at up to £2.4 billion. That arrangement covers Salesforce products including Agentforce, Data Cloud and Experience Cloud, alongside data integration software from Informatica.
The broader programme carries an estimated 15-year lifecycle cost ranging between £1.7 billion and £4.4 billion. The top end of that bracket incorporates standard Treasury accounting rules, adding value-added tax alongside a 40 percent allowance for optimism bias to absorb typical civil service budget overruns.
Why HMRC rejected an in-house build
HMRC examined six delivery models before picking commercial software-as-a-service. Alongside keeping its existing systems, the department studied a multi-vendor setup that would join off-the-shelf tools from several specialist providers, as well as an internal project to build a dedicated tax management platform from scratch.
Officials rejected the multi-vendor option because of high integration complexity and the administrative difficulty of managing several independent software suppliers. They also dismissed commissioning an in-house platform, concluding that the development work carried excessive delivery complexity, financial expense and timescale risk.
Industry specialists have argued that modern automated analysis tools can extract business logic and workflows from legacy infrastructure far faster than manual engineering teams. HMRC must complete that mapping work anyway as it shifts workloads off older platforms, but the department decided that writing custom software internally created unacceptable disruption risks for tax collection.
The agency plans to commit budget gradually through structured delivery stages. Built-in review mechanisms across the project lifecycle are intended to control overall expenditure and give managers break points if implementation milestones fall behind schedule.
Projected savings and operational changes
HMRC expects the migration to yield substantial operational efficiencies once fully deployed. The department forecasts £815 million in direct savings across the first ten years by joining customer databases that currently sit across isolated branches.
Over the full 15-year duration of the programme, HMRC estimates gross cost reductions between £924 million and £1.25 billion, even after applying its 40 percent optimism bias deduction. The department expects these savings to come from retiring outdated custom interfaces in favour of automated workflows and shared records.
Salesforce said the platform will give tax officials a complete view of taxpayer interactions, speeding up query handling and lowering manual caseloads through automated tools. Frontline staff will manage taxpayer queries through a unified record rather than consulting independent databases for self-assessment, payroll and corporate accounts.
The migration remains technically demanding. Engineering teams must retire more than 70 distinct customer management systems, many of which depend on custom software architectures and legacy support contracts that date back decades.
The clash with domestic procurement policy
The scale of the expenditure has drawn scrutiny because of its contrast with wider government technology policy. Ministers have repeatedly told parliamentary inquiries that departments must diversify their technical architecture and curb reliance on US cloud providers.
In September, the government replied to the Science and Technology Committee’s report on public sector technology by stating that public bodies must make risk-based decisions that avoid single-supplier dependencies while securing value for money. The First Secretary of State and the Chancellor also wrote to cabinet colleagues urging departments to direct procurement spending toward British start-ups and scale-ups.
The HMRC award points in the opposite direction. By selecting a proprietary ecosystem from a US supplier for core tax collection, the department has locked Britain’s revenue administration into a commercial supplier for up to 15 years. The deal’s upper cost ceiling of £4.4 billion also dwarfs recent domestic tech programmes, including the £500 million set aside for the UK Sovereign AI Fund.
Outsourcing track record under fresh scrutiny
The decision to commit billions to an external software vendor follows a succession of troubled public sector technology contracts managed by private firms. Civil service outsourcing programmes have faced steady criticism over performance shortfalls and cost escalation.
In the pensions sector, supplier Capita secured a contract to modernise the civil service pension scheme, telling ministers in late 2025 that it would deliver a flagship automated pension platform. The company subsequently missed service targets, leaving thousands of scheme members facing payment disruptions.
Capita chief executive Adolfo Hernandez later told MPs in parliamentary evidence that the administration was “very complex; more complex than we thought, realistically.” Paymaster General Nick Thomas-Symonds told a committee hearing that studying an in-house model remained an option, but cautioned that building internal systems would “need a quite enormous state architecture.”
HMRC argues that buying mature commercial enterprise software remains the safest way to replace delicate legacy infrastructure. Parliamentary spending committees are expected to question tax officials in upcoming sessions to examine the economic model and check whether cost controls will hold the programme to its targets.
