← Back to context

Comment by ezekg

2 days ago

I touch on this at the end of the post. It's a short 15m 'discovery call', not a sales call. It's essentially a formality to intro each other, make sure we're human, and move onto email for any further discussion. Essentially, not all enterprises will shoot you a cold email to start the conversation, so this call is to capture those leads, with the end-goal of having all real discussion in email.

tl;dr: some enterprises will bounce if they don't see a 'book a call' button.

You seem to be doing this in good faith but honestly, there is no difference between 'Discovery Call" and a "Sales Call". The point is that the customer has to speak with someone first. I do think it is required for enterprise deals but the premise of your post seems to say otherwise.

  • There absolutely is a difference between one 15-minute call to see faces vs a pipeline of ten 30- to 60-minute calls discussing requirements, compliance, pricing, billing, onboarding, implementation, and support over the course of 6 months.

    • Sales calls usually start with a discovery call then move to those later stages in the pipeline though, so you're just calling a sales call by another name.

      4 replies →

  • Yeah, I was annoyed at this too but I think they're differentiating it by having the price already set, and it's just a way for Companies to do the intro dance if they want to. I know my immediate decision-makers at my company wouldn't use a vendor if there was no call.

But the entire article is based on the decision to remove "book a call" from the Enterprise pricing.

  • No, the entire post is around the decision to remove sales calls from the pipeline.

    • Still, you didn't remove it as you claim in the article. For a potential customer booking a call there's no difference, even if your intention is for it to only be a "discovery call". What did you actually change on the website?

      3 replies →