Cityworks Alternative for Small Water Utilities: An Honest Look
If you run a water utility with somewhere between 2,000 and 50,000 connections, someone may have handed you a Cityworks renewal quote and asked if it's worth it. Maybe your crew barely opens it. Maybe the GIS person who set it up has moved on. Or maybe you just want to see what a Cityworks alternative looks like before you sign another three years.
This is the honest version. Cityworks is a serious product, and for some utilities it's the right one. For a lot of small and mid-size utilities, it's more system than the job needs, sold in a way that makes the real cost hard to see.
A quick note on who's writing. Fluvio is built by DB Utility, a water meter installation company. We spend our days in utility yards, meter pits, and the cabs of public works trucks. A lot of what follows we learned in the ditch, not in a sales meeting.
Where Cityworks is strong
Start with what Cityworks does well, because it's a lot.
It's mature. Cityworks has been around a long time and is used by cities, counties, and utilities across the country. Its core workflows for work orders, service requests, and inspections are deep and proven.
It's built on Esri. Cityworks is GIS-centric. It runs on top of ArcGIS, so assets live in your Esri geodatabase and work orders tie straight to them. If you have a strong GIS team and a clean ArcGIS deployment, that's a real advantage.
It scales to big, complex organizations. Large utilities and whole cities run Cityworks across water, sewer, streets, parks, and permitting. Its AMS (asset management) and PLL (permitting, licensing, and land) modules can cover many departments in one system.
It has an ecosystem. A network of integrators implement, host, and extend it. And Cityworks is now sold by Trimble as Trimble Unity Maintain, so there's a large company behind it.
If you're a large utility with a GIS department, IT staff, and a budget for an integrator, Cityworks is a reasonable choice. We'd tell you that in person.
Why small utilities look for a Cityworks alternative
For smaller utilities, the trouble usually isn't the software. It's everything around it. Four things come up again and again, and each one is in Trimble's own quote language from public contracts.
1. Named logins are capped. The City of Aurora, Ohio's March 2026 Cityworks contract includes 25 hosting logins. Whitestown, Indiana's 2022 quote includes 50. Both say additional logins can be added for an additional fee. At a small utility, that means someone decides which operators get a login and which ones call it in.
2. Esri is required, and it's on you. The Whitestown quote says the procurement, installation, and administration of Esri software is the customer's responsibility. If you already own Esri, fine. If you don't, that's a new line item and a new skill set to staff.
3. Price follows population, not your system. Aurora's contract says the annual fee is based on a population range, and that Trimble reserves the right to adjust the fee to match the city's actual population range. You pay for the size of your town, not the connections you serve.
4. Implementation is separate. Whitestown's quote says implementation services are priced separately. The town, which is under 10,000 people, paid $39,000 for core implementation in 2022. That's on top of the license.
None of this is hidden. It's just easy to miss until the invoices arrive. We break down each layer, with sourced numbers, in our post on what Cityworks really costs.
What to look for in a replacement
Judge any option by how your crew will use it on a Tuesday morning, not by the feature matrix. The short list:
- It works on a phone in the truck, including when the signal drops.
- Maps work without an Esri license, and it can still read your Esri data if you have it.
- Your staff build their own reports without a consultant.
- Everyone who touches a job gets a login. No rationing.
- Someone moves your data over for you, including open work and asset history.
- You get a price on the first call.
- You're live in weeks, not after a long project.
We wrote a full buyer's checklist for work order software, with questions to ask in every demo.
How Fluvio Field compares
Fluvio Field is our work order and field operations product. Here's how it lines up against the structure of a typical Cityworks deal.
| Cityworks (from public contracts) | Fluvio Field | |
|---|---|---|
| Users | Named logins capped (25 or 50 in the quotes above); more cost extra | Unlimited users |
| GIS | Esri ArcGIS required, customer's responsibility | No Esri license required |
| Pricing basis | Population band | Per connection, declining rate as you grow |
| Implementation | Quoted separately | Credited back in full on a 12-month commit |
| Price at similar size | License alone: $25,011 in year 1 to $27,575 in year 3 (Aurora, OH) | $15,000 a year at 4,000 connections |
A few honest notes on that table. The Aurora figures are for the asset-management license alone. Esri and implementation are quoted separately. Many cities also fund Cityworks across departments: Aurora pays for it from its General, Water, and Sewer funds. Fluvio Field is sold to the water utility. So compare your own paperwork, line by line.
On GIS: Fluvio Field reads your ArcGIS feature services and imports shapefiles or GeoJSON. If you don't have a GIS, Fluvio can be your GIS. You draw mains and drop valves and hydrants as you find them. Writing changes back to Esri is on our roadmap. It doesn't ship today, and we'd rather say that plainly.
See the full feature list on the Fluvio Field page, or check pricing.
When you should stay on Cityworks
Stay if:
- You're a large utility or a whole city running many departments in one system.
- You have a GIS team that keeps a mature ArcGIS deployment and wants work orders inside it.
- You rely on Cityworks permitting (PLL) alongside work orders.
- You've already paid for a deep implementation, and your staff actually use it.
Switching has a real cost. If Cityworks is working for you, keep it.
When an alternative makes sense
Look around if:
- Some of your crew don't have logins, so they phone or text the office instead.
- You don't have a GIS person, or you lost the one you had.
- Every new report means a call to the integrator.
- Your renewal went up and nobody can explain why.
- The water utility pays for a citywide system it mostly doesn't use.
Bring your renewal quote
We don't publish a "we're X% cheaper" number. Cityworks pricing varies too much for that to be honest. Two utilities the same size can sit in different population bands, with different modules, login counts, and Esri setups.
What we do instead: put your Cityworks renewal quote on the table and we'll walk the two line by line. You'll see where the money goes on both sides.
The bottom line
The right Cityworks alternative for a small water utility is the one your crew opens every morning without being told to. Cityworks is strong for large, GIS-heavy organizations. If that's not you, compare login caps, the Esri requirement, implementation, and who you call when you need a new report. Then decide with real numbers in front of you.
Fluvio is work order, resident portal, and water-loss software for small and mid-size water utilities, built by DB Utility, a water meter installation company. Unlimited users, no Esri license required, live in weeks. Book a walkthrough at getfluvio.com →