Talk about your next project
Okta case study

The lesson

Lead with the customer's own operational numbers, then use the story to show which workflows changed and why those numbers are believable.

The move

The page opens with the customer name in a breadcrumb, a large title, and a dark hero image. Beneath it, the LVT logo and customer facts sit next to five result callouts: “95% reduction in time to provision access for new hires,” “$500k saved annually,” “30% reduction in IT tickets,” “$500K-$1M costs avoided,” and “10% increase in productivity.” A named quote about access certifications running “on autopilot” leads into sections on protecting security operations, choosing Okta, and streamlining identity for employees, contractors, and service accounts. The story closes with an “About LiveView Technologies, Inc.” section, recommended stories, and an identity journey call to action.

Why it works

  • Our readThe opening title names the customer, the savings angle, and Okta Identity Governance before the reader reaches the story.
  • Our readThe result strip gives concrete operational and cost outcomes early, including provisioning time, saved licenses, IT tickets, and avoided costs.
  • Our readThe body follows a clean arc from siloed identity tools, to Okta selection, to onboarding, access requests, license management, and access reviews.

What not to copy

Don't copy LiveView Technologies, Inc.'s security operations context, NIST language, or specific Okta Identity Governance capabilities. Keep the structure of customer title, front-loaded result strip, named operational quote, problem, choice, implementation, results, company boilerplate, and related stories.

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.