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

This guide is for public works directors, town managers, and utility supervisors who are evaluating software. It is written from the buyer's side of the table. It covers the questions worth asking, the parts of a demo that can mislead you, and the contract terms people tend to regret two years in. There are no vendor rankings or affiliate lists here, and you don't have to fill out a form to read it.

Start with the problem, not the software category

A common mistake is to settle on a category ("we need a CMMS") before writing down what the problem is. Spend an hour with a notepad and answer five questions:

1. Which division is struggling the most? Streets, water, sewer, facilities, or fleet?
2. What steps does a typical work order go through today, from intake to close-out?
3. Where does work get lost? In our experience it is usually at intake or at a hand-off.
4. What reports do your council, mayor, or board ask for that you can't easily produce?
5. What one fix would save your supervisors four hours a week?

Bring that list to vendors. A good vendor will build the demo around it. A vendor who sticks to the standard script is likely to be just as inflexible after you sign.

What to require

In 2026, these should be requirements:

• A mobile app that works offline. A website that resizes for phones is not enough. You want an installable app that can close work orders where there is no signal. Why this matters.
• Resident intake included. You shouldn't need a separate SeeClickFix subscription. If you already use SeeClickFix, look for a native two-way integration.
• ESRI ArcGIS integration. It should sync both ways. If your assets live in GIS, the CMMS needs to connect to it directly and not rely on an overnight CSV export.
• Support for multiple divisions. Each division should have its own roles, categories, and dashboards.
• Pricing per organization. Per-seat pricing gets expensive when you bring on seasonal staff.
• An open API. If the vendor can't send you API documentation, getting your data out later will be difficult.
• Reasonable security. Look for SSO support, role-based access, audit logging, rate limiting, and encryption at rest. See our reference checklist.

What to ignore

• Logo lists. A vendor that sells to a Fortune 500 manufacturer may not be a good fit for a 12-person public works shop.
• Award seals. Most of them are paid placements.
• "AI" buttons. A chatbot in the corner that summarizes the screen you are already looking at adds little. Useful AI helps with triage, prioritization, asset health, and questions about your data asked in plain language. More on this.
• "Customizable" with no examples. Most vendors say their system is customizable. Ask to see screenshots of how three current customers have configured it.

Demo questions worth asking

Ask these in each demo. The answers will tell you more than a feature comparison chart.

1. "Show me your mobile app, not the desktop site on a phone." Hesitation here tells you a lot.
2. "What happens to a work order a tech creates in a basement with no signal?"
3. "Walk me through how a resident request becomes a closed work order, start to finish, without skipping any clicks."
4. "How do you handle several divisions with different categories and SLAs?"
5. "How do you import our existing assets? From CSV, from ESRI, or both?"
6. "What does your AI do? Please show me in the product."
7. "What is the total annual cost for an agency our size, including implementation, training, and integrations?"
8. "Can I get contact information for two customers our size so I can call them?"

Put the vendors who answer all eight clearly on your shortlist.

Red flags

• "We can't quote a price until we do a discovery call." This usually means pricing is negotiated case by case and tends to run high.
• "That feature is on our roadmap." This means it hasn't been built. Buy based on what the product does today.
• The mobile demo is a screenshot instead of a working app.
• The integration list is a page of logos with no detail. Ask which integrations are native and which go through a third-party connector like Zapier.
• The contract renews automatically and requires 90 or more days' notice to cancel. Negotiate that out before you sign.

Procurement and cooperative purchasing

Most SaaS vendors in this market sell through cooperative contracts such as OMNIA Partners, Sourcewell, or NASPO ValuePoint. If your jurisdiction requires competitive procurement, buying through a cooperative contract usually meets that requirement without a separate RFP. Ask each vendor which cooperatives they hold.

Pilot before purchase

If a platform looks like a good fit, it is reasonable to ask for a 30 to 60 day pilot with one division. The pilot should use your own data, at least one working crew, and the devices your crews already carry. If a vendor won't agree to a pilot, be cautious about how the software will hold up in daily use.

Implementation and onboarding

A well-built platform can get a single division running in two to four weeks. If a vendor quotes several months, either the software is overly complex or the vendor earns a lot from professional services. Data migration is rarely what slows things down. Getting staff to change how they work usually is, so plan for training and adoption as carefully as you plan the data move.

Total cost of ownership

The license fee is usually not the largest cost. Build a three-year estimate that includes:

• License fees (per organization or per seat, plus annual escalators)
• Implementation and training
• Integrations (per-connector fees or a premium tier)
• Storage overages (photos and attachments add up)
• Mobile devices and data plans for crews
• Staff time to administer the system

The vendor with the lowest license fee is often not the cheapest after three years. The most expensive vendor is also seldom worth the difference.

---

WorkmanIQ is built for municipal buyers of all sizes, with per-organization pricing, built-in integrations, and no-cost pilots. See how it works