Over the past few years, I’ve personally sat through at least 100+ digital transformation presentations with state leaders, most notably CIOs. They all end the same way: polite nods, but sadly no action.
I know the reason is NOT because CIOs lack vision, and it’s definitely NOT because they don’t understand the urgency. It’s because “digital transformation” has become vendor code for “expensive, multi-year, risky.” The phrase itself has lost all meaning in my opinion.
What if the problem isn’t the CIOs’ ambition? What if the problem, frankly, are the impossible options they’re given?
What You’ll See at NASCIO Midyear 2026
NASCIO Midyear gets underway April 26. The floor will be packed with “transformation” promises. Everyone will have a platform. Everyone will promise everything. Read through to the end of this blog to find out the three questions you need to ask each one of the vendors you meet on the show floor.
The False Choice
Every state IT leader faces the same trap. You need to modernize resident/citizen/student services. You know it. Your governor knows it. Your constituents are demanding it. But you’re stuck between two options that don’t work: “Build” or “Buy”?
The Build Trap
Let’s be honest… you don’t have an army of cloud engineers, full-stack developers, and data scientists sitting around waiting for projects. Even if you did, a custom-built unified services app for constituents is an 18-24 month undertaking.
By the time it launches, agency priorities have shifted. Half of your team has turned over. The legislative mandate that drove the project has been replaced by three new ones.
Cost before residents see anything? $2-5M+. Minimum.
The Buy Trap
Then the Commercial-Off-the-Shelf (COTS) vendor shows up with “the platform” or “the product.” The one that does everything. License costs: $3-7M.
The promise: “Everything you need, out of the box!“
The reality: You end up using 7-10% of the functionality. The rest sits there, costing you annual maintenance fees for features you and your stakeholders never touch.
Worse yet, it doesn’t integrate with your actual systems. Your Department of Transportation still runs on AS/400. Social Services is on Oracle 10g. The DMV has that custom system someone built in 2003 that nobody fully understands, but everyone depends on.
The integration costs weren’t in the initial quote. The timeline doubles. The pilot stalls in configuration hell. The license becomes shelfware. And then your team moves on to the next crisis.
The Real Problem
Neither option is built for these state government realities:
- Constrained budgets – You’re not AWS. You’re not Google or Microsoft. You have real fiscal constraints and legislative oversight.
- Legacy systems that aren’t going anywhere. (Arguably… should they? That’s a topic for another blog!) -That mainframe processing unemployment claims? It works. It’s reliable. Replacing it is a $50M, five-year gamble nobody wants to take.
- Small, overworked IT teams – Your people are excellent! They’re also stretched across 47 agencies, fighting fires to keep critical systems running.
- Political timelines – You need results before the next legislative session. Before the next election. Before the CIO who championed this retires and their replacement has different priorities.
The Reframe: Stop Transforming, Start Delivering
So here’s what I learned after implementing systems across countless agencies, universities, and school districts and then five years leading Growth and Advisory conversations in AWS’ Public Sector team: The goal was never “transformation.” It was TRUTHFULLY better end-userexperiences.
Residents don’t care about your cloud migration strategy. They care about renewing their professional license without taking a day off work. They care about checking their housing application status without calling six different agencies. They care about getting answers, not navigating bureaucracy.
Agencies don’t need to rip-and-replace. They need to incrementally improve specific services that matter to the people they serve.
The shift looks like this:
From: “Transform your entire DMV stack“
To: “Deliver a better Change of Address experience that federates data from your existing systems“
From: “Migrate everything to the cloud“
To: “Launch a unified housing application portal that works with your current agency databases“
From: “Replace all legacy systems“
To: “Modernize the resident-facing layer while legacy systems keep running underneath“
What this actually looks like in practice:
- Start with ONE high-impact service (housing application, benefit enrollment, occupational licensing, etc.)
- Use AWS-native components… not custom code from scratch, not massive platforms you’ll use 7% of
- Pre-configure for government patterns (security, accessibility, WCAG compliance, multi-agency data sharing)
- Integrate with your legacy systems via APIs (don’t replace them… just yet)
- Timeline: POC → Pilot → Production in 4-6 months
- Budget: Low hundreds of thousands, not millions
The Third Way: Solution Accelerators
There’s a third option that most vendors won’t tell you about because it doesn’t fit their business model. It’s what we’ve been building at Presidio specifically for this problem.
“Solution accelerators” are pre-built, cloud-native solutions designed for specific government and education use cases.
They’re not COTS… you’re not licensing software you don’t control, paying annual fees for features you don’t use, or waiting for the vendor’s roadmap to align with your needs.
They’re not custom builds… 70-80% of the work is already done. The patterns are proven. The components are tested.
Think of them as Lego kits for government services. Proven components you configure to your state’s specific needs.
Why They Work for State CIOs
Budget reality:
- $150K-400K to get to production (not $3M-7M)
- No multi-year license fees eating your budget
- You pay for AWS consumption, not hypothetical “enterprise seats” you’ll never use
Team reality:
- Your 3-person team can manage it (you don’t need 15 cloud engineers)
- Presidio architects guide the configuration (you’re not building from scratch)
- Knowledge transfer happens during deployment (not after the vendor leaves and takes all the expertise with them)
- In some cases managed services can bridge you until knowledge transfer completes
Timeline reality:
- Live pilot in 90 days
- Production-ready in 4-6 months
- Results before the next budget cycle
- Wins you can show legislators while momentum exists
Integration reality:
- Designed to work WITH your legacy systems, not replace them
- API connectors for common state platforms you may already have in place (i.e. Salesforce, Oracle, etc.)
- Data stays federated… you’re not migrating 30 years of records to “the new platform“
- Your mainframe keeps running; residents just get a better front door
Real Example: A Single Unified Housing Application
California AB 519 requires a unified housing application across eight different state agencies. Same resident, one application, eight different programs to check eligibility against.
Traditional approach? Either a $5M COTS platform that takes 18 months to configure, or a 2-year custom build that requires hiring a team you don’t have.
Solution accelerator approach:
- Pre-built AWS-native portal framework already exists
- Configure it for California’s eight specific housing programs
- Integrate with existing agency systems via API (HCD, DSS, HHS, etc.)
- Resident-facing pilot in 90 days
- Production-ready in six months
- Cost to production: ~$450K
The agencies keep their systems. The data stays where it lives. Residents get one place to apply. Done.
Other Presidio AWS Accelerators in Active Use
Human AI (HAI) Modernize: Legacy application modernization without rip-and-replace. Assess what you have, modernize what makes sense, leave the rest alone.
Presidio Captivate: AI video intelligence for public safety body cam footage, traffic cameras, university athletics. Search video by what’s actually happening, not by timestamp and a prayer.
Presidio Resonate: Intelligent media management for government video archives, legislative sessions, public meetings. Metadata lake that makes years of content searchable.
These aren’t vaporware. We can show them in action now.
Ask These Three Questions at NASCIO Midyear:
- “Can I see this working with a state’s actual legacy systems?” Not a pristine demo environment. Actual integration with real AS/400, Oracle 10g, whatever Frankenstein stack the agency actually runs.
- “What’s the timeline to a live pilot?” Not a proof-of-concept that sits in a lab. A live pilot with real residents using it. And be specific: “How many days from contract signature to residents using this?”
- “What’s the total cost to get ONE service live for residents?” Not just license fees. Not just Year 1. Everything… integration, configuration, training, AWS costs, pilot, production. One number.
The solutions worth your time will meet you where you are:
- They will work with legacy systems (don’t require replacing them)
- Deliver incrementally (one service at a time, not Big Bang)
- Fit state budgets (hundreds of thousands, not millions)
- Transfer knowledge to your team (not create permanent vendor dependency)
The Bottom Line
You don’t need transformation. You need better resident/citizen/student services, delivered incrementally, within the constraints of state government reality.
The states winning right now aren’t transforming everything. They’re picking one high-impact service, delivering it well, showing results, then moving to the next one.
They’re using pre-built “accelerators” that respect legacy reality! They’re showing residents tangible improvements in months, not years. They’re proving value before asking for the next budget allocation.
That’s not transformation. That’s simply execution.
Presidio will see you at NASCIO.
