The Readiness Gap: Why Technology Is No Longer the Hard Part for Canadian Municipalities
Municipal technology projects rarely fail at go live. They fail about eight months later, quietly, when the reports still don't answer the question anyone actually asked, when half the team has drifted back to the spreadsheet, and when nobody can quite say what changed. We've seen it often enough to argue that the real constraint in local government has moved. It isn't what the technology can do anymore. It's whether the organization has the process clarity, the data and the capacity to absorb it.
Across the municipalities we work with, the same handful of pressures keep surfacing: doing more with a tighter budget, meeting resident expectations shaped by their banking app rather than their old service counter, and protecting systems that were never built to withstand this kind of threat. Presented that way they read as separate budget lines competing for the same envelope. Look closer and each one turns on the same underlying question, which is whether the organization is set up to use what it already has. That makes them readiness problems before they become purchasing problems.
Cost management is a readiness problem, not a spending problem
It isn’t really about spending less. Most municipalities can tell you what they spent. Far fewer can tell you what a service actually costs to deliver, because the answer is scattered across a finance system, a payroll system, three spreadsheets and one person's memory.
When a treasurer can't produce that number quickly, budget season becomes a negotiation about last year plus inflation. Council asks a fair question and gets an approximation.
The same gap shows up in procurement. Technology purchases usually start with a decision to replace a system rather than a decision about what the organization wants to do differently. The RFP that follows describes the system they already have, vendors each interpret it their own way, and the bids come back looking impressive and impossible to compare on anything that matters. The evaluation turns into a judgment about which demo felt best, and the real cost of the project gets discovered during implementation.
Residents aren't comparing you to the next town over
Residents already compare a permit application to their banking app, whether or not the municipality has caught up to that expectation. They expect to apply at 9pm, see where it sits, and not have to phone anyone to find out.
Most municipal websites were built to publish information and were later asked to deliver services. They're doing a job they were never designed for, and staff absorb the difference by answering the phone. The fix starts with deciding which services actually need to be online and what a resident should be able to do without help, not with a redesign.
Hamilton's $18.3 million bill landed on taxpayers
Cybersecurity and privacy is tightening from a background concern into an active one. The Canadian Centre for Cyber Security recorded a 26% average year-over-year increase in ransomware incidents reported to it between 2021 and 2024, and continues to flag critical infrastructure as an attractive target for attackers looking to disrupt services people depend on.
Hamilton is the case every Canadian municipality should read. On February 25, 2024, attackers disabled roughly 80% of the city's systems and demanded $18.5 million. The city refused to pay. Recovery has since cost $18.3 million. The city submitted roughly $5 million in insurance claims and the insurer denied all of them, citing a policy exclusion for any loss where the absence of multi factor authentication was the root cause. A third party review confirmed the denial was consistent with the policy terms, and Hamilton taxpayers are covering the full cost.
The detail that matters most for everyone else is what never came back. The city's finance business management suite, development and permit applications, licensing, fire department records management, public health inspections, traffic signal systems management, museum collections and utility locates were all unrecoverable. Prevention failing is one problem. Being unable to restore the systems afterward is a separate problem, and it's the one that decided how long residents felt the impact.
The AI numbers are where it gets uncomfortable
A 2025 KPMG survey of Canadian public sector organizations found that 48% of public servants are already using AI in their work, while 85% rate AI literacy across the public sector as low and 60% say they’ve had no data literacy training at all. Only 22% of organizations have formally implemented AI tools, which means most of that hands-on use is happening ahead of, not because of, any organizational rollout.
Staff are already using these tools, whether or not the organization has caught up with formal training or policy. AI is already in the organization. The open question is how much guidance it arrives with.
Capacity is the resource nobody budgeted for
This is the finding that sits underneath everything above it. In nearly every municipality we work with, leadership already knows change fatigue is real. Very few have a formal, organization-wide reskilling strategy, and fewer still take a proactive, data-driven approach to workforce planning. It tends to happen department by department, project by project, whenever the pressure gets high enough to force the conversation.
You have organizations that know they need to change, broadly agree on what needs to change, and are running short on the one resource change actually costs, which is people's capacity to absorb it. Buying more technology into that environment doesn't relieve the pressure. It adds to it.
How Perry Group can help
Readiness looks different depending on which of these a municipality is facing. In each case the work that shapes the outcome happens earlier than most organizations plan for, well before a contract is signed or a system goes live. Some of that work is what we do.
On cost, the decisions that determine what a project ends up costing are made during planning. We help municipalities define what they actually need, then build the RFP and procurement process around that definition, so the bids that come back are comparable and the price quoted reflects the scope that will actually be implemented.
Customer service work runs on two tracks. We review the processes behind a service to find where residents get stuck and where staff absorb the friction. We also design and deliver municipal websites, which for most communities is now the main way residents interact with their local government. Getting that experience right does more for how service quality is perceived than almost anything else a municipality can spend on.
On cyber security and privacy, we help municipalities strengthen how systems and data are protected. The area where we add something distinct is business continuity planning. That means confirming your data is genuinely backed up, that critical systems can be restored, and that the organization knows how it will keep delivering services while recovery is underway. Hamilton shows the distance between having security measures in place and being able to bring a service back. Continuity planning is the discipline that closes it.
With AI, we've built a framework we use with municipalities that goes well past tool training. It covers where AI makes sense for your organization and your community, which guardrails belong in place before staff start using it, and the policy and governance that lets people experiment with confidence.
See the full range of our services at perrygroupconsulting.ca, or get in touch to talk about where your organization sits today.