Talk about your next project
AuthZed case study

The lesson

Tell a technical buy-versus-build story through one named engineer's quotes, so the reasons to buy come from the customer and not the vendor.

The move

The hero puts the Workday logo and headline over a one-sentence summary, with an "At a glance" box listing Integrations (SpiceDB, AuthZed Dedicated, Relationship-based Access Control) and Featuring Derek Li, Founding Engineer at Workday. A sticky side menu links to "About Workday", "A Complex Challenge", "Single Solution", "AuthZed Dedicated" and "Extending AuthZed to more services", with a "Talk to an engineer" button. After the short About Workday section, each section pairs prose with a Derek Li quote, including the cost-benefit reasoning for buying and an implementation timeline of planning in one or two months, some clients within three months and full production within five months. The page closes on "See AuthZed in action" and a row of more customer stories.

Why it works

  • Our readThe challenge section names the two old models, RBAC for pre-signature and ACLs for post-signature, so a technical buyer can match the problem to their own system.
  • Our readQuotes such as "We needed to focus on our legal products, not authorization" let the customer make the build-versus-buy argument a vendor could not make for itself.
  • Our readThe phased timeline in the customer's words answers the question an engineering lead asks first: how long until this runs in production.

What not to copy

Don't copy the Zanzibar and SpiceDB history, the legal-document security framing or the open source evaluation detail. Keep the at-a-glance box with the named speaker, the sticky section menu, a quote in every section after the About section, the buy-versus-build reasoning in the customer's voice, and the customer's own implementation timeline.

More from AuthZed

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.