Practice 01

ERP Implementation

Modern platforms for finance, HR, and utility billing.

Municipal ERP projects fail more often than they succeed. We run them differently: vendor-neutral selection, ruthless scope discipline, and change management that keeps line staff on board through go-live.

Discuss this practice

Outcomes

What success looks like.

  • Consolidated financial and operational data on one platform
  • Faster monthly close and audit-ready reporting
  • Retired legacy systems and reduced vendor sprawl
  • Trained staff who own the platform after handoff

Deliverables

What you receive.

  • Current-state assessment and data mapping
  • Vendor-neutral RFP and scoring model
  • Chart of accounts and workflow design
  • Data migration plan and validation harness
  • Cutover runbook and hypercare support

Engagement model

How we work together.

Fixed-fee discovery followed by milestone-based implementation, typically 9–18 months.

Ideal for

Who we serve.

  • Cities replacing legacy financial systems
  • Utilities modernizing billing and CIS
  • Counties consolidating disparate departmental tools

FAQs

Questions we hear most.

Straight answers on scope, timeline, staffing, and cost — the same ones we give in the first procurement conversation.

How long does a municipal ERP implementation take?
Most city and county ERP implementations run 9–18 months from kickoff to go-live, depending on module scope, data quality, and the number of departments involved. We stage utility billing, payroll, and finance cutovers separately so risk stays contained.
Are you tied to a specific ERP vendor?
No. We are vendor-neutral and have deployed Tyler, OpenGov, Workday, Oracle, Infor, and CentralSquare. Our selection process scores platforms against your workflows, procurement code, and total cost of ownership — not our commissions.
What happens if our legacy data is a mess?
That is the norm, not the exception. We build a data validation harness during discovery, reconcile balances and master data with your finance team, and stage migrations so you can compare legacy and new-system reports side by side before cutover.
Can you help write the RFP before implementation begins?
Yes. Many clients engage us first for a fixed-fee discovery and RFP engagement, then bring us back for implementation oversight once a vendor is selected. Both phases can also be procured separately for jurisdictions with strict conflict-of-interest rules.
How do you keep staff engaged through go-live?
Change management is scoped from day one — role-based training, super-user networks, and hypercare desks staffed by our consultants alongside the vendor. We measure adoption post-go-live and revisit training until it sticks.

Next step

Let's talk about erp implementation for your agency.

Start a conversation