Talk about your next project
Coiled case study

The lesson

Tell a technical case study as named stages of adoption, and let one practitioner's quotes carry each stage.

The move

The hero pairs the headline 'How EOLAS Insight processes petabytes of Sentinel-2 imagery' and a subhead naming Xarray, Dask and Coiled with a 5:09 video. Below, a two-column layout puts each stage heading on the left: 'Mapping Environmental Change at Scale', 'The Data Challenge', 'Starting Small: Building the Right Stack', 'Scaling Up: First Steps with Coiled', 'Breaking Through', 'Optimizing: Fine-Tuning for Cost and Performance', 'Business Impact' and 'Looking Forward: Expanding Capabilities'. Each right column holds a short paragraph and one or more boxed quotes, with a logo row for AWS, Xarray, GeoPandas and Dask near the top. The 'Breaking Through' section states the largest job processed nearly a petabyte using approximately 500 machines at its peak, and the change from local Dask to Coiled took two lines of code.

Why it works

  • Our readStage headings such as 'Starting Small' and 'Scaling Up' let a technical reader find the stage that matches their own setup and read from there.
  • Our readLong first-person quotes about CPU bottlenecks and wasted EC2 capacity sound like an engineer talking, which builds trust with an engineering audience.
  • Our readNaming the customer's existing stack (Xarray, Geopandas, Dask) shows the product fits tools the reader already uses rather than replacing them.

What not to copy

Don't copy the Sentinel-2 and petabyte details, the region-placement point about US West 2, or the environmental stewardship angle unless they apply to your customer. Keep the video hero, the left-column stage headings, a quote in every section, and the 'what changed in the code' detail.

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.