Public Works Software: A Buyer's Guide for Small & Mid-Sized Cities

If you are a public works director, town manager, or utility supervisor evaluating software, this guide is for you. It is written from the buyer's side of the table — the questions that actually matter, the demos that mislead, and the contract terms that turn into regret two years later. No vendor tier rankings, no "Top 10" affiliate lists, no requirement to fill out a form to read the rest.

Start with the problem, not the software category

The single biggest mistake buyers make is anchoring on a category — "we need a CMMS" — before they have written down the problem. Spend an hour with a notepad and answer five questions:

1. What division is hurting the most? Streets, water, sewer, facilities, fleet?
2. What does a typical work order touch today, from intake to close-out, in concrete steps?
3. Where does work get lost? (Hint: usually intake or hand-off.)
4. What reports does your council, mayor, or board ask for that you can't easily produce?
5. What is the one thing that, if it just worked, would buy your supervisors back four hours a week?

Take that list to vendors. The good ones will adapt their demo to it. The ones who insist on the canned tour are showing you what to expect from the relationship.

What to require

Non-negotiable in 2026:

• Mobile-first with offline capability. Not a "mobile-friendly" website. A real installable app that closes work orders in dead zones. Why this matters.
• Citizen intake in the box. Not a separate SeeClickFix bill. (Or, if you already use SeeClickFix, native bidirectional integration.)
• ESRI ArcGIS integration. Bidirectional. If your assets live in GIS, the CMMS has to talk to it natively, not by overnight CSV.
• Multi-division support. Real role isolation, separate categories per division, separate dashboards.
• Per-organization pricing. Not per seat. Seasonal labor will punish you under per-seat models.
• Open API. If the vendor cannot send you API docs, your data is hostage.
• Reasonable security posture. SSO support, role-based access, audit logging, rate limiting, encrypted at rest. Reference checklist here.

What to ignore

• Logo lists. The fact that a vendor sells to a Fortune 500 industrial does not mean the product fits a 12-person public works shop.
• Award seals. Most are paid placements.
• "AI" buttons. If the AI is a chatbot in a corner that summarizes the screen you are already looking at, it is theatre. Real AI shows up in triage, prioritization, asset health, and natural-language data queries. More on this.
• "Customizable" without examples. Every system claims to be customizable. Ask for screenshots of three customers' actual configurations.

Demo questions that separate the field

Ask these in every demo. The answers tell you more than any feature comparison.

1. "Show me your mobile app, not the desktop site on a phone." (If they hesitate, you have your answer.)
2. "What happens to a work order created by a tech in a basement with no signal?"
3. "Walk me through how a citizen request becomes a closed work order, end to end, with no clicks omitted."
4. "How do you handle multiple divisions with different categories and SLAs?"
5. "How do you import our existing assets — CSV, ESRI, both?"
6. "What does your AI actually do? Show me, don't tell me."
7. "What is the all-in annual cost for our agency size? Including implementation, training, and integrations."
8. "Can I have the contact information of two customers my size to call?"

The vendors who answer all eight directly are your shortlist.

Red flags

• "We can't quote price until we do a discovery call." (Translation: pricing is bespoke and probably high.)
• "That feature is on our roadmap." (Translation: not built. Buy what exists, not what is promised.)
• The mobile demo is a screenshot. Real software has a real app.
• The integration list is a wall of logos with no detail. Ask which are native vs. Zapier-style.
• The contract has auto-renewal with 90+ days notice required. Negotiate this out before signing.

Procurement and cooperative purchasing

Most modern SaaS vendors will work through OMNIA Partners, Sourcewell, or NASPO ValuePoint cooperative contracts. If your jurisdiction requires competitive procurement, a cooperative contract usually satisfies it without an RFP. Ask the vendor which cooperatives they hold.

Pilot before purchase

For platforms that are a real fit, a 30-to-60-day pilot with one division is reasonable to ask for. The pilot should be against your real data, with at least one real crew, on real devices. A vendor who refuses a pilot is telling you their software does not survive contact with reality.

Implementation and onboarding

Modern, well-built platforms onboard a single division in two to four weeks. Anything quoted in months is a red flag for either bloated software or a vendor who profits from professional services. Migration is rarely the bottleneck — change management is. Plan for the people side as carefully as the data side.

Total cost of ownership

The license fee is rarely the real cost. Build a 3-year TCO that includes:

• License (per-org or per-seat, escalators)
• Implementation and training
• Integrations (per-connector fees? premium tier?)
• Storage overages (photos and attachments add up)
• Mobile devices and connectivity for crews
• Internal time to manage the system

The platform with the lowest license fee is rarely the cheapest at the 3-year mark. Conversely, the most expensive vendor is rarely worth the gap.

---

WorkmanIQ is purpose-built for small-to-mid-sized municipal buyers — per-organization pricing, integrations in the box, no-cost pilots. See how it works →