Talk about your next project
dltHub case study

The lesson

For a technical buyer, list the customer's full data stack before the story so the reader can check whether their setup matches.

The move

The hero pairs the headline and a one-sentence summary with a logo card listing Company, Location and Industry. Three tiles follow: "Code Reduction" (3,183 lines -> 472 lines for the critical pipeline), "Cost Savings" and "Migration Speed". Next come a Highlights box with three bolded points, then a "Data Stack" block naming sources, destinations, orchestration (Dagster) and transformation (dbt). The body runs through "Challenge", "Solution: dlt as the flexible, transparent, code-based 'LEGO Manual'", a "Bonus: Leveraging LLMs" aside, "Results" and "Future", with quotes from Lucas Fagliano, Senior Data Engineer, and closes on an About the customer box and More customer stories.

Why it works

  • Our readThe Data Stack list names tools a data engineer already knows, such as Kafka, Salesforce, Snowflake and Dagster, so fit is clear before any narrative.
  • Our readThe Challenge quote names Airbyte and Stitch and gives specific reasons they fell short, which gives the switch a concrete baseline.
  • Our readThe "LEGO" quote gives the product a memorable metaphor in the customer's own words, and the section heading reuses it.

What not to copy

Don't copy the energy-transition framing, the viral meme origin story or the named competitor comparisons unless your customer said them. Keep the logo card with firmographics, the three result tiles, the Highlights box, the stack list, and challenge, solution, results, future sections anchored by one engineer's quotes.

More from dltHub

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.