[jenkstom]

It's annoying to the person who needs to get details and pricing and who would love to buy the product but right now is just trying to find out if a project is feasible.

It's insulting in that they could just give me the information but they won't because they think I am too stupid to understand it "the way they intend it" (i.e., in a way that doesn't solve my problem or does so using mostly marketing buzzwords that cause endless technical implementation issues and waste so very much time).

The buzzword I've learned to dislike the most is "RESTful!". It means that your API is written by developers who don't my industry at all. And no, it doesn't matter what industry. RESTful means you've started with a set of premises that don't work in the real work except under very limited circumstances (like distributing media files).

It's self-destructive in that any normal people aren't interested in a sales pitch. They just want information. If you aren't going to provide that then you're at the bottom of the list and we're probably going with a competitor of yours unless you somehow find out that I need a similar product and you start calling upper management. That's the worst-case scenario... now we aren't implementing technology that fits into our use case and architecture, we're dealing with a push from senior management to use technology that doesn't work. We know that a sales call means your product sucks. Hard.

At face value no, this isn't a dark pattern. But experience tells me otherwise. If your product is "contact us for a quote!" then I already know it won't work and is overpriced because you have to work so very hard to "sell" it. Could I be wrong? Yes. Have I been wrong? No. In 30 years of doing this.

Wow... I guess I had a lot to say on this subject. I feel so much better now. ;-)