A pattern most municipal stormwater coordinators recognize: the vendor sells you a platform. The platform looks great in the demo. Then your team needs a field added to the construction inspection form, a dropdown value changed on the source-control checklist, or a label renamed so the report uses the program’s actual terminology. The vendor sends a quote.
The quote is the problem. Configuration is what makes the workspace match how the program runs. If every configuration change is billed as a custom services engagement, the platform is structurally expensive to operate, not just to buy.
This post walks through what should be included self-service in any modern stormwater software, and what is actually fair to scope separately.
What should be included self-service
The configuration that should never trigger a paid services ticket:
Module toggles. A program without public participation should not see MCM 2 modules on its dashboard. A team without source control should not see source control inspections in My Work. Turning modules on or off is a tenant administrator decision, not a vendor decision.
Terminology renaming. The program already has language for catch basins, inspections, contractors, and BMPs. The workspace should use the program’s words. Renaming labels in a modern multi-tenant SaaS is a database column read at render time. It is not custom development.
Inspection fields per kind. Which fields show, which are required, what the labels say, what order they appear. Construction site inspections in a coastal program ask different questions than the same inspection inland. The form should reflect that without a quote.
Dropdown values. BMP types vary by region. Finding categories vary by program. Enforcement action types vary by ordinance. The dropdowns should be editable in the tenant.
Display settings. Default views, visible columns on the inspection list, dashboard widgets. The tenant administrator should control what the program’s coordinators see when they log in.
Site, contact, and asset inventories. Standard format imports (CSV, GeoJSON, shapefile) should be a self-service workflow, not a “data services” engagement.
What is fair to scope separately
A short, honest line about what custom engineering actually is:
- A workflow concept the platform does not yet support (a new record type with no existing analog).
- A bespoke integration with a non-standard system (proprietary CAD, a regional reporting portal with no export format).
- A substantial historical data migration that requires custom mapping logic.
- Procurement work that goes beyond a standard pilot or annual agreement.
These are real engagements. They take time. They are fair to quote. The dishonest part is when a vendor bills the first list (terminology, fields, dropdowns) as if it were the second list.
What “included self-service” should look like in writing
A few questions worth asking on a vendor evaluation call:
- Can a tenant administrator add or rename a field on an inspection form without filing a support ticket?
- Can a tenant administrator edit dropdown values on BMP types, finding categories, and enforcement actions?
- Can a tenant administrator turn off a module the program does not run?
- Is configuration logged on the audit trail the same way records are?
- What is the line between configuration that is included and custom engineering that is scoped?
A vendor that can answer the first four with “yes” and the fifth with a clear honest line is the vendor that does not bill back every program change.
How NPDESTracker handles this
NPDESTracker is being built around included self-service configuration. Module toggles, terminology, configurable fields, editable dropdown values, custom modules built from the platform’s configurable building blocks, and display settings are part of every annual plan. The full breakdown is on configurable stormwater software.
Custom engineering beyond the platform configuration tools is scoped separately during a kickoff conversation. NPDESTracker does not promise unlimited custom development. The honest line is on the pricing page, under “Scoped separately.”
To see how the configurable workspace looks on sample data, try the demo. The 60-day Guided Pilot at $999 is the most common starting point for cities that want to test the workflow on their own program, with the workspace configured around their permit and inventory. The inspection-focused entry points are on stormwater inspection software and MS4 inspection software.