You do not run one system. You run a book of them.
A handful of small towns, a few districts, maybe a private system or two. 25 connections here, 25 there, spread across a county or a couple of states. Each one came to you the same way: a paper set of maps with some Sharpie lines on it, a meter-read sheet, and whatever the last operator could remember on the way out the door.
Nobody takes on systems like that to get rich. You take them on because the water has to stay safe and the town has nobody else, and if not you, then who. We know, because we run a contract operation ourselves. Running ten systems at once is a different problem than running one. This is about the one app you run all of it from. Here is what it does and what it does not do.
The work is the easy part. The paperwork is what buries you.
What software do contract operators use to run multiple water systems?
The ones who can, run them all from one app instead of a separate login, a separate map, and a separate binder per town.
Ziptility puts every system you operate on one map. Your whole crew works from it in the field, with the assets, the work history, and the records for each one in the same place.
We built it for small water and wastewater systems, the kind run by a handful of people wearing every hat. That is exactly what a contract operator's portfolio is made of: systems too small to carry a city's software, run by a crew that is already stretched thin. You are not stitching together five tools per town. You run the map, the asset records, and the field work from one place, on a phone, in the truck.
Can I manage several water and wastewater systems from one app?
Yes. Each system you operate gets its own clean record, organized as its own team inside your company's account.
One login for you. The systems split out so a crew can be pointed at the right one, and the work stays attached to the right town.
It works for the assets a small system actually runs. Distribution: mains, service lines, curb stops, valves, hydrants, meters. Sources and storage: wells, well pumps, booster stations, storage tanks. Wastewater: gravity mains, force mains, manholes, lift stations, grinder pumps. And the events you have to keep on the record but that are not rate-base assets: main breaks, SSOs, sewer backups. Same setup, system after system, so the tenth town looks like the first.
You run all your systems in one place, each one its own clean record. We are not going to pretend we have a feature that walls off and resells data access to each district for you. That part lives in the conversation we have, not on this page.
What happens when I take over a system with no records?
The first thing you do is get it on the map off the billing meter-read list, then the record fills in as your crew works.
You start with whatever the predecessor handed over, paper maps, an old shapefile, a spreadsheet of meters, and we import it. From there it gets better every week instead of staying a snapshot that was wrong the day it was drawn.
This is the part that lets a portfolio grow without burying you. The map and the records update as a byproduct of the work your crew is already doing, not as a separate data project. An operator out marking an 811 locate or exercising a valve logs what he would note anyway, and that writes itself onto the asset. Every person on the crew does maybe ten small tasks a day. Across a portfolio that adds up to thousands of dated, true updates a year. You built a real database on every system without anyone sitting down to a data project. The next takeover is the same playbook, not a fresh fire drill. You already have enough to do.
If you are still building the book, the same playbook holds from the first anchor system: land the one that can carry a full-time operator, build density around it, and let every takeover after that inherit the same backbone from day one. We built our own operation that way. How it maps to your geography is a demo conversation, not a page.
Can the data I collect help me get my systems funded?
Yes, and this is the part no other tool does for you.
The leak repairs, condition notes, and inspections your crew enters become the historical record a funding application needs. That record is the hardest thing to produce when you sit down to apply. A system that was a dog nobody wanted becomes a system you can get funded.
That is two wins, not one. The same record saves the system money (you find the bad assets before they fail) and makes the system money (it backs the funding that fixes them). For a contract operator that is the growth engine: better-funded systems are better systems to operate. When you need a formal asset management plan for a board or a funder, you hand your engineer current data instead of paying them to re-gather it. The engineering judgment stays your engineer's job. We just keep the record honest in between.
Is there a per-seat fee if my whole crew uses it?
No. Water and sewer pricing is per organization, by service connection, with unlimited users and no lock-in.
Every operator and field tech can have it on a phone instead of one license sitting on the office computer. You are not paying more every time you add a person.
Per-seat pricing is the thing that punishes a contract operator for growing: you add crew, you add cost, on top of the systems you take on. This does not work that way. Because there is no per-seat fee, the people who actually do the work are the ones feeding the map. That is the only way a field-first record stays current. Operators who run multiple systems get a custom quote, since a portfolio is not a single system. There is no lock-in either: a system can map and leave. That is rare, but the door is not bolted.
You stay an operator. The app handles the backbone.
The admin is the thing operators hate. At scale across a portfolio it is relentless: the work assignments, the records, the reports, the proof that the work got done. Letting the software carry that backbone is what frees you to stay an operator instead of becoming a paperwork shop.
We speak from our own books here. Ziptility was built by an operator who ran small water systems, and then we went a step further and bought a contract operations company that runs small systems every day: Mogollon Water Management, the contract operator we run ourselves, the largest contract O&M provider in northeast Arizona, working two of the poorest counties in the state. The crews doing the leak repairs, the locates, and the meter swaps tell us what works and what gets in the way, and when something is clumsy in the field, we hear about it that week.
On a single Mogollon system, bringing Ziptility on saved 10 to 15 hours a week of admin time. Mostly by assigning work straight from email out to the crew in the field instead of routing it through a second system. Multiply that across a portfolio and it is the difference between taking on the next town and turning it down.
See it run on a real contract operation
The demo is not a sandbox. We pull up the live Mogollon org: this is our staff, these are the systems we operate, this is how a real contract operation runs on it day to day. No other vendor can show you that, because no other vendor is a contract operator. If you run systems for a living, that is the fastest way to see whether it fits how you work. Request a demo, or see pricing.
What it takes in your state
Licensing, operator-of-record rules, site visits, and remote operation all vary by state. Pick yours for the rules, the paperwork, and how to get listed.
Questions operators ask
What software do contract operators use to run multiple water systems?
The ones who can run them all from one app instead of a separate login and binder per town. Ziptility puts every system you operate on one map your crew works from the field, with the assets, work history, and records for each system in one place. Built for the small systems a portfolio is made of.
Can I manage several water and wastewater systems from one app?
Yes. Each system gets its own clean record, organized as its own team inside your company's account, so the work stays attached to the right town. Same setup system after system, so the tenth town looks like the first.
Is there a per-seat fee if my whole crew uses it?
No. Pricing is per organization, by service connection, with unlimited users and no lock-in. You are not paying more every time you add an operator. Operators running multiple systems get a custom quote.
I just took over a system with no records. How do I get it on the map?
You start with what the predecessor handed over: paper maps, an old shapefile, a meter-read sheet. We import it. Get it on the map off the billing list, then the record fills in as your crew does normal work. The next takeover is the same playbook.
Can the data I collect help me get my systems funded?
Yes. The repairs, condition notes, and inspections your crew enters become the historical record a funding application needs, which is the hardest part to produce. The same record saves the system money and helps it win the funding to fix it. Two wins, not one.