HMRC Signs 15-Year CRM Deal with Salesforce

What happened

HM Revenue and Customs (HMRC), the UK's tax and customs authority, has signed a 15-year customer relationship management (CRM) agreement with Salesforce, according to reporting from UKAuthority.

The deal sets a long-term commitment to a single CRM platform for the department. The reporting reviewed does not give the contract value, the scope of the modules covered or the exact signing date, so those details should be confirmed with the primary sources before they are relied on.

Why it matters

A 15-year term is a long horizon for any software commitment. It suggests HMRC is treating CRM as core operating infrastructure rather than a short-cycle tool. For an authority that handles very large volumes of taxpayer contact across several channels, the platform shapes what a case officer can see, how quickly a query can be resolved and whether a taxpayer has to explain their situation again. Long contracts also lock in data models and integration patterns, so the design decisions made at the start carry as much weight as the licence itself.

For digital transformation leaders more broadly, the announcement reflects a wider pattern in public-sector modernisation, where a small number of enterprise cloud platforms increasingly anchor service delivery. That brings speed and consistency, but it also raises questions about concentration risk, data portability and ongoing service design. The procurement event is the start of that work, not the finish.

The Renascence take

Most coverage of a deal like this will focus on the vendor and the headline term. The more useful question is what the contract makes easy, or hard, to change later.

The headline is the length of the contract, but the real decision is the operating model it locks in: how case data is structured, which taxpayer journeys are designed around it, and who owns the experience when a process crosses team boundaries. Behavioural economics tells us that people, including overstretched officials, follow the path of least resistance, so the default configuration will shape service quality more than any service charter will. A customer-obsessed operator in this position should map the highest-volume taxpayer journeys before configuration begins, treat repeat contacts as the primary success measure, and write exit and data-portability requirements into the operating plan now rather than in year twelve.