From CRM systems to public service infrastructure: The end of software designed for users
The New Zealand government has set out a Digital Government Target State, setting direction for improved government digital services – moving towards a more customer-oriented approach. At the same time, agentic AI is transforming how citizens engage with government and businesses, with 64% of those surveyed saying they use AI tools on a weekly or more frequent basis. An example of this in action is people booking travel by expressing travel goals to chatbot, rather than navigating online travel booking systems. In this article we explore what government and digital trends mean for the future of Customer Relationship Management (CRM) in the public sector.
The future of public service users
For more than 30 years, enterprise software has been designed around a simple assumption: people use systems. Government and businesses have digitised service-by-service, often investing heavily in human-centred experience design for customers and staff. This has significantly improved access through individual channels.
The emergence of agentic AI has demonstrated that the assumption, people use system, no longer holds true. This represents one of the most consequential shifts in enterprise CRM technology in decades. For the first time, the user of a service may not be the user of the system.
Historically, citizens accessed services through websites, forms, contact centres and applications, while public servants relied on screens, records and workflows. Enterprise systems were therefore designed around human users. That model is changing as citizens increasingly use digital agents and public servants use AI to retrieve information, interpret cases, recommend actions and coordinate services.
Humans remain accountable for outcomes, but agents increasingly navigate systems on their behalf. Citizens still consume services and public servants still deliver them, yet AI agents may become the primary users of the CRM platforms enabling those interactions.
For government, this shift is not just about technology. It has implications for how systems are designed, delivered and governed. And it raises a more fundamental question: if agents increasingly use systems on behalf of people, what should we optimise our CRM platforms for?
The quiet decline of the user interface
For decades, enterprise software has been built around a human requirement: people need information organised before they can use it. Customer records, case views, dashboards, forms and workflows all exist to aggregate data, provide context and help people make decisions. Every design decision, from navigation structures to training models, has been shaped around that idea. The success of a platform was often measured by the quality of its user experience and adoption by these users.
The rise of digital agents shifts the value of enterprise systems from presenting information on screens to exposing trusted data, business rules and service capabilities that AI can use. Screens will remain important for oversight, exceptions, governance and accountability, but AI may increasingly perform tasks such as navigating records, interpreting case history and identifying next actions.
In that context, designing primarily for screens risks optimising for the wrong thing. The strategic asset is no longer the interface itself. It is the underlying service capability: trusted data, business rules, eligibility logic, workflows and governance controls that can be consumed consistently by people, applications and AI agents.
Organisations that invest primarily in front-end experiences risk rebuilding the same capabilities repeatedly. Organisations that invest in reusable service and data foundations are better positioned to adapt as new channels emerge.
The rise of the headless architecture: simplifying reusable service foundations
This is why the shift towards headless architectures is gaining momentum.
Headless architecture separates the front-end user interface (the “head”) from the back-end data and business logic (the “body”). Think about modern banking. The same payments infrastructure sits behind mobile banking apps, ATMs, EFTPOS terminals, online shopping checkouts and digital wallets. Customers experience each channel differently, but the underlying payment capability remains consistent. New channels can be added without rebuilding the core banking system. Headless CRM applies the same principle to service delivery, allowing a single set of trusted business rules, data and processes to support many different citizen experiences.
Headless CRM moves the centre of gravity away from the application layer and towards a service layer. It enables organisations to expose core capabilities as APIs (Application Programming Interface) and MCPs (Model Context Protocol) and services that can be used across multiple contexts, including digital assistants, contact centres, mobile applications and partner ecosystems.
None of this works without strong data foundations. A service can only be reused safely if the underlying data is trusted, governed and accessible. An agent can only make effective recommendations or complete tasks if it can draw on accurate and consistent information. Poor data that causes frustration for a human user, can be amplified at machine speed when consumed by digital agents.
In this environment, data is no longer simply an asset that sits behind applications. It becomes a strategic foundation for service delivery. The quality of the customer record, the consistency of service history, and the ability to connect information across systems become critical enablers of future service models.
For public-sector organisations, this is a structural shift. Headless architectures create the opportunity to separate service logic from the applications that consume it. Rather than embedding policy rules and eligibility decisions inside individual systems, organisations can expose them as reusable capabilities that support websites, contact centres, frontline workers and AI-enabled services alike.
Digital public infrastructure is about to expand
Governments have historically defined digital public infrastructure in terms of identity, payments, connectivity and data exchange. In a future where citizens interact with services through digital assistants as well as websites, the workflows and business rules themselves begin to look like infrastructure.
The ability to determine eligibility, coordinate service delivery, manage cases and orchestrate decisions becomes central to how services operate at scale. These are not just siloed application or agency features, they are capabilities that can be shared, reused and standardised across government.
Agencies have traditionally procured CRM systems as standalone applications. Each system embeds its own version of workflows, rules and logic, even where those capabilities are fundamentally similar across organisations. That model becomes harder to sustain in an environment where services need to be integrated, responsive and increasingly personalised.
The next generation of digital public infrastructure is therefore unlikely to be defined by a single front door or portal. It is more likely to consist of a set of shared service capabilities that can be consumed dynamically by citizens, public servants, partners and AI agents.
There is a real risk that organisations respond to AI by layering it onto existing CRM implementations, without reconsidering the underlying architecture. AI cannot compensate for unclear rules, disconnected data or duplicated processes, but it can amplify them.
An alternative is to rethink CRM as part of a composable service-delivery foundation. In this model, CRM is not simply a front-office system. It is part of the infrastructure that enables consistent, coordinated service delivery across agencies and channels.
CRM is becoming public service infrastructure
We believe the future of CRM lies beyond the application itself. As services become more digital, connected and AI-enabled, CRM is evolving from a system of engagement into part of the service-delivery infrastructure. Its value comes not from the screens it provides, but from the capabilities it exposes.
For public sector leaders, this changes the investment question. The pace of technological change means today's interfaces are unlikely to be tomorrow's. This means less emphasis on investing in the "right" channel or technology, and greater emphasis on ensuring the underlying service capabilities can evolve as citizen expectations and technology continue to change.
Our view is the agencies that will realise the greatest long-term value will be those that prioritise trusted data, reusable service capabilities and transparent governance and policy logic. These foundations provide flexibility to adopt new technologies and channels as they emerge without needing to repeatedly redesign core services whilst delivering on the operating imperative of the public sector: trust and confidence.
For government leaders, this changes the investment conversation from “Which CRM platform should we buy?” to “What capabilities do we need to deliver services consistently, safely and flexibly, regardless of how people choose to access them?”
The payoff: faster, fairer, more flexible services
The prize is not just a more modern CRM estate. It is a public service that can implement policy changes faster, provide more consistent and equitable experiences with transparency, reduce duplicated investment, and adapt to new technology without repeatedly rebuilding its foundations.
The organisations that act now will be able to add new channels and digital agents without recreating the machinery of service delivery each time. Those that continue to embed data, rules and processes inside individual applications risk making every future change slower, more expensive and harder to govern.
Before investing in the next CRM interface, government leaders should ask three questions:
- What service capabilities should we build once and reuse everywhere?
- What surrounding investments are required to make those capabilities trusted, connected and safe?
- Will today’s decisions expand or constrain our options when the next technology shift arrives?
The future of CRM is not another screen. It is the trusted service infrastructure behind every screen, worker, partner and digital agent.
