With all due respect, this is more often than not what IT people think is happening, meanwhile the person signing the check is talking behind their backs to see if anyone else in the industry is using the product and how they're using it.

It's more prevalent in certain industries than others, and some IT people may have more sway than others, but inferring that logos aren't valuable is a terrible take.

Not necessarily the logos in the presentation, but I saw a lot of purchases where knowing someone who used the product in other similar companies was a decisive factor in the purchase. These meetings that you mention would almost always involve something in the lines of ”I will ping a friend on company X using this and check what they think of it”. Or the product was being considered in the first place because someone had worked on a company that used it or a friend working on another company have recommended it.

When I worked in Enterprise IT evaluating new products for a Fortune 50 company it was pretty much the same way. The three biggest things that we looked at were functionality, support and the stability of the company.

We needed to know that it could do what we needed it to do and that there were enough support resources that we could get someone on the phone if we had an emergency. It is not cheap to integrate new software into the systems and processes of a large company so we also needed to know that we weren't going to put in that effort and then have the company go under a year later.

Support and stability were the two biggest issues that limited adoption for early stage startups. We didn't care if you had any big name customers. We just needed to know that your product did what we needed and you'd be able to support us for the long term.

Agree with all of that, except that for some companies logos are used as a substitute for internal expertise.

Most people who know what they're about will also know that companies sometimes pay to have other companies use their product, just for the logo on the presentation. Or that it could just be used in one little local office of a multinational. Or that it's just shelfware, bundled with whatever it is they bought that they actually wanted.

Everyone else thinks, "Oh wow, X are using it? Must be good!" And it grabs those people as customers. And that's why it's done.

I speak to a lot of enterprise buyers ands startups and it's definitely a major issue when it comes to buying products, especially from a startup.

There's a big difference between what a product does in theory vs in practice - and social proof is a big guiding factor for what it can do in practice.

> when I worked in Enterprise IT, and this was a factor in our decision-making literally zero times.

I believe this (i.e. credibility) is a necessary, but not sufficient, requirement in B2B sales. If a company/product doesn't establish enough credibility it won't even be considered for further discussions/approval in many cases. It seems that in your purchasing experience the credibility criteria was already met, so your team didn't even bothered to review the "many logos" slide from the sales pitch.

Many B2B startups (including my own mobile market research startup) struggle to reach this credibility threshold. It's a critical factor for scaling sales. Most big companies aren't willing to buy from a startup they've never heard of, no matter how great their product is.

> cheaper than the "build" option with internal talent

I'm curious how that gets evaluated, is it more of a ballpark estimate or is there a more formal process involving engineering teams providing time and effort estimates?

It’s got to do with buy-in-risk. How much of a risk are we willing to buy into? If they have other enterprise customers, there are things they should already set their org for , like uptime-support for SLAs etc

Sounds like The Chasm [0] to me. Conservative early majority people are by definition the majority and in enterprises probably even more so.

[0] http://beza1e1.tuxen.de/crossing_the_chasm.html

Hm. I think of my time in IT at big finance. Where the software solution was bought and paid for before IT even knew what was happening. For many enterprise IT is not the King you make them out to be.

Cold emails can be a highly effective strategy, surprisingly.

OP here. This was in the original tweetstorm that got me thinking: https://twitter.com/ibringtraffic/status/1319732207410237440

Strongly believe that you should ask for payment - until then everybody gives nice feedback. But the proof of the putting is in pulling your card/checkbook/Purchase Order out and eating the pudding.

This definitely resonates. We’re building a product management/issue tracker and it sometimes happy that we have very satisfied users who are then forced into using Jira or something else because of company-wide mandates.

Yes in this case it can be seen as a necessary but not sufficient condition.

OP here. Always a good place to be in. Hard numbers is more valuable but you need to think about how to address the concerns else you will hit a glass ceiling, or the moment they find an alternative they will jump. Thinking about lock-in is very important.

Hi! We offer both monthly and annual billing. Sorry for the confusion- we’ll clear it up on the landing page.

We added the pricing with monthly billing cycles now. Thanks for catching it!