Talk about your next project
Coiled case study

The lesson

Tell a technical case study as the customer's own path from one tool to the next, and let the engineer explain each step in a quote.

The move

The hero pairs the headline and a subhead, "Orchestrating distributed ETL and machine learning with Coiled and Dagster", with a 4:48 video of Jack Solomon, CTO and Co-founder. Below, section headings sit in a left column beside body copy on the right: "Introduction: Guac's Mission", "Modern ML for Better Forecasting", "The Scale Challenge", "Finding Simplicity with Coiled", "A Complete ETL+ML Platform", "Business Impact: Scale Is No Longer an Issue" and "The Future: Growing Without Infrastructure Constraints". A logo row for Google Cloud, PyTorch, XGBoost, Dagster and Dask follows the introduction, and an indented Solomon quote appears in nearly every section, including the sports betting odds example and "Adding Coiled was just a few extra lines of code."

Why it works

  • Our readThe story walks from pandas to Dask on one machine to Coiled across many, so a technical buyer sees where the product fits in a stack they likely already run.
  • Our readSpecific operating details, such as Coiled handling about 10% of ETL jobs and tuning jobs running across 30 machines, show how the product is actually used rather than claiming it is used everywhere.
  • Our readThe sports betting odds example makes the customer's own work memorable before the product appears, which keeps the piece readable for a non-engineer.

What not to copy

Don't copy Guac's food waste mission, the sports betting anecdote or the Dask and Dagster stack details. Keep the hero video of the customer's technical lead, the left-column headings with right-column body, a logo row for the stack, and a customer quote anchoring each section from mission to future.

More from Coiled

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.