I think the money is a red herring here.
In Oak Park, Illinois, we ran into a rhyming version of this problem: the only control we had about what technology OPPD deployed was a spending limit ($15K, if I'm remembering right), above which they had to ask the board for an appropriation. Our pilot deployment of Flock cameras easily went underneath that limit.
I'm not reflexively anti-ALPR camera. I don't like them, but I do local politics and know what my neighbors think, and a pretty significant chunk of my neighbors --- in what is likely one of the top 10 bluest municipalities in the United States (we're the most progressive in Chicagoland, which is saying something) --- want these cameras as a response to violent crime.
But I do believe you have to run a legit process to get them deployed.
OPPD was surprised when, after attempting to graduate their pilot to a broader deployment, a minor fracas erupted at the board. I'm on Oak Park's information systems commission and, with the help of a trustee and after talking to the Board president, got "what the hell do we do about the cameras" assigned to my commission. In conjunction with our police oversight commission (but, really, just us on the nerd commission), we:
* Got General Orders put in place for Flock usage that limited it exclusively to violent crime.
* Set up a monthly usage report regime that allowed the Village to get effectiveness metrics that prevented further rollout and ultimately got the cameras shut down.
* Presented to the board and got enacted an ACLU CCOPS ordinance, which requires board approval for anything broadly construed as "surveillance technology" for policing, whether you spend $1, $100,000, or $0 on it.
Especially if you're in a suburb, where the most important units of governance are responsive to like 15,000-50,000 people, this stuff is all pretty doable if you engage in local politics. It's much trickier if you're within the city limits of a major metro (we're adjacent to Chicago, and by rights should be a part of it), but still.