This note summarizes a public Calendly customer story about HackerOne. It is not Tiercel Labs client work. The interesting part for security-conscious teams is not only the ROI—it is that scheduling automation had to clear SSO, SCIM, and compliance review before it was allowed to run.
Security first, then speed
HackerOne paused consumer-style Calendly usage while IT vetted tools for ISO 27000, FedRAMP, SOC 2, DPA/GDPR, and related compliance needs. The Customer Success team needed fast meeting booking; IT needed SSO and SCIM.
Calendly for Enterprise returned only after those controls were acceptable. Automation without identity controls was not an option.
What the numbers say
Calendly’s case study reports 169% ROI in twelve months, 588 hours saved on scheduling (about 73 business days), 114% more meetings year over year, and 88% more customers reached year over year.
Those gains came from removing email back-and-forth so Customer Success could spend time on enablement and renewals instead of calendar ping-pong.
SSO and SCIM as product requirements
Okta SSO reduced password sprawl. SCIM provisioning cut IT toil for creating and offboarding accounts. Compliance documentation from the vendor mattered for auditors as much as features mattered for CSMs.
For security companies—and any regulated buyer—these are table stakes, not nice-to-haves.
Lesson
Automate the coordination tax, but only with tools that survive your security review. Measure hours returned to customer work, not just meetings booked.
This remains a public vendor case study about HackerOne and Calendly—not a Tiercel delivery.