A short transcript from a YouTube talk comparing scheduling needs across roles and arguing that external-facing teams (e.g., sales) have distinct scheduling requirements. The speaker explains that Calendly’s strength is integrating with customer-facing stacks to make scheduling part of acquisition and business-outcome optimization, not just personal productivity.
Chapters
So I think on the surface, scheduling looks like a one size fits all problem, right? Like, you know, the scheduling needs of a, of a teacher are the same as a sales rep. At least on the surface it seems like that. But as you dig a little bit deeper, I think what you begin to realize is that the needs of external facing teams are again, are very, very different from internal facing professionals or, or even, especially sales teams, for example. Right. So it ends up looking like the scheduling needs end up sort of divergent by function and by role. And what we've done is really focus on people who are in external facing roles and that's how we end up winning. So there are people who want to use Calendly who maybe now use Google Calendar, but they there's just as many who were using Calendly and still use Calendly because of one of the comments that he made earlier, the breadth of our integrations. So being able to integrate into everything in your customer facing stack ends up meaning that Calendly is not just a scheduling product for you. It is part of a very important process like how you acquire customers. You can measure, you can track it, you can optimize for, you can optimize for a very specific business outcome as opposed to just purely productivity and efficiency in a nutshell.