Most utilities didn't choose spreadsheets because they wanted to. They ended up there because the alternatives didn't fit. The last decade of SaaS promised dashboards, workflows, automation — and in plenty of industries it delivered. But walk into a small utility's cross-connection control program and you'll still find the real system: an Excel file named Backflow_Master_2026_v3, a folder of scanned test reports, and a utility clerk who knows which rows not to trust. That isn't because utilities are behind. It's because the software never matched how the program actually runs.
What "Fixed Data Models" Means in Practice
Generic SaaS is built for scale, which means standardized workflows and a fixed data model. That works when the work is uniform. Backflow isn't. Try entering an assembly with two responsible parties — the property owner gets the shutoff notice, but the tenant schedules the tester — into a platform with one Contact field. There's no place to put the second party, so it goes in a notes field, and notes fields don't get certified mail.
Or take a test report. In a real program, a report submitted by a tester isn't a pass or a fail yet — it's awaiting review. Staff check the tester's certification number, the expiration date, the gauge calibration, whether the serial number matches the assembly on file. A platform with two statuses, Compliant and Non-Compliant, has no place for that report to sit. So the dashboard says compliant while the pending report was never approved. The dashboard is wrong in exactly the way that matters.
The Two Ways It Ends
Force a compliance program into a fixed product and one of two things happens. The first: the system gets bypassed. The clerk dutifully enters data for a few weeks, keeps hitting fields that don't exist — vacant service, assembly replaced during a remodel, owner disputes the due date — and within a month is back in Excel, because Excel never tells her a field is invalid. The vendor's dashboard keeps rendering. Nobody looks at it.
The second: the system survives, choked with workarounds. Fourteen custom fields named Misc1 through Misc14, each meaning something only one employee remembers. A status called Other-See-Notes. An export-to-spreadsheet step in the middle of every workflow, because the letters still get mail-merged in Word. Either way, the software has stopped being the system of record. It's just another place data goes to disagree with the spreadsheet.
Why This Is Changing Now
The cost of building software has dropped far enough that "custom" no longer means a six-figure project and a maintenance contract nobody can afford. It's now realistic for a small program to get software shaped around its actual rules — its enforcement timeline, its escalation policy, its letter templates — instead of adapting the program to fit a vendor's data model. The model is inverting: the workflow comes first, the software is built around it.
Tools vs. Systems
The shift isn't from SaaS to custom-everything. It's from tools to systems. A tool helps with one step: it stores assemblies, or it prints letters. A system runs the process end to end — the test comes due, the notice goes out, the report comes in, staff review it, the status changes, the next due date is set, and the audit trail shows who did each step. The test of a system is simple: when the state auditor asks why a shutoff notice went out, can you answer from the software, or do you answer from someone's memory?
Where MyFlow Fits
MyFlow is the system I built for this. It isn't a generic platform with a backflow skin — it's built around the compliance workflow itself: assemblies with their real relationships, test reports that move through review, notices generated from program rules, and a record of every action. The goal isn't to store data next to the existing process. It's to replace the fragmented one — spreadsheet, folder, mail merge — with a single system of record that works the way the program does.
If you're evaluating software for a compliance program, skip the feature list and run one real record through the demo: the assembly with two responsible parties, the test report that needs review before it counts, the account that just went vacant. If the product has no place for those, your staff will find a place — and it will be a spreadsheet.