Choosing a water utility software vendor requires evaluating platform architecture, integration depth, implementation timelines, pricing models, cybersecurity posture, and post-go-live support. This 10-question framework gives Utility Directors a structured way to compare shortlisted platforms and identify vendors who are genuinely built for small and mid-sized US municipal water systems.
You've sat through the demo. The slides looked polished. The sales rep answered every question with confidence. But when you asked — specifically — how long the data migration from your current system would take and who is responsible if something goes wrong, the answer was vague. That's a red flag. And it's the kind of red flag that's easy to miss when you're evaluating three vendors simultaneously while running a utility.
Most water utilities replace their core management software once every 15 to 20 years. That means most Utility Directors have never done it before. The vendor, on the other hand, has done hundreds of sales calls. The information asymmetry is real and it's what this guide is designed to correct.
A water utility software vendor is a company that provides cloud-based or on-premise software platforms to manage billing, customer information, metering, work orders, asset tracking, and compliance reporting for water utilities. Not all vendors serve the same market. Many are built for large investor-owned utilities with dedicated IT departments and multi-year implementation budgets. If you're running a 5,000- to 100,000-meter municipal system, you need a vendor who has solved your specific problems, not adapted an enterprise solution to fit you.
The 10 questions below are organized into five evaluation areas. Use them in vendor demos, in written RFP responses, and in reference calls. A vendor who answers all ten well, specifically, with evidence, belongs on your shortlist. A vendor who hedges, deflects, or answers with marketing language does not.
Before asking technical questions, it's worth establishing why ICP fit, whether a vendor is actually built for utilities your size, matters more than feature lists. Enterprise software vendors serving large investor-owned utilities have deep feature catalogues and strong brand recognition. They also typically require 18-month implementations, dedicated internal project managers, and licence fees that assume a large IT team and a large customer base to absorb costs.
For a municipal water system serving 10,000 to 50,000 meters, neither the implementation model nor the cost structure of enterprise software is appropriate. A vendor designed for utilities in your size range will have pre-configured workflows for the regulatory environment you operate in, pricing that scales per meter rather than per user or per site, and an implementation team that has seen your exact setup before.
SMART360, for example, is built specifically for utilities operating between 3,000 and 100,000 meters. Platform architecture, onboarding methodology, and pricing are all calibrated to that ICP. When evaluating any vendor, ask directly: "What is the smallest and largest utility you currently serve, measured in meters?" The answer tells you immediately whether you're in their core market or their edge case.
This is not a technical question. It is a total-cost-of-ownership question. On-premise software requires your IT team (often a team of one or two in a small utility) to maintain servers, apply security patches, manage backups, and handle disaster recovery. Cloud-native SaaS shifts all of that to the vendor — your team logs in via a browser and the infrastructure is the vendor's problem.
A good answer: The platform is cloud-native, hosted on a major cloud provider (AWS or Google Cloud), with no on-premise servers required at your site. Security patches, updates, and backups are managed by the vendor.
A red flag answer: "We offer both on-premise and cloud options" without a clear recommendation. Vendors offering both often have a legacy on-premise codebase and a newer cloud wrapper — which means your system may not be getting the full benefit of cloud architecture.
SMART360 is cloud-native SaaS with no on-premise infrastructure required — relevant for lean IT teams managing multiple operational priorities.
Integration depth is where most software evaluations break down. A vendor may claim to "integrate with all major AMI platforms" and mean that they can export a CSV file that your team imports manually. That is not integration. Integration means automated, bidirectional data exchange with configurable sync frequency — meter reads flowing into billing without a manual step in between.
Ask for a specific list of named integrations, not a category description. Ask whether the integrations are native (built and maintained by the vendor) or via third-party middleware. Ask what happens to your billing data if an integration breaks at 2am on a Monday.
The benchmark for integration breadth at this market level: 25+ pre-built integrations covering AMI/MDM platforms (Sensus, Itron, Badger), GIS (Esri), payment gateways, and ERP systems. SMART360 meets that benchmark. When you evaluate other vendors, ask them to match that list specifically.
Implementation timeline is the single most manipulated figure in utility software sales. The headline number — "we can go live in X weeks" — rarely includes the full picture: data cleaning, staff training, parallel billing runs to verify accuracy, and hypercare support in the first 60 days after go-live.
According to AWWA, the average utility software implementation with large enterprise vendors runs 12–18 months. Purpose-built platforms designed for small and mid-sized utilities, with pre-configured templates for standard utility workflows, can go live significantly faster. SMART360's implementation timeline is 12–24 weeks, which includes data migration, configuration, staff training, and a parallel billing run.
A good answer: A specific week-by-week phased plan, with clearly named deliverables and named responsibilities (what your team does vs what the vendor does) at each stage.
A red flag answer: "It depends on your system" without a baseline range. Every vendor knows their median implementation time. If they won't give you a range, they're managing expectations downward before the contract is signed.
Your customer data, billing history, meter reads, and work order records represent decades of institutional knowledge. Migration risk is real: data formatting inconsistencies, field mapping errors, and partial data loss are common in system transitions. The question is not whether migration risk exists, it does, but what the vendor's process is for identifying it, testing against it, and recovering from it.
Ask for their data migration methodology in writing. Ask whether they have migrated data from your current system before and can name a reference. Ask what their policy is if post-go-live auditing reveals data loss or corruption.
SMART360's implementation and data migration service includes a pre-migration data audit, field-mapping validation, and a 30-day post-go-live reconciliation window. Ask every vendor on your shortlist whether they offer an equivalent guarantee.
Pricing model structure determines whether your cost grows predictably with your system or spikes unpredictably with your team. Per-user pricing punishes you every time you hire a new billing clerk or field supervisor. Flat-licence pricing front-loads cost and creates budget risk when you're not sure how much of the platform you'll actually use. Per-meter pricing aligns vendor revenue with your operational scale — your cost grows as your system grows, and shrinks if it contracts.
SMART360 uses a pay-per-meter pricing model — no per-user fees, no module unlocks. For a 15,000-meter municipal system, you know exactly what you'll pay in year one, year three, and year five. When you evaluate other vendors, ask them to model your cost over five years at your current meter count and at 110% of your current meter count. The difference in how those numbers move tells you whose incentives are aligned with yours.
Review SMART360's utility software pricing model as a benchmark for what transparent, scalable pricing should look like in this market.
Implementation fees, data migration fees, training fees, additional module fees, API access fees, and premium support tier fees are all common add-ons that can add 30–60% to the sticker price of utility software. Ask for a complete list of every cost category that is billed separately from the base subscription.
A good answer: A clear line-item breakdown of what is and is not included, ideally in writing before the contract stage.
A red flag answer: "We'll work that out during scoping." Scoping happens after LOI. By then, switching costs make walking away expensive.
It is also worth asking whether a free trial or proof-of-concept period is available before full contract commitment. SMART360 offers a 9-week free trial — a vendor who is confident in their product will let you verify it before you commit.
Utility operational data — customer PII, payment information, AMI read data — is a high-value target. The 2021 Oldsmar, Florida water treatment attack was a reminder that utility infrastructure is not abstract to ransomware actors. Your software vendor is a significant part of your attack surface.
Minimum certifications to require: SOC 2 Type II (demonstrates ongoing security controls, not just a point-in-time audit). Ask also about data encryption standards (AES-256 at rest, TLS in transit), multi-factor authentication, role-based access controls, and audit trail logging.
A good answer: SOC 2 Type II report available on request, named security certifications, documented incident response policy, and a clear answer on where your data is hosted (country, cloud provider, data centre region).
A red flag answer: "We take security very seriously" followed by a reference to their website's trust page. Ask for the report, not the marketing copy.
The America's Water Infrastructure Act of 2018 (AWIA 2018) requires all community water systems serving more than 3,300 people to conduct a risk and resilience assessment and certify an emergency response plan every five years. Your software vendor should be able to demonstrate how their platform supports documentation, audit trail, and reporting obligations under AWIA.
In addition, EPA Safe Drinking Water Act reporting, Lead and Copper Rule compliance tracking, and state-level monitoring program data submissions are recurring obligations for most municipal water systems. Ask the vendor to walk you through — specifically, in the product — how those workflows are handled.
Ask to see SMART360's security and compliance documentation as a reference point for what adequate regulatory support looks like in a platform at this market level.
The sales team you have been talking to is not the team you will be working with once the contract is signed. Ask specifically about the post-go-live support model: Who is your named customer success manager? What is the SLA for critical issue resolution (e.g., billing system down on billing day)? Is there a 24/7 support line for operational emergencies?
Ask about product update cycles as well. Cloud-native platforms release updates continuously — ask how updates are communicated, whether they require any action from your team, and whether configuration customizations are preserved through updates.
This is the most important question on the list, and the most commonly skipped. Reference calls are your best source of information about what it is actually like to work with a vendor — not what the implementation looks like in a demo environment, but what it looks like at 6pm on a Tuesday when a billing run fails and your customer service team is fielding calls.
Ask for two references: one at a utility at roughly your meter count, and one who went live within the past 18 months. The recent reference will give you current information about the vendor's support quality; the same-size reference will give you relevant operational comparisons.
A vendor who can only offer references significantly larger than your system, or who requires you to sign an NDA before connecting you with references, is managing your information access. That is a meaningful data point about how they will manage your relationship post-contract.
Use this table in vendor demos. If a vendor gives you a response in the left column, the right column is what it usually means in practice.
Once you have run every vendor on your shortlist through the 10 questions above, use this scoring framework to compare them systematically. Score each category 1–5 based on the quality and specificity of the vendor's answers, then multiply by the category weight. The highest weighted score wins the evaluation — not the best demo or the most familiar brand name.
A vendor scoring above 4.0 weighted average across all five categories is a strong candidate. A vendor scoring below 3.0 in any single category — regardless of overall score — warrants a follow-up conversation before advancing to contract stage.
How long should a water utility software implementation realistically take?
For a small to mid-sized municipal water utility (3,000–100,000 meters), a well-structured implementation with a purpose-built platform should run 12–24 weeks from contract to go-live. This includes data migration, configuration, staff training, and a parallel billing run to verify accuracy. Enterprise implementations with large vendors routinely run 12–18 months.
What is the difference between per-meter and per-user utility software pricing?
Per-meter pricing charges a fixed rate for each active meter in your system, making costs predictable and proportional to operational scale. Per-user pricing charges per staff member with system access, which creates unpredictable cost growth as your team expands. For most small and mid-sized utilities, per-meter pricing provides significantly better long-term cost control.
Does AWIA 2018 apply to my water utility?
AWIA 2018 requires all community water systems serving more than 3,300 people to complete a risk and resilience assessment and certify an emergency response plan. If your water system serves above that threshold — which most municipal systems do — AWIA compliance is a current obligation. Your utility software vendor should be able to support your documentation and reporting requirements under AWIA.
What data should I ask a vendor to migrate from my current system?
At minimum: full customer account history, billing records for at least 24 months, meter inventory and read history, active service order records, payment history, and any compliance documentation tied to customer accounts. Ask the vendor to provide a data field mapping document before migration begins, so you can verify completeness before go-live.
How do I check a utility software vendor's security credentials?
Request their SOC 2 Type II report — this is a third-party audit of ongoing security controls, not a self-certification. Ask specifically about AES-256 data encryption at rest, TLS encryption in transit, multi-factor authentication, role-based access controls, and audit trail logging. Ask where your data will be physically hosted (cloud provider and data centre region).
