Going live in weeks, not quarters: a realistic municipal rollout

The reason municipal software rollouts take two quarters is rarely the software. It’s the sequence: data migration before anyone has agreed what the data should look like, and configuration handed to a consultant who doesn’t run the city.

Connect before you configure

Start from the GIS you already have. Point the system at your Feature Services and let it propose your asset structure from what’s actually there. That single step removes the biggest source of early rework.

Configure in your own words

Work-order types, inspection checklists, and crews should be shaped by the people who’ll use them — with an assistant helping, not a vendor billing hourly. When the team owns the configuration, adoption follows.