By the time a modernization request lands in front of a committee, it’s usually too late to build a good case for it. Budget season crush pushes agencies toward a rushed pitch built on urgency instead of evidence, and rushed pitches are easy to say no to. The agencies that actually get funded did the groundwork months earlier, and most of them wouldn’t have called it “budget prep” at the time.

Why the ask stalls before it’s even submitted…

Here’s a strange finding worth sitting with. A 2025 EY survey of state and local IT leaders found 71% think modernizing their legacy systems cost too much, and 71% think staying on those same systems costs too much. Same people, same survey, both directions at once. That’s not indecision. It’s a sign the conversation itself is broken. Once “too expensive” is true of every option on the table, it stops being useful information, and a budget request that leads with cost is like walking straight into a wall.

It doesn’t get easier after the money is spent either. Deloitte’s review of ERP-related language across a decade of financial filings found 69% of business leaders hold a negative or neutral view of their own ERP investments. Ask why, and a big part of the answer is that almost nobody measured the “before.” A 2012 survey of GFOA members found finance officers were, in the survey’s own words, “quite glum” about their ability to measure ERP costs and benefits at all, and that problem hasn’t aged out. If most organizations can’t prove their last technology paid off, the next request is going to get a skeptical review.

What to actually build before you ask

The fix isn’t a better slide deck. It’s deciding, before you ever request money, exactly what you’re going to measure, then writing down what the current process costs today so you have something to compare against later.

Pick something specific. Days to close a budget cycle. Hours spent reconciling by hand each month. The size of a permitting backlog on a given date. Measure it now, while the old process is still the one everyone’s stuck with, because six months after go-live nobody remembers how bad it actually was.

Then price out the full run, not just year one. GFOA’s own capital planning guidance is blunt about this: “the ongoing life cycle costs associated with each project should be quantified, and the sources of funding for those costs should be identified.” A request that only shows the first year’s numbers is setting up a fight two years from now, when the renewal bill lands and nobody budgeted for it.

If the internal pushback feels personal, it probably isn’t. A ClearGov survey of local government finance leaders found 60% named modernizing inefficient systems their top investment priority in the current budget climate. Most finance departments are stuck in the exact same spot yours is.

What a credible case actually looks like

Utah’s technology efficiency program is a decent model here: over 12,000 staff hours saved and $7.7 million in documented cost savings, plus another $9.8 million in service improvements delivered at no added cost. Notice what that isn’t? It isn’t “the new system improved efficiency.” It’s a specific hour count and a specific dollar figure, checked against a process that existed before. That’s what survives a budget hearing. “Trust me, it’s worth it” doesn’t.

The timing matters more than people think

Most local governments run a fiscal year starting July 1, which puts internal budget requests somewhere in the fall, months before a council ever sees the line item. If that’s your calendar, this work needs to start now. Measuring the “before,” pricing out the multi-year cost, lining up the reassurance data; none of it happens in the two weeks before the request is due, which is usually when most people start.

None of this guarantees funding. It just means showing up with a number the committee can check, instead of a feeling they have to take based on trust.

Interested in learning more about how we do it? Contact us to schedule a conversation!

__________________________________________________________________________________________

– EY, *2025 Government — State and Local Survey Findings*
– Deloitte, *Maximizing ERP Market Value*
– Microsoft & GFOA Consulting, *The Real Impact of ERP Systems in the Public Sector* (2012)
– GFOA, *Multi-Year Capital Planning* 
– ClearGov, *Innovation During Inflation* 
– Route Fifty, *As budgets tighten, states double down on efficiency and tech innovation* (2026) 

GovSense is the first complete cloud solution purpose-built for local governments, empowering over 60 communities and supporting more than 2 million citizens. Govsense built on Oracle NetSuite—the #1 true cloud ERP platform with over 50,000 customers worldwide— GovSense delivers a modern, unified system that streamlines operations, enhances transparency, and drives efficiency. GovSense’s team has been implementing cloud solutions since 2005, bringing over two decades of expertise in delivering scalable and secure technology for local agencies. As a five-time GovTech 100 recipient, we are recognized as an industry leader in transforming government technology. GovSense is one modern platform that has everything you need for your local government, ensuring your community is equipped with the tools to thrive in the digital age.