Generally on multi-tenant SaaS kind of systems you do have testing environments, but they're filled with garbage data, plus they are usually running pre-release versions that aren't yet ready for the light of day. It's where QA and CI/CD operates. Sales demos are generally done on a production environment, but on dedicated tenants that are set up with "nice looking" well-organized data (e.g. company is named Contoso, users have names like "Jason Anderson" and "Maria Ramirez"). Testing environments have users with names like "1111111" and "`<script>alert(window.domain);`"

I think it's probably a just laziness here, which makes some sense - it would be easy to set up 5 Flock cameras on the sales demo tenant sitting in a storage room at HQ, but it would make for incredibly uncompelling demo. Rather than set up a pipeline to run stock footage in as a camera feed, they got lazy and used real tenants.

Sounds like the testing stage is sticky? It could exist without the tooling to reset it to a known baseline and/or create multiple environments which would enable safe demos.