"A dark pattern is "a user interface that has been carefully crafted to trick users into doing things, such as buying overpriced insurance with their purchase or signing up for recurring bills"."[0]
By this definition, no, it's not a dark pattern. It may be a pricing strategy that you don't like, but not a dark pattern. It's an invitation to start a full discussion with the vendor about what you're trying to achieve.
Usually, you'll see "Contact Us" on the pricing page for enterprise services. If you're an enterprise buyer, you usually have lots of people on your team who want different things. You might have special requirements for your industry. You probably need to sign a contract for special provisions or services.
Or maybe the vendor is in a new market and they're trying to learn about their customers with an MVP. How many times have you seen the recommendation here on HN to set up a landing page and add a button that says "Email me if you're interested"? Same idea.
It ensures you are captured as a lead and establishes a human connection. Serious buyers have no problem getting on the phone.
The fixed price you were quoted is a starting point for negotiation. It's the "book price", aka the chump price. You're leaving money on the table if you're not haggling with them or finding a way to get a better deal.
Enterprise culture is to negotiate price. They have purchasing teams - multiple people whose entire job is to get a better deal than whatever is listed on the website or the first number quoted over the phone.
These people are hard nosed and have zero problems calling for a price. A good purchaser on a big enough deal would rather hunt down your sales team on linkedin and start talking than accept a list price on your website.
As an aside:
How many people would hang a sign around their neck with a fixed price when looking for non-contract employment?
How many slap a fixed price on the side of their house during a sale?
Fixed prices are in some ways the anomaly; haggling mostly disappears when the cost of negotiation exceeds the benefit of price discrimination and products and customers are fungible.
Personally I love fixed prices but most business does not work like that.
When my employer (only ~300 people) switched to salesforce it took 3 years from when we started looking at vendors to completing the switch. Buying software at this level is not just adding it to your cart, its creating a project that will take up huge chunks of dev time. Its a discussion between parties, and the price (contract) takes months of work to agree on.
We hired a consultant literally just for redlining. https://blog.pandadoc.com/what-is-contract-redlining-and-con...
Just because you can implement easily does not mean 90% of the vendor's customers can.
Without this you either end up with one of two scenarios. Scenario 1: companies price extremely high on paper and then negotiate down afterwards, as happens in the US health insurance markets, and it’s a nightmare. Or scenario 2 the producer ends up pricing for their profit maximizing volume, which at constant price means customers who realize greater utility are subsidized by those who realize the least utility.
Consider a very real example: AWS charges outrageous markups on bandwidth. This is because many organizations realize far greater value from the AWS ecosystem and are willing to pay. This prices out people who are more price sensitive, and means they end up using a competitor, even if Amazon would happily sell them bandwidth at a lower price. They simply can’t without canibalizing their fatter customers.
I’ve negotiated services for startups at a fraction of the cost of what larger companies are paying (on the order of 90% less) because of this dark pattern.
They're either getting income/revenue information that's connected in some way to the number you called from, or you're providing just enough information to enable them to quote a particular price for you.
[1] https://www.joelonsoftware.com/2004/12/15/camels-and-rubber-...
If your needs are served by the standard packages and you want to hook the thing up to your Slack for notifications, that's super. There is a pricing plan for that.
If you need basically a full year's worth of effort to hook this service up to your environment, and you want the experts involved with doing this integration, there's a kind of pricing plan for that, too.
The latter just does not look reasonable on a web page, because it starts with "it depends" and scales (non-?)linearly.
If your price point is much less than this you should probably just have users self-service with a credit card.
But the reason they do those dumb meetings is it seems related to their performance measurement, which is ultimately by revenue, but it is a function of deals and their stage through their sales pipeline. How do you measure the quarterly performance of a sales person when the average enterprise sales cycle can be 6-18 months? Number of deals in the pipeline per stage and probability of that revenue landing.
By forcing stupid meetings to get the most minor bit of information, they can move my "deal," into a pipeline stage that improves the perception of their performance numbers, independently of whether revenue is ultimately realized. If you are a startup they need those numbers for projections that go into investor and analyst presentations that get you the funding to stay alive, and it's why you don't want engineers to say something or add information that will collapse the superposition of everyone's ability to believe long enough to survive to a more stable state.
My experience has been that enterprise sales are bizarre political intrigues that are divorced from features and product qualities, where concreteness itself becomes the enemy. So, tl;dr: "contact us for pricing," isn't so much a dark pattern as it is the outer edge of an infinite existential void.
I'm sure there is a more optimistic explanation though.
1. There's not much competition for the product, so the seller has no reason to compete on price and make things easy to compare
2. The sales process / cycle for that industry requires so many stakeholders and agreements etc that pre-committing to a price range up front is just an unnecessary handicap. They'll be in negotiations with numerous executives with a prospective buyer potentially for years before getting a signature. In these situations the buyer is not a naive consumer, they're a corporation that can take care of themselves and giving out the price is a free point in that game.
3. They haven't sold anything yet. They are still in the research phase and are feeling out what people might pay.
The business execs that I'd have to involve to contact you for pricing are, firstly - cheap, secondly - are probably going to outnegotiate you, thirdly - introduces a whole level of complexity to the process that I'd rather just pick your competitor and ask for approval.
On the other hand, we offer a custom plan that has a contact us for pricing button. Because in that plan we are gonna do whatever we can to add as much value as possible for your business. Mostly integrations and updates on legacy systems.
The same idea applies when selling other products to companies, with slightly different dollar thresholds.
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. ;-)
There are only a few reasons where I could see 'contact us for pricing' being appropriate:
1 Volatility caused by unknown market or price war, where competitor keeps causing price stability issues.
2 Complex purchase - too many confusing options - so we have to have a sales person walk you through it. 'So you want a web page and you need a specific person to do it ...'
3 Contractual - in rare instances a vendor can purchase excess product, at a steep discount. But are not allowed to advertise the price.
All other options make me think of a used car salesman trying to figure out how much they can do you for.
That said, I'm shocked they'd do this for a simple product selling a single item. It wouldn't be worth the time spent on the phone.
You don't show the price because you want me to talk to a salesperson that has to justify the price. I don't want to talk to a sales person. I want a demo account if it's a service and a number for a technical person to answer questions
Save the pitch for someone who gives a damn
The sales person is an impediment to the sales process
I do clearly state pricing for the normal plans, otherwise that would just push away most of the customers.
Typical for overpriced products or middlemen-driven sales pipeline