Equitable Smart Cities: Strategies for Inclusive Infrastructure

The biggest challenge? Assuming stability. Most smart infrastructure assumes people have consistent addresses, phone numbers, and documentation. When we work with formerly homeless individuals, we’ve had to build flexible systems that don’t immediately lock people out when their phone number changes or they miss an appointment. We maintain a 98.3% housing retention rate specifically because our systems bend instead of break.

My concrete advice: Create a “worst case scenario” user profile and design for them first. If your smart infrastructure works for someone with no smartphone, limited English, and spotty housing history, it’ll work for everyone. We recently expanded to 422 affordable housing properties, and the programs that succeeded were the ones where we piloted with our highest-need populations first, not as an afterthought.

Running an IT company for 20+ years in Utah, I’ve seen how the “digital divide” plays out in real time–not just who *has* technology, but who has the expertise to actually *use* it securely and effectively. My advice: don’t just deploy infrastructure, deploy the knowledge transfer alongside it. We’ve worked with small community organizations that got fancy new cloud systems but had zero clue about basic security protocols, which meant they were actually *more* vulnerable than before the upgrade.

The biggest challenge is that training gets treated as an afterthought line-item that gets cut when budgets tighten. I saw this during COVID when remote work exposed how many small businesses in underserved areas had internet but couldn’t implement secure VPNs or recognize phishing attacks–their employees were clicking malicious links at 3x the rate of our enterprise clients. A hacker attack happens every 39 seconds, and those attacks disproportionately succeed in communities without ongoing IT education.

What actually works is embedding support directly into the infrastructure contract from day one, not as optional add-ons. When we deploy systems, we build in quarterly security training as a non-negotiable part of the package–it’s baked into how we price everything. One healthcare client in a rural area went from monthly security incidents to zero breaches over 18 months because their staff learned to spot threats, not just because we installed better firewalls.

I built a million-dollar metal fabrication business before launching DuckView, and here’s what I learned: the communities that need smart infrastructure most are often the ones municipalities overlook because they seem “too complicated” or “not worth the investment.” That’s backwards thinking that costs everyone more in the long run.

My advice is simple: start by identifying where you’re spending the most on reactive costs–overtime police hours, repeated vandalism cleanup, insurance claims from incidents. When we deployed our AI surveillance units at public events and high-risk areas, one municipality cut off-duty police hours dramatically and saw disorderly conduct cases drop. They weren’t spending more money; they were spending smarter by putting technology where the problem actually existed.

The biggest challenge isn’t budget–it’s that decision-makers wait for crises instead of preventing them. We’ve seen this with construction sites in rough areas and dealerships in higher-crime zones. They’d rather pay for guards after three break-ins than deploy a $12K solar-powered unit that works 24/7. The math makes no sense, but that’s the pattern.

What worked for us was showing them the cost of doing nothing. When you can prove that one theft incident costs more than six months of smart surveillance, suddenly “underserved” areas become priority deployments. Make the business case show that ignoring these communities is the expensive choice.

I’ve helped enterprises across automotive, telecom, and finance deploy smart tech in over a dozen countries, and here’s what I’ve learned: Don’t start with the technology–start with the problem map. Most smart infrastructure projects fail at equity because teams build solutions in boardrooms, not communities. Before any city deploys sensors or platforms, they need to crowdsource the actual friction points from residents who live there–not just survey data, but real conversations about what breaks down daily.

The biggest challenge is misaligned incentives between departments. I’ve watched a European city invest €4M in smart parking for downtown (where 80% of users drove luxury cars) while their public housing districts had zero connectivity infrastructure. The transportation department optimized for revenue per parking space; the housing authority had no seat at the innovation table. When we mapped their internal workflows at Entrapeer, we found eight different teams buying overlapping IoT solutions with zero data sharing–literally building digital silos while claiming to break down physical ones.

My concrete advice: Create a “use case veto panel” with actual end-users from underserved neighborhoods. A bank we worked with wanted to deploy AI-powered ATMs in rural branches but found through community feedback that 60% of residents there needed better mobile connectivity first–ATMs were useless if people couldn’t get account alerts. They pivoted to sponsor local 4G infrastructure, which then made their smart ATMs viable *and* opened up telehealth access for 12,000 people. The ROI came from solving the foundational gap, not adding another shiny layer on broken infrastructure.

I’ve been running Sundance Networks for 17+ years, and we’ve donated 1000+ hours annually helping libraries, schools, and limited-income communities with IT infrastructure. The biggest lesson: don’t wait for organizations to come to you–actively identify who’s being left behind and bring refurbished equipment directly to them.

My one piece of advice is to build a parallel economy around what you’re already doing. We take outdated but functional hardware from our enterprise clients and refurbish it for local Pocono churches, libraries, and schools who couldn’t otherwise afford it. This costs us almost nothing since the equipment would be recycled anyway, but it’s given dozens of community centers technology they’d never access through traditional procurement.

The biggest challenge is that infrastructure projects measure success by deployment speed and uptime, not by who actually benefits. I watched our local libraries struggle with grant applications for weather stations and learning centers because the requirements assumed they had existing IT staff. We started volunteering to help them steer those grants and implement the technology–suddenly these “under-resourced” organizations could compete for the same smart infrastructure funding as wealthy districts.

Track who you’re NOT serving, not just who’s paying you. We measure how many community organizations we support annually because that number forces us to design services that work without massive budgets or technical expertise on their end.

I’ve been installing integrated building systems in high-rises and gated communities for 16 years, and here’s what I’ve seen work: Design for the least tech-savvy person first, then add features up. When we installed intercom systems in a 400+ resident estate, we didn’t lead with smartphone integration–we made sure the physical buttons were intuitive for elderly residents who’d never use an app. Then we layered on the mobile options for those who wanted them.

The biggest challenge is that decision-makers rarely use the systems they’re approving. I’ve walked into strata meetings where committees vote for fancy facial recognition when half the residents just needed reliable basic intercoms that actually connected calls. The people controlling the budget aren’t the ones standing at a gate in the rain trying to get the system to work.

My advice: Mandate that whoever signs off on the tech must personally use it for two weeks in real conditions before rollout. When we retrofit existing buildings, I always insist the building manager tests the access system during after-hours, in bad weather, with gloves on. You find real fast which solutions exclude people–like touch screens that don’t work with arthritic fingers or keypads with tiny numbers that seniors can’t see at night.

The unglamorous truth is that equitable infrastructure usually means spending less on flashy features and more on proper lighting at entry points, clear signage in multiple languages, and backup systems when the primary tech fails. Nobody puts that in the brochure, but it’s what actually works for everyone.

I’ve worked on both sides of Baltimore’s economic development equation–as Deputy Director of the Baltimore County Economic Development Commission and now managing commercial real estate portfolios. The single biggest advice: stop planning infrastructure around where affluent residents *already are* and start building it where workers *actually need to get to*.

I’ve watched Baltimore lose half a million square feet of office space when federal funding cuts decimated nonprofits like Catholic Relief Services and JHPIEGO. Those organizations employed thousands in Baltimore, but many employees couldn’t reliably commute because bus routes were optimized for tourism downtown, not for getting workers from East Baltimore to the office districts. When companies can’t count on employees showing up on time because the #64 bus runs every 90 minutes, they leave entirely.

The biggest challenge is that city administrators measure success by ribbon-cutting photos, not by whether someone can get from their house to their job in under an hour without a car. I see this constantly–cities will spend $50 million on a downtown light rail extension that serves 2,000 daily riders, while refusing to fund $200,000 in annual operating costs for three bus routes that would connect 15,000 residents to actual employment centers. The ROI math works, but it requires tracking “jobs retained per transit dollar” instead of “developer interest generated.”

Here’s the test I use: can a single parent working two shifts get to both jobs and pick up their kid from school using public transit? If the answer is no, your smart infrastructure is just making rich neighborhoods richer.

I’ve raised $500M+ and led 15 acquisitions across civic tech companies serving 2,500+ government agencies, and here’s what I learned: The single most important thing is to give local communities veto power over vendor selection, not just input. At Accela, when we tried to deploy smart permitting systems in smaller cities, the projects that succeeded were those where city council members from underserved districts could literally reject our platform if it didn’t work for their constituents. That one change forced us to design differently from day one.

The biggest challenge is that procurement cycles reward scale over accessibility. Large contracts go to vendors who can serve the most people fastest, which almost always means optimizing for the average user in wealthier areas. When we worked with agencies in places like Los Angeles and DC, we had to fight internally to build mobile-first interfaces that worked on older phones with spotty data–because that’s what residents in South LA and Ward 8 actually had. It cost more upfront but prevented a two-tier system.

My concrete advice: Require vendors to prove their tech works in the lowest-connectivity, lowest-literacy scenario in your jurisdiction before you sign anything. We implemented this at multiple agencies, and it immediately filtered out platforms that would’ve created digital divides. If a resident in rural Texas or a non-English speaker in San Francisco can’t use it without help, you’re not deploying smart infrastructure–you’re just automating inequality.

I’ve been managing cybersecurity and IT infrastructure for small businesses in Central Texas for years, including rural areas where internet access is spotty at best. The biggest challenge isn’t the technology–it’s assuming everyone has the same baseline access to even use smart infrastructure.

My advice: Build offline fallback systems into every smart infrastructure project from day one. When we design remote work solutions for businesses in Hill Country towns outside San Marcos, we always plan for intermittent connectivity. Cloud platforms are great, but if your smart traffic system or emergency alert only works with high-speed internet, you’ve just excluded 30% of rural America. We’ve seen this firsthand–businesses with satellite internet can’t use the same security tools as those with fiber, so we architect solutions that sync when connection is available.

The real issue is that most smart infrastructure projects are designed and tested in well-connected urban areas, then rolled out everywhere else. I’ve watched small towns struggle because the “smart” parking meters or permit systems require apps and data plans that not everyone has. When San Marcos upgraded city systems, the ones that worked best kept simple alternatives–text-based options, phone numbers that actually work, physical kiosks.

Test your infrastructure in the most challenging environment first, not last. If it works in a place with limited connectivity and diverse technical literacy levels, it’ll work everywhere. We use this approach with every client–if the 68-year-old owner can use it without calling us, we’ve succeeded.

I started MicroLumix in my garage because my 33-year-old friend died from a staph infection she got from a contaminated door handle. That taught me something critical: infrastructure equity isn’t just about who gets access to technology–it’s about who gets protected by it first.

My advice: deploy smart infrastructure where the risk is highest, not where the budget is biggest. Healthcare-acquired infections kill 54,000 people daily according to the CDC, and it’s not wealthy suburbs filling those body bags–it’s underfunded hospitals in underserved areas where cleaning staff are stretched impossibly thin. When we pitched GermPass, every fancy private hospital wanted it for their lobbies. We prioritized public facilities and pediatric centers in lower-income areas instead because that’s where one contaminated bathroom stall handle sends 47 kids home sick in a week.

The biggest challenge is that procurement committees want ROI measured in dollars saved, not lives protected. I had to reframe our whole pitch around litigation cost avoidance and staff retention rates before a single public facility would listen. We proved a $12,000 GermPass unit prevents roughly $440,000 in HAI-related costs annually–suddenly budget constraints became budget priorities.

Make your business case prove that *not* deploying in underserved areas costs more than deploying there. That’s the only language procurement understands, and it’s how you get technology past the velvet rope.

I’ve built digital infrastructure that’s supposed to serve everyone–roadside assistance platforms connecting drivers to help across multiple states. The biggest challenge isn’t technology, it’s distribution of access. We can build the smartest dispatch system in the world, but if rescuers only cluster in wealthy suburbs or if rural areas get 90-minute wait times while cities get 15-minute service, we’ve failed.

My advice: mandate coverage requirements with teeth. When we expanded Road Rescue Network, I had to make hard calls about requiring rescuers to accept jobs in lower-income zones or lose platform access. It cost us some providers who only wanted high-margin highway calls, but our average response time in underserved areas dropped from 74 minutes to 38 minutes in six months. You can’t rely on market forces alone–infrastructure builders need to bake equity into the contract terms, the algorithms, and the business model from day one.

The real test is whether your smart infrastructure works for someone in a food desert at 2am with a dead battery and no credit card, not just someone in a tech corridor with AAA premium. We added cash payment options and partnered with community organizations to get that right, and our service request volume in historically ignored ZIP codes went up 340% year-over-year. That’s the metric that matters.

I’ve trained law enforcement agencies and military units across every economic spectrum–from well-funded federal task forces to small-town departments running on shoestring budgets. The single biggest mistake I see is rolling out technology without training people how to actually use it. A $2 million surveillance system means nothing if only three people know how to access the data, and two of them are about to retire.

Here’s what works: Before you buy one piece of smart infrastructure, identify the least tech-savvy person who will need to use it–the night shift dispatcher, the patrol officer who still uses a flip phone, the community member filing reports at 2 AM. If they can’t figure it out in under two minutes without help, your system will create a two-tier access problem. I built Amazon’s Loss Prevention program by making sure every warehouse worker, regardless of education level, could report issues through multiple channels–app, phone, or in-person.

The real challenge isn’t technical–it’s ego. Decision-makers fall in love with flashy dashboards and AI analytics that look impressive in boardroom demos but completely alienate the people who need them most. When I design certification programs for investigators worldwide, I obsess over one metric: Can someone with zero prior experience complete the first module without calling support? That same ruthless simplicity test should apply to every smart city interface, kiosk, or alert system before launch.

Test in the field with real users before you spend millions. I’ve watched cities deploy “smart” crime reporting systems that required smartphone apps when 40% of residents in certain neighborhoods didn’t have data plans. The result? Those communities became invisible in the data, and officials made decisions based on incomplete information that hurt the people who needed help most.

I run addiction recovery services in Australia, and I’ve seen how “accessible support” gets designed by people who’ve never had to access it themselves. When I was desperate for help with alcoholism, I literally couldn’t afford treatment and had to borrow significant money for rehab–meanwhile free programs had 6-month waitlists or operated only during business hours when I needed to work.

The advice: Put people with lived experience of struggling to access services on the planning team from day one, not as an afterthought. When we designed The Freedom Room, I made sure our hours, location, payment structures, and even how people book appointments reflected what I wished existed when I was trying to get help. That meant evening sessions, no-shame intake processes, and being upfront about costs–not hidden behind phone tag.

The biggest challenge: Decision-makers assume if you build it in a “central location” with “affordable pricing,” everyone benefits equally. But transport costs, childcare needs, language barriers, and shame about seeking help create invisible walls. I’ve watched people relapse because the only free program required three bus transfers with young kids in tow. Smart infrastructure means nothing if the last mile to your door is still impossible for the people who need it most.

For cities, organizations want equitable smart infrastructure. As a cash home buyer investor, I say: make sure inclusive community engagement comes first when figuring things out. It means residents, especially those from underserved locales, should get involved in deciding things. Doing so lets cities grasp local needs plus sidestep unintended issues like displacement, letting smart infrastructure fairly benefit everyone.

The biggest hurdle? Systemic inequalities impacting urban growth and fair distributions. Think about how unequal access to tech or funding favoring richer areas might worsen existing social divides. Also, equitable policy plus funding transparency seems quite vital, because smart infrastructure spending seems prone to clustering within high-value or politically strong areas, possibly worsening inequities. So, to really tackle issues people face, think plans: funding folks need, protecting affordable places, plus tech access for everyone.

Smart infrastructure only works if it’s accessible. Ride-share autonomy and services like Waymo or Uber already expand mobility for seniors and people without cars, lowering per-mile cost. The real challenge is data ownership—who controls mapped roads and digital layers that future transport depends on. Cities must ensure open standards so private mapping doesn’t create digital toll roads. Equity starts with access, not just asphalt.