No Calls

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.

> 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.

> I've rolled-my-own solution more than once as well when there were no other good competitors.

I don't want to be rude but this sounds like terrible business decisions. I would say this is a case of cutting your nose off to spite your face but I suspect it's not your money your wasting rolling-your-own solution. Like it normally costs a lot more in dev resources to build instead of buying. And it seems like your doing it because of your ego and your unwillingness to play stupid games.

That's a significant over-simplification and ends up wrong in many cases. Build vs. buy is largely the same equation as rent vs. own in real estate or automobiles. Generally speaking, in the short term renting is almost always cheaper, but there's a break-even point at which buying (aka building) becomes cheaper. Owning the system also grants considerable ability to build it to be exactly what you need, instead of hacking around deficiencies and/or begging your account manager to get your feature approved and implemented.

There are plenty of situations in which the terrible business decision is to rent instead of build. The difficulty is that without knowing the future it's not always clear, so you have to use your best judgment and hope you get it right.

Edit: Also don't forget that roll-your-own doesn't necessarily mean starting something from scratch. In many cases I opted to use and self-host an open source project that sometimes is sufficient all on its own, and when not we can make changes to it. I almost never start a non-trivial project from scratch just to avoid buying, unless it's a major piece of our product or value proposition in which case you have to consider the risk of building on a foundation you don't control.