←back to thread

No Calls

(keygen.sh)
1603 points ezekg | 2 comments | | HN request time: 0.429s | source
Show context
freedomben ◴[] No.42728008[source]
I'm a CTO who makes purchasing decisions. There are numerous products I likely would have purchased, but I either find a substitute or just go without because I won't play the stupid "let's get on a call" game.

If your website doesn't give me enough information to:

1. Know enough about your product to know that it will (generally speaking) meet my needs/requirements.

2. Know that the pricing is within the ballpark of reasonable given what your product does.

Then I will move on (unless I'm really desparate, which I assure you is rarely the case). I've rolled-my-own solution more than once as well when there were no other good competitors.

That's not to say that calls never work or don't have a place, because they definitely do. The key to using the call successfully (with me at least) is to use the call to get into true details about my needs, after I know that you're at least in the ballpark. Additionally, the call should be done efficiently. We don't need a 15 minute introduction and overview about you. We don't need a bunch of small talk about weather or sports. 2 minutes of that is ok, or when waiting for additional people to join the call, but beyond that I have things to do.

I know what my needs are. I understand you need some context on my company and needs in order to push useful information forward, and I also understand that many potential customers will not take the lead in asking questions and providing that context, but the sooner you take the temperature and adjust, the better. Also, you can get pretty far as a salesperson if you just spend 5 minutes looking at our website before the call! Then you don't have to ask basic questions about what we do. If you're willing to invest in the time to get on a call, then it's worth a few minutes of time before-hand to look at our website.

replies(30): >>42728440 #>>42729968 #>>42730113 #>>42730304 #>>42730478 #>>42730488 #>>42731122 #>>42731205 #>>42731562 #>>42731625 #>>42731654 #>>42731749 #>>42731845 #>>42732395 #>>42733222 #>>42733534 #>>42733736 #>>42733894 #>>42734213 #>>42735020 #>>42735376 #>>42736599 #>>42736685 #>>42738466 #>>42738777 #>>42740067 #>>42740099 #>>42740345 #>>42754672 #>>42786202 #
giancarlostoro ◴[] No.42730113[source]
Going to add the most important thing: It is perfectly fine to end calls early if it feels like it has phased itself out. Don't be afraid to do so! Everyone on the call is costing someone else a lot of income. This goes for internal or external calls.
replies(1): >>42730314 #
1. freedomben ◴[] No.42730314[source]
Yes, seriously. When a sales call is scheduled 30 minutes but 5 minutes in we have a conclusion, you get a lot of good will points from me if you thank me for my time, ask me if there's any other questions I have, and then conclude the call. You can even make this explicit with a quip like, "I'll give everybody 20 minutes back!" then it's clear you are being courteous with our time.
replies(1): >>42733522 #
2. giancarlostoro ◴[] No.42733522[source]
Some people dont know when to end calls early and everyone else is too polite to tell them to end it. I had a manager who made it a point to suggest to end a call early. I try not to force calls to end early unless I know everyone on the call. I notice when its all devs its really easy to suggest ending early vs when non devs are on a call unless a dev manager does it.