Talk about your next project
Verkada case study

The lesson

Break a public-sector case study into named constraints, then answer each one with the product behavior that removed it.

The move

The story opens with the customer name, the title, Joe Davis’s role, a product tag for Cameras, and a landscape image. A “Background” section explains that Moapa Valley Water District provides clean water to over 9,000 Nevada residents and needed a stronger surveillance system after a critical threat and a new water infrastructure bill. The body repeats a clear pattern: “Challenge #1: Budget & Time Constraints,” “Solution,” then the same structure for limited bandwidth in remote locations and poor coverage across facilities. A short “Conclusion” summarizes increased visibility across the district and ends with a custom demo prompt, followed by related customer stories.

Why it works

  • Our readThe background names the customer, the facilities, and the compliance pressure before the product appears, so the need feels operational.
  • Our readEach constraint gets its own challenge and solution pair, which makes a technical security story easy to scan.
  • Our readJoe Davis quotes carry the story, keeping the claims tied to the person responsible for the district.

What not to copy

Don't copy the water district setting, the Water Infrastructure Act of 2018 context, or the specific facility names. Keep the three-part challenge-and-solution structure around budget, deployment constraints, and coverage gaps.

More from Verkada

More case studies

Steal it for your brand.

Tell us what you want to make. We’ll talk through how to put these ideas to work for your brand.