Fresno City Council Approves $689K Contract for Cloud-Based Procurement Software
The Fresno City Council approved a seven-year contract worth up to $689,319.96 in taxpayer money for cloud-based procurement software from OpenGov, Inc., voting it through on the consent calendar in August 2024 with no public debate.
The contract commits the city to three years of cloud-hosted software at $94,415.48 per year, plus a one-time implementation fee of $28,810.60. Four optional one-year extensions push the potential total to $689,319.96, with annual cost increases capped at 5%.
The council authorized the purchase through a cooperative agreement run by NASPO ValuePoint and the State of Utah. This cooperative procurement was competitively solicited by those jurisdictions, not by Fresno itself.
According to the staff report signed by General Services Director Brian Barr and Chief Information Officer Bryon Horn, the software “streamlines procurement processes” by centralizing bid management, contract tracking, and staff collaboration. The report frames the platform as a time-saver that “ensures transparency” in the city’s procurement workflow.
What the staff report does not state: how much time the software is projected to save, what measurable ROI the city expects, or whether existing systems were evaluated for cost-effectiveness before committing to a nearly $700,000 spend. The material names no benchmarks, no cost-benefit analysis, and no internal alternatives considered.
The Breakdown
- The contract runs three years guaranteed, with four optional one-year extensions ā a potential seven-year commitment.
- Year-one cost: $123,226.08 ($94,415.48 annual software fee plus $28,810.60 one-time implementation).
- Years two and three: $94,415.48 each.
- Extension years can see annual increases up to 5%.
- The city is purchasing through a cooperative agreement administered by NASPO ValuePoint and the State of Utah, which the State of California joined via a “Participating Addendum.” This cooperative procurement was competitively solicited by those jurisdictions.
What This Means for You
This contract represents a multi-year taxpayer commitment to a single vendor for a core administrative function ā procurement management ā with no stated performance benchmarks in the public record.
As a voter, you’re evaluating a council that approved this spending on the consent calendar, meaning no individual discussion or public scrutiny before the vote. The decision reflects the council’s approach to technology spending: whether officials demand measurable ROI before committing taxpayer money, or whether they greenlight software purchases based on general descriptions of efficiency gains with no hard numbers attached.
If you’re weighing how your council manages operational budgets, this contract is a test case ā nearly $700,000 in potential spending, no documented cost-benefit analysis in the public record, and a seven-year timeline that ties the city to one vendor.
What to Watch
The staff report offers no cost-benefit analysis, no timeline for expected time savings, and no performance metrics the city will use to judge whether the software delivers value.
That’s a gap in any business decision ā committing $689,000 without stating what success looks like and how you’ll measure it. Key questions the material leaves unanswered:
- What measurable efficiency gain does the city expect, and by when? The report claims the software will save “significant time and effort,” but gives no baseline for current procurement cycle times and no target for post-implementation improvement. Without that, there’s no way to know whether the software is performing or whether the city is simply paying $94,000+ per year for a system no one can prove is working.
- What did the State of Utah’s process actually evaluate, and did Fresno staff independently verify that OpenGov was the best fit for the city’s needs and budget? The material provides no analysis of whether this particular cooperative agreement delivered better pricing or features than the city could have secured on its own.
- What happens if the software underperforms or the city wants to switch vendors mid-contract? The three-year commitment is firm, but the material gives no detail on exit terms, performance penalties, or whether the city retains any leverage if the platform fails to deliver.
The council approved this on the consent calendar ā a procedural tool meant for routine, low-controversy items that don’t warrant individual discussion. Whether a contract of this size qualifies as “routine” is itself a voter-accountability question: did your council treat this as the vendor commitment it is, or as administrative paperwork that didn’t merit public scrutiny?
