Talk about your next project
Grepr case study

The lesson

Put one stat each for the result, the effort and the disruption in the hero, so the buyer's three objections are answered before the story starts.

The move

The headline 'How FOSSA Reduced Their Logs by 95% Without Burdening Their Engineers' sits beside the FOSSA logo, above three stats: '95%' log reduction, '<1 hr' deployment time and '0 Changes' required to their app or existing dashboards and alerts. The body runs through 'FOSSA: Control Your Software Supply Chain', 'Hmmmm, Observability is Expensive!' and 'What Were the Options?', with Dave Bortz, VP Engineering, quoted in three parts across the sections. A 'Conclusion' states the 30% rollout and the 94% reduction in volume stored in Datadog, then shows a volume chart, before two closing CTA blocks.

Why it works

  • Our readThe '0 Changes' stat speaks to an engineering buyer's fear of rework, which a savings number alone does not address.
  • Our readNaming the 100+ custom dashboards and about 30 log-based alerts shows why switching tools was not an option, so the reader sees why a pipeline in front of Datadog fit.
  • Our readSplitting one executive's quote across the problem, the discovery and the result lets a skimmer follow the whole story through the bold and quoted lines.

What not to copy

Don't copy the Datadog cost framing, the S3 storage detail, or the sidebar tags, which list Jitsu and an unrelated use case instead of FOSSA. Keep the three-stat hero covering result, effort and disruption, one named customer quote threaded through each section, and a conclusion that states how far the rollout has gone.

More from Grepr

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.