Talk about your next project
Gridware case study

The lesson

Prove the product with one specific incident told in time order, and end on the customer's own estimate of what was avoided.

The move

The hero puts the title and a one-sentence summary over a dusk photo of power lines, with a Customer and Website card on the right. The body opens on Colorado's drought, wind and terrain, sets an unattributed italic quote about responding with "the right equipment", then names the gap: structural failures that never trigger an electrical fault. "Unprecedented Hazard Detection and Response Times" covers the mid-2023 pilot near Denver and Boulder with three numbered capabilities and the expansion. "Gridware AGR Averts Wildfire" then walks through March 17th: gusts over 45 mph, leaning poles, sensor detection, a crew dispatch, and Xcel's fire-spread model estimating 3,200 acres and 360 structures spared.

Why it works

  • Our readNaming the gap before the product, failures that don't trip protection systems, tells a utility reader exactly what problem the sensors solve.
  • Our readThe March 17th incident is laid out in sequence, so the reader sees what usually happens without the product and what happened with it.
  • Our readThe closing figures come from the customer's own fire-spread model, which makes the avoided-damage claim more credible than a vendor estimate.

What not to copy

Don't copy the wildfire framing, the red-flag weather detail or the unattributed quote; name the speaker in yours. Keep the order: context, the gap, the pilot with numbered capabilities, the expansion, then one dated incident ending on the customer's own impact estimate.

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.