Smart City Pilot Programs in Mid-Size American Cities
Mid-size cities show that smart programs last only with owners and budgets.

Smart city programs in mid-size American cities test whether technology can become dependable public infrastructure. Their success depends less on visible deployments than on cloud infrastructure, shared data standards, stable operating budgets, and institutions that can sustain services after federal grants expire. The strongest evidence comes not from what cities launch, but from what they can keep operating for public benefit.
Mid-Size Cities Test Smart City Viability
Municipalities of 100,000 to 500,000 residents face deteriorating infrastructure, limited IT staff, and pressure to improve services. Those constraints make them a meaningful test of smart city viability. Technical performance is only part of that test. A system must also fit the people, funding, and older infrastructure a city actually has, rather than depend on resources available only during a demonstration.
New York, San Francisco, and Los Angeles have resources, political clout, and proximity to technology companies that few municipalities can match. In a mid-size city, the question is whether a tool can become ordinary municipal infrastructure without requiring exceptional support. That shifts the standard of success from the sophistication of a deployment to its place in everyday service delivery.
Cloud Migration Comes Before Advanced Analytics
Most current smart city work in mid-size municipalities involves moving legacy platforms to hosted environments and unifying departmental data. Relocating an ERP from local hardware to hosted infrastructure qualifies as a smart city investment because it creates access, interoperability, and protection needed by later tools. Shared data standards also help make departmental information usable beyond the system in which it originated.
The four-layer framework makes the sequence explicit. The first layer consists of sensors and meters that collect raw input. The second has cloud platforms and API gateways that link the information together. In the third, analytics and AI turn that information into actionable insights, while the fourth, operational response, applies the findings. Mid-size cities are largely building the first two layers, with analytics beginning to appear. Their visible equipment can therefore understate their progress toward more sophisticated services.
Federal Funding Sets The Deployment Pace
The Inflation Reduction Act and the Bipartisan Infrastructure Law required cities to meet smart technology mandates to get funds for grid modernization, resilient infrastructure, and broadband expansion. Such requirements can shape deployments before a municipality has its own smart city plan. Whether a project qualifies for funds helps decide what it covers and when it goes ahead. The U.S. Department of Transportation’s SMART Grant program, for example, pays for Smart Curb Buffalo’s curbside work, but money to get started does not by itself cover the costs over time.
Other support changes the speed of experimentation. Leading Cities’ AcceliGOV program, offered through the Clinton Global Initiative, provides fully funded municipal pilots worth $50,000–$100,000 each. Its roughly 90-day rollout contrasts with a traditional RFP process that typically takes 18–24 months. Yet speed and eligibility can orient projects away from resident needs if funding opportunities define the agenda. The proposed 2025 Smart Cities and Communities Act would authorize support for 2026 through 2030 for small cities, midsize municipalities, counties, and Tribal governments, but Congress has not passed it.
Columbus Separates Deployment From Civic Value
Columbus received $40 million from the federal Smart City Challenge to serve as a midsized testing ground. Its initial transport experiments produced uneven results. The program’s closing report revealed scant uptake of Pivot, a driverless shuttle halted after a passenger was hurt, negligible rides from Smart Mobility hubs, and an abandoned truck platooning effort.
Coordinated funding involving the City of Columbus, Franklin County, ODOT, Ohio State University, and additional partners supported commercial growth and generated thousands of employment positions. After federal funding ended, Smart Columbus became a 501(c)(3) that the city and Columbus Partnership led together. That transition gave the work an organizational home. By 2025, lasting results included Honda’s Central Ohio Living Lab, over 600 bikes added through an E-Bikes Incentive Program, and the country’s first Green IT zone. These outcomes distinguish the program’s longer civic contribution from the performance of its initial pilots.
New York, San Francisco, and Los Angeles have resources, political clout, and proximity to technology companies that few municipalities can match.
Buffalo & Detroit Define Finishable Pilots
Smart Curb Buffalo has live message boards and detection devices in use at Buffalo Niagara Medical Campus, Canalside, and Chippewa Street’s entertainment corridor. Its single-street-first approach keeps costs clearer and decisions reversible before citywide expansion. Scope is a form of financial discipline. A restricted trial gives the city a more manageable basis for judging whether a service warrants expansion.
Detroit’s Advanced Aerial Innovation Region, or AAIR, tests aerial tools for specific tasks. Newlab, Michigan Central, Airspace Link, Michigan’s Office of Future Mobility and Electrification, and the Michigan Department of Transportation launched the program. In its first year, AAIR supported over 800 flights and secured six BVLOS waivers, including a 2.3-mile beyond-visual-line-of-sight cargo drone run. A pilot at Engine 27 and the Fourth Precinct found over 460 thermal deficiencies in days rather than the weeks a traditional process would take. Energy modeling suggested that targeted changes could cut HVAC energy consumption by as much as 22 percent across every tested building, a forecast the city could use when reviewing its budget.
Scottsdale & Raleigh Institutionalize Smart Services
The Center for Digital Government’s 2025 Digital Cities Survey highlighted Scottsdale’s modernization of IT and public services through AI, drones supporting safety efforts, and a live Smart Water Grid. The grid is permanent infrastructure, and the rules for running it include gathering data at all times, involving residents, and protecting privacy. This is more than a deployment distinction. Governance establishes a place for the service within the city rather than leaving its future attached to a temporary experiment.
Raleigh’s Office of Strategy and Innovation runs the Raleigh Impact Lab within city government and uses human-centered design in work across its departments. Its institutional position differs from the nonprofit model in Columbus. Raleigh and Scottsdale embed continuity within government, while Columbus created a separate organization to sustain its work after the federal program. The structures differ, but each addresses the transition from trial to service by establishing who is responsible for continued work.
Operating Budgets Determine Which Pilots Survive
A pilot can succeed technically and still disappear when its grant period ends. Columbus’s nonprofit gives the work a home where it can continue, while Buffalo’s small trial makes it easier to estimate maintenance costs. Detroit’s building-energy modeling helps with another part by showing how the proposed changes could bring a benefit the city can measure in its operations. None of those elements alone substitutes for a defined operating budget.
The lesson for cities is to connect a pilot with a measurable result, an accountable owner, and operating funding before the grant closes. Timing is central to that decision. Confronting the expense only after launch funding has disappeared separates the demonstration from the resources needed to preserve it. A budget review must therefore distinguish evidence that a tool works from evidence that the city can afford and manage it as an ongoing service.
Privacy & Equity Shape Public Value
Operational success does not establish public acceptability. Amsterdam stopped its intelligent signal initiative in early 2025 after regulators warned that handset data could show where people went for their whole journeys. That case shows how a privacy concern can interrupt a technically oriented program. Algorithmic tools have also disproportionately flagged marginalized communities, making their distribution of scrutiny part of any assessment of public value.
Access presents a different but related constraint. Columbus found that tens of thousands of households across Franklin County had no home internet, weakening any service model that assumes residents are connected. A digital service cannot be judged solely by its availability to people already able to use it. Portland’s Smart City PDX initiative pilots tools first in marginalized areas, while Scottsdale incorporates privacy safeguards and resident input into deployment. Raleigh’s human-centered approach likewise requires public accountability when tools are designed, before they are up and running.
Permanent Infrastructure Requires Operational Commitments
For practitioners, the four-layer framework offers a way to locate missing prerequisites before committing to analytics or operational pilots. A proposed application may depend on data access and integration that the city has not yet established. Departmental scope makes those dependencies easier to define. Near-term applications such as digital twins for water systems, traffic-network tests, and building-energy models offer more manageable work than whole-city platforms.
The lesson from Buffalo and Detroit is to establish ownership, operating funding, and open oversight tied to measurable results from day one. Their limits on the work tie those commitments to specific tasks with clear bounds. Federal support can accelerate the initial deployment. The decision to make a service permanent, however, rests on demonstrated public benefit and the city’s capacity to sustain it after the grant ends.