Talk about your next project
Okta case study

The lesson

Lead with the identity process that changed, then make each body section a different workflow the customer automated.

The move

The hero opens with the breadcrumb 'Customers > Juni' and the title 'Juni: automating its internal identity processes with Okta' over a desk photo. Beneath it, a company facts column names Juni, Financial Services and Okta Workforce Identity, beside three results: '100% of onboarding and offboarding for core apps automated from an IT perspective', '2 hours of IT effort removed per new hire' and '5 days of keyboard time saved by switching to chat-based workflows for access requests'. A large customer quote leads into sections that introduce Juni, then walk through 'Growth, meet security', 'Hands-off onboarding', 'Slack me some access' and 'Automating audits to accelerate growth'.

Why it works

  • Our readThe three result callouts summarize the operational value before the reader reaches the story.
  • Our readThe section heads name specific workflows, so an IT buyer can scan for onboarding, access requests and audits.
  • Our readThe named quotes from Josef You explain the before state and the after state in the customer's own words.

What not to copy

Don't copy Juni's financial management story, Slack access workflow or exact automation numbers. Keep the structure of headline, customer facts, result callouts, customer quote, then workflow-by-workflow proof.

More from Okta

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.