Talk about your next project
Obsidian Security case study

The lesson

Before you pitch your product, name the in-house alternative the customer considered and list exactly where it fell short.

The move

The headline sits over a company profile paragraph, a sticky Table Of Contents, and a customer photo with three stat tiles: '1500+ Employees Protected', '150 countries that BigCommerce operates in' and '25% reduction in SIEM costs'. The story moves through 'Flying Blind in the Fight Against Cyber War and Malicious Users' and 'Mitigating Insider Risk', then 'SaaS Requires Purpose Built Security' lists two numbered disadvantages of using the team's own SIEM. 'Why BigCommerce Chose Obsidian' gives the findings from a two-week evaluation as bullets, followed by numbered reasons: '1. Built-in expertise', '2. Versatile capabilities', '3. Hard Costs Savings'. The page closes with 'What's Next?' and a 'Get Started' demo block.

Why it works

  • Our readThe two threat sections, nation-state pressure and a peer's insider breach, give a security buyer a reason for urgency that they likely share.
  • Our readSetting the product against the team's own SIEM answers the 'can we build this ourselves' objection before the buying reasons appear.
  • Our readBulleted evaluation findings show what the trial uncovered, so the decision reads as the result of evidence instead of a sales claim.

What not to copy

Don't copy BigCommerce's Ukraine engineering context, the peer insider breach anecdote, or Obsidian's SSPM positioning claims. Keep the structure of profile and stat tiles, threat context, the in-house alternative's gaps, evaluation findings, numbered buying reasons, and a closing look ahead.

More from Obsidian Security

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.