Insights
The Smart City Has Entered the Chat. The Budget Has Left It on Read.
The technology to fix our cities is sitting on the shelf. The invoice is what keeps it there.
Naveed A. Pirzada·Chief Operating Officer·

The technology to fix our cities is sitting on the shelf. The invoice is what keeps it there.
Picture a city engineer with a brilliant plan. Sensors that flag a failing water main before it floods a street. Traffic lights that actually talk to each other. A car park that tells you where the free spaces are instead of letting you find out the hard way.
Now picture that same engineer walking into the finance meeting.
That's where most smart city ideas quietly die. Not in the lab, and not because the technology doesn't work. It works fine. They die somewhere between "this is a great idea" and "who's paying for it?"
A bridge is easy to budget for.
Traditional infrastructure finance was built for things you can kick. A road, a bridge, a building. You know roughly what it costs, you know who owns it, and if it earns money at all, the money arrives somewhere obvious.
Smart infrastructure is a different animal. One project can bundle hardware, software, connected devices, a data platform and a support contract that runs for a decade. And the payoff is slippery.
Take a smarter traffic system. It saves fuel, shaves minutes off commutes, eases wear on the roads and lets the city squeeze more out of tarmac it already owns. Wonderful. But none of those wins lands on a single line of a spreadsheet marked "income." The benefit is sprinkled across the whole city like confetti, while the cost sits in one department's budget, looking lonely and expensive.
So the case never quite adds up on paper, even when it adds up in real life.
Stop asking "can we afford it?"
The better question is what the thing does to the economics of the asset. What does it cost to run once it's switched on? Could it earn its keep? What does it cost over its whole life, and how much more use do we get out of what we already own?

Public-private partnerships can help here. So can contracts where the supplier gets paid for results rather than just for turning up with boxes. Which one fits depends on the asset, the local rules and who's best placed to carry which risks.
The point isn't to hunt for a bigger pot of money. It's to build a deal where the money, the technology and the measurable outcomes pull in the same direction. Investors get something they can actually weigh up. Governments get a way forward that doesn't strain the balance sheet. And technology providers finally get a route out of pilot purgatory.
The cheapest new infrastructure is the old infrastructure
Here's the part that gets too little airtime: you often don't need to build anything.
Cities are already sitting on a huge portfolio. Car parks, transport hubs, council buildings, energy systems, public squares. Most of them were designed to do one job, in an era when "connected" meant the phone had a long cord.
Give them a second look and they start to look like underused talent. A transport hub can become part of a joined-up mobility network. A town hall can manage its own energy and quietly cut its own bills. Public spaces can generate data that tells the authorities where to send crews and cash.
Making what you own work harder is usually faster and cheaper than building more. It's strange how rarely it tops the agenda.
Get everyone in the room before the plan is written
There's a pattern in infrastructure planning that you can set your watch by. The technology team finds a solution. The finance team looks at the budget. Procurement drafts the requirements. Each team does its job well. Then the project stalls, because nobody ever sat the three of them down together.
It's like three people cooking separate courses for the same dinner party without talking. Everything's technically edible. It just isn't a meal.
The fix is to bring them in from day one. The technology should answer a clearly defined need. The commercial model should reflect the benefits it will really deliver. The funding should suit the risk and the way the project will be built.
That's the thinking behind Valo Smart City: treat capital, intelligent infrastructure and commercial delivery as one problem instead of three, so good projects have a fighting chance of leaving the slide deck.
The conversation is growing up
For years, the smart city debate was a show-and-tell. Look what the technology can do! Now the questions are tougher. What does it cost? How resilient is it? What will it deliver, and how will we know? Investors want credible structures and sensible risk. Operators need something that makes sense in year twelve, not just on launch day.
None of these demands cancel each other out. Handled well, they hold each other up.
So the question is no longer whether our cities can get smarter. They can. The question is whether we're willing to rewrite the economics so someone can actually pay for it.



