Talk about your next project
Logz.io case study

The lesson

Put a short summary under the hero that names each product the customer uses and what it did, so a skimmer gets the whole case before the narrative starts.

The move

The dark hero holds the headline, Free Trial and Demo Request buttons, and the Monoova logo. A light box follows with a quote from Nicholas Tan, CTO, beside Customer, Industry, Headquarters and linked Products (Log Management, Infrastructure Monitoring, Distributed Tracing). Four summary paragraphs cover the company ($100 billion in payments to date), the platform, Kubernetes 360 and the Data Optimization Hub cutting metrics usage by 50%. The story then runs under four headings, from "Observability as the Heartbeat of the Monoova Payments Platform" to "Immediate Issue Identification with Observability Powered by Logz.io", and closes on a "You Might Also Like" row of three stories.

Why it works

  • Our readThe summary ties each named product to one job, such as Kubernetes 360 for the Kubernetes environment and Data Optimization Hub for metrics cost, so a buyer can map the story to the product list in the box.
  • Our readThe CTO's own line about expensive SaaS observability tools gives the cost section a reason to exist, voiced by the customer and not the vendor.
  • Our readThe payments-as-blood metaphor and the point that minutes of downtime cost revenue explain why recovery time matters before any feature appears.

What not to copy

Don't copy the Monoova payments metaphor, the national payment system details, or the Trivy and Falco security aside. Keep the quote-plus-firmographics box under the hero, the summary that maps products to outcomes, the descriptive section headings, and a closing incident example told in the customer's voice.

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.