Your town may soon budget for ransom like it budgets for road salt
A budget template under discussion among small-town finance officers would open a standing line for extortion payments. The debate in the council chamber would not be about whether to pay. It would be about the realistic unit price.
Under a budget template circulating among small-town finance officers, a municipality could in future carry a permanent line for ransomware incidents, sitting in the accounts between winter road maintenance and street lighting. The question before the council would not be whether such a line should exist. By the time it reached the chamber, the argument would be about the unit price.
The defence of the line would be word for word the defence of road salt. In any given year the town may not need it. Across a decade it certainly will, and provisioning in advance is cheaper than improvising at two in the morning with somebody who knows exactly how the conversation ends. It is the same argument councils already make about the gritting lorry, in a building that acquired a salt store long before it acquired a server.
“We would not be budgeting for a crime,” the mayor would be expected to say at the second reading. “We would be budgeting for a Tuesday. The registry stops working, the water company cannot read its meters, and two hundred people cannot file a birth certificate. I am obliged to have a number for that. I would rather the number sat in the budget than in a phone call.”
The line would not survive under that name. Several jurisdictions are moving to forbid public bodies from paying at all, and the template deals with this in a footnote: the item would continue as a recovery reserve, covering system restoration, legal advice, negotiation support and the letters that have to go to every resident whose file was copied. Most of the money goes there in any case. Only the label would be contested.
Insurance would complicate the arithmetic rather than simplify it. Cover would be available, conditional on a questionnaire the town clerk would have to answer honestly, including the question about whether remote access to the waterworks requires a second factor. In many towns the honest answer is not a tick but a sentence, and the quotation would arrive accordingly.
The comparison with salt would break down at the least comforting point. The salt has a store, a lorry and a man who has driven it for nineteen years. The other risk has an IT contract shared with two neighbouring villages, an access list nobody has audited since the last election, and a helpdesk number answered in office hours by somebody excellent and alone.
Nothing has been adopted: a template, a footnote and a working group of finance officers. But the significant part is not the attack. It is the line. A risk that acquires a permanent budget line stops being an emergency and becomes a municipal service — priced, argued over, and quietly assumed to recur.
If you liked this…
Your fridge may soon need a credit score
A concept under discussion among appliance financiers would let a household appliance hold its own payment history. The appliance would not own itself. It would merely be the party that fell behind.
Your body may soon get a patch Tuesday
A proposed update schedule for implanted medical devices would standardise when your hardware restarts. The working title of the document is said to be deliberately boring, for reasons its authors consider obvious.
Your insurer may soon ask how old your router is
A claims framework under discussion among European home insurers would make a burglary payout depend on whether the box in the hallway was still receiving security updates. The device would not have to be broken. It would only have to be out of support.
Still laughing
We made it up. Then reality caught up.
What we wrote
We wrote it in 2021
One day the junior developer's main skill could be describing the problem clearly enough for the machine to solve it.
What actually happened
Reality caught up in 2025
AI coding assistants are built into mainstream development tools, and producing code from a plain-language description is now a routine part of professional software work.
Vendor product documentation and developer surveys on assistant adoption.
The joke was the job description. The job description was updated.
MISTAKE
TOMORROW, DELIVERED TODAY.
One email a week. The future, before it files a press release.
Worst case: you laugh. Best case: we predicted the future.
