Talk about your next project
dltHub case study

The lesson

Give technical buyers the customer's full data stack as a labeled spec list before the narrative, so they can check fit before reading the story.

The move

The hero pairs the headline 'How Harness transformed 14 data pipelines in 14 days' and a one-line summary with a logo card listing Company, Location and Industry. A three-stat row follows ('14 sources', '2 weeks', '4 teams'), then a Highlights box and a 'Data Stack' list naming sources, destination, orchestration and transformation. The body runs through 'Challenge: Inefficient setup delays expansion', 'The Solution: Starting afresh, proving dlt with SQLMesh', with two quotes from Alex Butler and a pipeline diagram, then 'Results: Strengthening and streamlining infrastructure' as a bolded list, a 'Future' section and 'More customer stories'.

Why it works

  • Our readThe Data Stack list names Salesforce, Zendesk, MongoDB, BigQuery and SQLMesh, so a data engineer can see at a glance whether their own stack matches.
  • Our readThe challenge names the tools being replaced, Singer and Meltano, and the specific failure of unmaintained Taps, which gives readers with the same setup a reason to keep going.
  • Our readThe solution is told as an ordered sequence, first an Asana Tap test, then Salesforce, then a source registry and a CLI wrapper, which reads as a migration plan another team could follow.

What not to copy

Don't copy Harness's Singer-to-dlt migration details, the Continuous Data Flow CLI name or the matching '14 pipelines in 14 days' headline. Keep the logo and firmographic card in the hero, the three-stat row, the Highlights box, the labeled stack list, and the challenge, solution, results, future order with the engineer's own 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.