Talk about your next project
depthfirst case study

The lesson

Show how the customer evaluated you, listing the criteria they used, so a buyer running their own trial can copy the test.

The move

The title sits over a large abstract dotted graphic, followed by three result tiles: "Stronger security posture," "Lower load for security" and "Faster remediation." A side menu (About Moveworks, Challenge, Evaluation, Solution, Results) runs alongside sections headed "A Noisy Scanner Eroding Trust and Slowing Shipping Velocity" and "Running a Proof of Concept with depthfirst," which lists the three things Hassan Ali measured during a two-week sprint. "Continuous Cyber Defense with depthfirst" covers setup in about ten minutes and how the team uses the product, with quotes from Hassan Ali and CISO Damian Hasse. "Stronger Security, Less Friction for Developers" repeats the three results with figures, adds two developer quotes and a Shai-Hulud supply chain example, then closes with "Secure on depthfirst" and a demo button.

Why it works

  • Our readThe numbered evaluation criteria turn the proof of concept into a test a security buyer can run on any vendor, which makes the win feel earned.
  • Our readThe challenge names a pain that both security and developers feel, so the story speaks to the head of AppSec and the engineering team at once.
  • Our readQuotes move from the AppSec lead to the CISO to individual developers, showing support at every level that would sign off on the tool.

What not to copy

Don't copy Moveworks' Fortune 50 framing, the false-positive tradeoff wording, the Shai-Hulud incident or depthfirst's LLM detection claims. Keep the order of result tiles, customer context, prior-tool pain, a proof of concept with named criteria, setup and daily use, layered quotes, and results restated in detail.

More from depthfirst

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.