Selling to State Government: A CIO's Playbook | Podcast

If you have ever tried to sell technology to a state government and felt like you were navigating a maze blindfolded, you are not alone. The budget cycles are long, the decision-making is layered, and the rules change from state to state. Most vendors never get a clear picture of how the machine actually works from the inside.

‍

Jim Weaver spent 37 years on the buying side of state government. He served as Chief Technology Officer for Pennsylvania, State CIO for Washington, and most recently as Secretary and State CIO of North Carolina at the cabinet level. He is a past president of NASCIO, the National Association of State CIOs. As of January 2025, he switched sides of the table as a national strategy advisor at Everpure.

‍

On this episode 10 of In Pursuit, Jim pulls back the curtain on what a state CIO actually does, how money moves through a state, how initiatives get formed and funded, and critically, how vendors can position themselves to win and how they get disqualified before they even know it. Watch the full episode here.

‍

What a State CIO Actually Does

Most people assume a state CIO manages IT. Jim is quick to correct that assumption.

‍

"It's not about managing IT. It's about focusing on the business objectives that need to be accomplished, not only from the governor's perspective, but your fellow cabinet members as well. Really at the end of the day, from a CIO perspective, it's about relationship building."

‍

The state CIO serves as the technology advisor to the governor, translating the governor's policy agenda into technology initiatives and bridging the gap between the executive branch and the legislature. Jim describes the governor as the CEO of a company and the legislature as the shareholders, the ones who authorize the funding needed to get things done.

‍

The blocking and tackling of keeping systems operational is real and demanding. But the strategic work is about enabling outcomes across a diverse set of cabinet agencies, each running its own complex business, each with its own funding streams and priorities. Understanding that dynamic is the starting point for any vendor trying to sell into state government.

‍

You Have Been to One State, You Have Been to One State

One of Jim's most important pieces of advice for vendors is also one of the most overlooked: every state is different.

‍

The organizational structure, the level of centralization, the enabling legislation, the relationship between the governor and the legislature, and the autonomy that individual agencies have over their own technology decisions all vary significantly from state to state. What works in Washington will not necessarily work in North Carolina. What is true of Pennsylvania's procurement process may be entirely different in another state.

‍

"You need to understand your enabling legislation. You also need to understand even with your enabling legislation, what you will be allowed to do and what you will not be allowed to do."

‍

Jim worked across three states with fundamentally different operating models. Pennsylvania was heavily centralized, with agency IT teams folded into the central IT organization. Washington was decentralized, with agencies operating more independently. North Carolina sat somewhere in between. Each required a different approach to building relationships, positioning initiatives, and winning budget.

‍

For vendors, the implication is clear: do not assume. Research the specific state you are targeting. Understand whether it is centralized or decentralized. Know who controls IT budgets at the agency level versus the central office. That context shapes every conversation you will have.

‍

How the Budget Cycle Actually Works

This is the section that most vendors have never heard explained clearly. Jim walks through the annual state budget cycle in detail, and understanding it is essential for knowing when and how to engage.

‍

The cycle begins in October, when agencies start developing concept papers or program revision requests covering big-ticket items, policy changes, and requested legislative changes. By December, agencies are finalizing their budgets and submitting them to the governor's budget office. January and February are when the governor's office assembles everything and prepares the administration's budget proposal, typically announced in a state address between February and April.

‍

From April through June, the legislature debates and passes the budget, ideally signed into law before the July 1 fiscal year start date. After the budget is passed, agencies go through a re-budget or certification process to align what they asked for with what they actually received.

‍

"Budget folks never really get a chance to cycle down. It's a continuous year-long process, wash, rinse, repeat."

‍

And then, just as the state budget cycle wraps up, the federal budget cycle creates another layer of uncertainty, particularly for agencies like health and human services that depend heavily on federal funding streams. A federal continuing resolution or budget impasse can directly affect what state agencies planned to spend, forcing them to slow, pause, or restructure initiatives mid-cycle.

‍

For vendors, knowing this cycle means knowing when to engage. If you are reaching out to a state agency in March or April, the budget for the coming fiscal year is already largely decided. The time to be in conversation about a new initiative is October through December, when concept papers are being written and priorities are being formed.

‍

How Initiatives Get Prioritized

Jim describes the most mature prioritization process he encountered during his career, which was in Washington State. Agencies submitted project proposals that were reviewed by a cross-agency team including portfolio managers and agency representatives. Each project was scored and ranked from one to one hundred across the entire state portfolio. The recommendations, whether to fund, partially fund, or not fund, were shared with both the governor's budget office and the legislative fiscal research team.

‍

"The legislative branch and the executive branch had the same baseline that we were all working from. It didn't allow agencies to go back-door into their oversight committees and say, hey, I need this."

‍

That transparency created accountability on all sides and made it harder for individual agencies to lobby for funding outside the formal process. It also meant that vendors who understood which projects were being prioritized at the state level had a significant advantage over those responding cold to RFPs.

‍

The lesson for vendors: follow the public record. Concept papers, governor's budget proposals, and legislative fiscal notes are often public documents. Reading them tells you what is being prioritized, what is being funded, and where there is a genuine appetite for new investment.

‍

The Role of Lobbyists and Government Affairs

Jim describes the lobbying community as the force. There is a good side and a bad side.

‍

On the good side, lobbyists understand key legislative stakeholders, know what is being discussed in budget caucuses, and can help vendors get dollars set aside for broad categories of investment. A lobbyist might, for example, help position a $25 million cybersecurity centralization initiative that then becomes a competitive opportunity for multiple vendors.

‍

On the bad side is when lobbying pushes for funding that is earmarked for a specific product rather than a category of need. When legislatures name specific product sets, it undermines the state's ability to negotiate good pricing and contract terms, and it puts vendors in a position where their competitive advantage disappears the moment the law is written in their favor.

‍

"Work with the public sector to enable the opportunities that feed into what the governor is trying to do. You're going to start making very quick friends and those relationships last forever when they know they have a strategic partner who's there to work with them, not the other way around."

‍

The vendors who build lasting relationships in state government are the ones who help agencies accomplish their goals, not the ones who try to lock in business through legislative maneuvering.

‍

The Mainframe as a Service Deal: A Procurement Case Study

Jim walked through one of the most instructive procurement examples from his career: moving North Carolina's mainframe environment from state-owned data centers to a managed cloud service through a vendor called Ensono.

‍

The decision was driven by several converging factors: aging hardware, agencies actively looking to migrate away from mainframe applications, the looming retirement of experienced mainframe staff, and the opportunity to move from capital expenditure to operating expenditure. Rather than locking the state into another long-term ownership model, Jim structured it as a service contract where the vendor took on the infrastructure risk.

‍

What made it work was not just the technology decision but the people decision. Staff who wanted to move with the vendor were enabled to do so. Staff who wanted to stay in state IT were given development opportunities to transition into new roles. Those who wanted to retire were honored.

‍

"It wasn't just moving the technology. It was also making sure that our personnel were accounted for in this process."

‍

The broader lesson for vendors pitching as-a-service models to state government: the technology conversation is only half the battle. The workforce conversation is the other half. Vendors who anticipate that and address it proactively will find fewer obstacles in the procurement process.

‍

NextGen 911: How a Large Multi-Vendor Initiative Gets Done

The NextGen 911 project in North Carolina involved migrating all 125 public safety answering points across 100 counties to a new technology infrastructure. It involved multiple vendors, significant funding complexity, and years of execution.

‍

Jim credits the success largely to how the initiative was framed from the beginning: as a technology project, not a political one. By housing it within the Department of Information Technology rather than treating it as a public safety policy initiative, the team was able to apply consistent technology governance across all 125 PSAPs and leverage shared funding streams that would not have been available otherwise.

‍

The project's resilience was tested during Hurricane Helene, which devastated Western North Carolina. Not a single 911 call from the affected region was lost. A call routing program where each region of the state designated a backup region to absorb calls automatically proved its value when towers went down and fiber lines were cut repeatedly during cleanup.

‍

"We did not lose a single 911 call that was made from Western North Carolina."

‍

For vendors working on large multi-jurisdictional government technology projects, the takeaway is that resilience and redundancy need to be built into the design from the start, not added after the fact. The state agencies that invested in that upfront were the ones that performed when it mattered most.

‍

AI in State Government: Promising but Not Without Risk

Jim is thoughtful about AI rather than evangelical. He sees real potential and real risk, and he is especially focused on the cost question that most AI vendors are not answering clearly.

‍

The consumption-based pricing models common in AI create genuine budget uncertainty for state government. When an agency's usage of an AI-powered service grows as the population it serves grows, the cost grows with it, and it is not always clear at contract signing what that cost trajectory looks like.

‍

"When we're looking at what's going on across supply chain and everything else, I don't know if we fully understand yet what the cost of this is going to look like down the road. And so that's where my hesitation comes in."

‍

His other core concern is data quality. AI is only as good as the data it accesses. In state government, where data is often siloed across agencies, inconsistently formatted, and built up over decades of legacy systems, the readiness of the underlying data is often the real barrier to AI delivering on its promise.

‍

His view on the human-in-the-loop question is grounded in his human services background. Even when a system can calculate an outcome automatically, there are times when a caseworker's judgment needs to override the algorithm. That capability cannot be designed out of government AI systems.

‍

For AI vendors selling into state government, these are the questions you need to be ready to answer: What does total cost of ownership look like at scale? How does your solution perform with imperfect or siloed data? And what does the human oversight model look like in practice?

‍

The Three Things Nothing Gets Done Without

Jim distills 37 years of state government experience into a simple framework that he calls the evil pitchfork: procurement, budget, and personnel.

‍

"Nothing gets done without people, the ability to go buy things, and funding. It's quite simple. If you can master those skill sets and understand how the funds move around, it makes your job a lot easier."

‍

For vendors, mastering those three dimensions from the outside is what separates the ones who win consistently from the ones who keep losing to incumbents or losing bids they thought they had. Know where the money is coming from and when it becomes available. Know who has the authority to approve a purchase. And know who the people are who will live with the decision every day, because they are the ones who will champion your solution or quietly kill it.
‍

=======================================

‍

This post is based on a recent episode of In Pursuit, featuring Jim Weaver, former State CIO of North Carolina, Washington, and Pennsylvania, and current national strategy advisor at Everpure. Watch the full episode for more on centralized versus decentralized IT models, mainframe modernization, and the NextGen 911 project.

‍