I spent more than three decades in government IT, across three states, and if there’s one thing that never changed, it’s this: Budgets in the public sector don’t move like budgets in the private sector. They move with legislative sessions, continuing resolutions, and appropriations that arrive late, arrive in pieces, or don’t arrive at all until everyone’s patience has run out. Any CIO who’s lived through a biennial budget cycle knows what I mean. Against that backdrop, the old way of buying storage — size it for five years, ask for the capital up front, hope the forecast holds — never made much sense to me. Storage as a Service is a much better match for how government actually has to operate.
The appeal is simple. Instead of guessing what you’ll need five years out and asking the legislature to fund all of it today, you pay for what you’re using now and add capacity as the mission requires it. I always found that a much easier conversation to have with budget staff than trying to defend a five-year capacity forecast I only half-believed myself. Overbuy, and you’ll hear about it in the audit. Underbuy, and you’re the CIO explaining to an agency director why the system can’t keep up. A consumption model doesn’t eliminate that tension, but it gives you room to adjust instead of locking in a guess.
That flexibility matters most when funding is unpredictable, which in my experience was most of the time. Continuing resolutions, delayed appropriations, a legislature that changes a program’s mandate mid-year — none of that is unusual, and none of it waits for IT to catch up. A large capital purchase assumes a level of budget certainty that state and local government rarely has. Storage as a Service takes that assumption out of the equation. The question stops being “how much can we afford to buy this year” and becomes “what do we need right now, and how do we grow it responsibly.” That’s a question I could actually answer with confidence, year to year.
There’s a real financial benefit too, and it’s not just about which column the spending lands in. A steady operating expense is easier to plan around than waiting for the one funding event every few years that lets you do a wholesale refresh — the technology equivalent of a bond issue. I sat through enough of those cycles to know how disruptive they are: You wait for the stars to align on budget and procurement, and in the meantime the old infrastructure just keeps aging. Smoothing that spending out helps IT and finance actually plan together instead of IT showing up every few years asking for a large check.
It also changes how modernization happens day to day. In the environments I ran, upgrades too often waited on that rare alignment of budget cycle, procurement timeline, and hardware end-of-life — and by the time it all lined up, the infrastructure had aged well past where anyone wanted it. Modernization became a big, high-risk event instead of routine work. Storage as a Service lets you modernize in smaller steps, adding capability as you go rather than betting everything on one large appropriation. In government, I’d take steady and incremental over a single high-stakes purchase every time.
But I don’t think of this mainly as a procurement fix. The bigger value is resilience. Government workloads don’t arrive on a predictable schedule — elections, emergencies, a new policy mandate, a cybersecurity incident, a surge in citizens needing a service all at once. I’ve been on the other end of those calls, and the last thing you want is infrastructure that can’t flex when the state needs it most. A consumption model lets capacity move with the mission instead of against it, which is exactly what agencies need when circumstances shift fast.
That makes flexibility a resilience strategy, not just a financial preference. When agencies can scale without delay, avoid prolonged procurement bottlenecks, and maintain current infrastructure without waiting on major capital approvals, they are better positioned to support continuity of operations. They can respond faster, recover more confidently, and plan with greater realism. In this sense, Storage as a Service aligns directly with one of the government’s most important responsibilities: maintaining dependable service in spite of volatility.
Looking back on my time as a state CIO, I’d put it this way: The question isn’t whether storage can be delivered differently. It’s whether the old capital-purchase model still fits how government actually operates. It doesn’t, not anymore. Storage as a Service replaces rigid capital cycles with scalable consumption, turns spending into something predictable, cuts down on disruptive refresh events, and — maybe most importantly — turns flexibility into resilience.
That is why Storage as a Service is not just a new procurement option. For the government, it is increasingly the better fit.
For state, local, and education leaders thinking through what that looks like in practice, see additional resources on modernization, cyber resilience, and building a more predictable data foundation.
Jim Weaver is a former state CIO and nationally recognized public-sector technology leader with deep experience guiding government IT strategy, modernization, and cybersecurity initiatives. He served as Secretary and Chief Information Officer for the North Carolina Department of Information Technology, where he oversaw statewide IT strategy, procurement, cybersecurity, and broadband expansion. Prior to that, he served as CIO for the state of Washington, helping strengthen the state’s IT infrastructure and advance technology adoption across government. Jim also served as president of the National Association of State Chief Information Officers (NASCIO), contributing to IT policy and collaboration nationwide.
Leave a Reply
You must be logged in to post a comment.