Talk about your next project
Lightdash case study

The lesson

Write the customer's buying requirements as a list before you show the product, then match each capability back to that list.

The move

The hero sets the headline over the line "A conversation with Yu Ishikawa, Principal Data Architect at Ubie," with a two-figure stat bar beneath: "600+" monthly PRs to their dbt repo and "80%" of employees use Lightdash. A left card holds the Ubie logo, the speaker, Industry, Size, Location, the data stack (BigQuery, dbt, GitHub, Terraform) and an "On this page" list. The body moves from "Meet Ubie" and a lead quote to "Governance at scale is hard," then a bulleted "What Ubie needed from BI governance" list, then "Building governance that scales with Lightdash," which names the other tools evaluated (Metabase, Looker, Preset) and covers dbt, AI and governance capabilities. It closes with "How Ubie put governance into action," "The results" and "Final thoughts," each carrying a quote, then a row of more stories and a CTA.

Why it works

  • Our readThe requirements list lets a data lead check their own needs against Ubie's before reading any product claims.
  • Our readNaming Metabase, Looker and Preset as tools Ubie explored tells a buyer comparing those same options that this story speaks to their shortlist.
  • Our readThe data stack in the side card lets a technical reader confirm stack fit at a glance, next to industry, size and location.

What not to copy

Don't copy the healthcare compliance angle, the medallion architecture explainer or the dbt and AI framing that belongs to Lightdash's product. Keep the stat bar under the hero, the side card with stack and jump links, the needs list before the solution, the named alternatives, and a quote closing each major section.

More from Lightdash

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.