Talk about your next project
Gridware case study

The lesson

Build the case study around one dated incident, and tell what would have happened without the product next to what did happen.

The move

The hero headline sits over a street photo of the town, with a sub-head naming the stakes: "A turkey vulture, a 21 kV transmission line, and 130,000 people in town for Peach Days," and a Customer and Website card on the right. The body sets out the utility's territory and the problem of "hazard awareness delay", followed by a superintendent quote. "Brigham City Pinpoints Hazards Down to the Exact Structure" covers the pilot of approximately 50 Gridscope devices and lists three numbered capabilities. "Gridware AGR Catches an Ignition During Peach Days" retells September 6, 2024, then a counterfactual paragraph and two more quotes, closing on "Eyes on Every Structure", two related case study cards and a contact block.

Why it works

  • Our readThe sub-head puts the bird, the line voltage and the crowd size in one sentence, so a utility reader knows the stakes before the body starts.
  • Our readThe paragraph on what SCADA alone would have shown, with a patrol starting at one end of a two-mile line, gives the reader a baseline to measure the five to six minute response against.
  • Our readThree numbered capabilities with bold labels let a technical buyer see what the product adds over existing protection and SCADA before reading the incident.

What not to copy

Don't copy Gridware's festival and wildfire details, the UAMPS pilot route or the utility terms like reclosers and ghost faults. Keep the stakes-in-one-sentence sub-head, the customer card, the numbered capability list, the dated incident retold in order and the without-the-product counterfactual.

More from Gridware

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.