“We shouldn’t need three versions of the same data just to answer a basic question.”
For many public sector leaders, that frustration feels all too familiar. Enterprise resource planning systems were designed to bring consistency, visibility, and control to operations. Yet over time, as services evolve and expectations change, those systems are often stretched beyond what they were originally built to support.
Modern public sector work doesn’t stand still. Budgeting methodologies change. Residents expect digital services instead of in person transactions. New regulations reshape reporting and compliance requirements with little warning. When core systems can’t adapt easily, teams find ways to keep work moving — through spreadsheets, side systems, and manual workarounds that sit outside the ERP.
In these situations, the issue isn’t always that the ERP has failed. More often, a single, rigid system is being asked to support services, workflows, and outcomes that didn’t exist when it was first implemented. Modernization doesn’t always require replacing everything at once. Sometimes, progress starts with understanding where flexibility is needed most — and where smaller, more intentional changes can better support how work actually gets done.
An assessment of your ERP can show where the platform still operates as intended and where work is consistently happening outside the system to keep moving. Your assessment result isn’t an answer, but a path forward. In many organizations, that evaluation reveals a common pattern where stability is still needed at the core of the technology, but flexibility is required in areas that are subject to change more often. So, when a single platform can’t support both flexibility and change, where should leaders look next?
From ERP assessment to strategy: Building the roadmap
Public sector work rarely moves in straight lines. Regulations change midyear, reporting requirements tighten unexpectedly, and funding windows open and close with little warning. An assessment helps identify where the system needs more flexibility and turns those findings into a roadmap grounded in what needs to change.
Moving from results to strategy means deciding where flexibility matters and where to change accordingly. Here’s how public sector leaders can approach it:
- Identify mission-critical capabilities. Map the core functions your specific agency relies on. Consider how those functions enable transparency, compliance, and service delivery. These should drive your ERP strategy, not legacy processes.
- Assess gaps and integration needs across departments. Identify where the system struggles to support diverse functions — such as public health, utilities, budget development, and community development. Determine where specialized tools may be needed to support their objectives.
- Prioritize based on public value and risk. Rank priorities by their impact on service delivery, compliance, and fiscal responsibility. For example, improving grant management or procurement transparency may deliver higher public trust than automating a low-impact internal process.
- Implement modular solutions with strong governance. Adopt modular, API-driven solutions that allow flexibility without sacrificing accountability. Establish governance frameworks to ensure interoperability, data security, and adherence to public sector regulations.
For some organizations, the roadmap points to modular, composable capabilities that can adapt without overhauling the platform.
A best-of-breed approach
Composable ERP is one approach that addresses this challenge. While composable ERP introduces greater flexibility, a fully integrated platform offers the advantage of seamless data flow and consistency across all modules. The choice between a fully integrated system and best-of-breed modular solutions ultimately depends on what your organization values most — unified integration across departments or specialized, deep functionality in key areas. Composable ERP allows agencies to keep what’s working in their system while introducing best-of-breed capabilities to implement change.
Individual capabilities, like financials, procurement, permitting, and billing can operate independently while remaining connected to the whole. That means agencies are able to adjust one component without destabilizing everything else. The system doesn’t have to be perfect everywhere at once. It needs to be adaptable where the work is changing most. Composable ERP is characterized by its modular, API-driven, and cloud-based framework that enables flexibility, supports faster innovation, and allows seamless integration with modern tools — like AI, advanced analytics, and cloud applications.
Consider this example: Cities have implemented a utility billing module within their legacy ERP system to keep all data in one place. While this seemed efficient at the time, it locked them into an inflexible model with limited ability to connect to other systems. Later, when they introduced a modern work order system, they couldn’t easily determine whether completed maintenance reduces water loss or improved billing accuracy. What was the result? Missed opportunities for insight and confusion on delivery simply because the ERP couldn’t adapt.
So, if alignment to organizational goals, not configuration to follow a legacy process, is the measure of success, how do leaders prioritize what to change first?
Moving toward a platform that supports change
Public sector organizations are constantly balancing stability with change. Core financial controls, compliance, and reporting need consistency. At the same time, service delivery models, regulations, and community expectations continue to shift — often faster than a traditional ERP replacement cycle can accommodate.
A composable ERP approach recognizes that reality. By keeping what’s working and introducing targeted, modular capabilities where change is happening most, organizations can evolve their systems without destabilizing their foundation. The goal isn’t customization for its own sake, but alignment — ensuring technology supports the services and outcomes the organization is responsible for delivering today.
An ERP assessment doesn’t provide a single answer; it provides direction. It helps leaders see where the system still serves its purpose, where it’s creating friction, and how to sequence change in a way that’s manageable and intentional. With a clear roadmap and the right governance in place, agencies can move forward with confidence — improving systems in smaller, meaningful steps that keep pace with the work they do and the communities they serve.
