Talk about your next project
Gridware case study

The lesson

Give the customer's problem a short name, define it in one sentence near the top, and make every later section show how that gap closed.

The move

A dark control-room hero carries the label "Case study", the headline, and a summary paragraph, with a side card listing Customer and Website. The body opens by naming PG&E as serving 16 million customers and defining Hazard Awareness Delay as the time between a hazard occurring and operators knowing about it. The sections that follow are "Hazard Awareness Delay Threatens Power Grid Safety", an integration section on joint work between PG&E IT teams and Gridware engineers inside the GDAT tool, and a bulleted list of operational improvements with bold lead-ins, then a quote from Tim Bedford, Principal Program Manager, Asset Performance Center. It closes with "Ready to Scale", two related case study cards, and a "Want to learn more about Gridware?" block with Contact Us and Schedule Call buttons.

Why it works

  • Our readDefining Hazard Awareness Delay in the first body paragraph gives an operations reader a single problem to track through the rest of the page.
  • Our readNaming the internal tool, GDAT, and the joint IT and engineering team shows a utility buyer that the product fit into an existing system rather than replacing it.
  • Our readBold lead-ins on each improvement bullet let a skimmer read the outcomes in a few seconds before the named quote confirms them.

What not to copy

Don't copy the utility and grid-monitoring details, the OMS and GDAT specifics, or the repeated claims of measurable improvement with no figures behind them. Keep the named problem defined up top, the challenge, integration, improvements and next-step sections, the bolded outcome bullets, and the customer quote placed right after the results.

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.