The Hidden Cost of 'Enterprise Call Us' Pricing

The pattern

Open a B2B SaaS pricing page. The first three tiers have published prices: Starter, Professional, Business. The fourth tier is grey, says "Enterprise" or "Custom" and has a button labelled "Contact sales" or "Get a quote." There is no number.

This pattern is so universal in 2026 that nobody questions it. Salesforce does it. Zendesk does it. Most of the legacy helpdesk vendors do it. Workday, ServiceNow, Tableau, the same. It feels like the natural shape of B2B SaaS pricing.

It is not. It is a deliberate sales tactic with specific buyer costs and specific vendor benefits. This post walks through what the tactic is actually doing, the four ways it hurts buyers, the vendor incentives that drive it, and what the transparent alternative looks like in practice.

I want to be careful: contact-sales pricing is sometimes legitimate, particularly for genuinely custom deployments. The line I draw is whether the price is hidden because the work is genuinely custom, or whether it is hidden so the vendor can charge different customers different amounts for the same product. The bulk of "Enterprise: contact sales" buttons fall into the second category.

What "contact sales" actually means

In the typical SaaS sales motion, "contact sales" triggers a multi-step process:

1. You fill out a form. Marketing qualifies you against ICP criteria (company size, industry, geography, project timeline).
2. A Sales Development Representative books a discovery call within 1 to 3 working days.
3. The discovery call probes your budget, your evaluation timeline, your alternatives. The price is not discussed in detail.
4. You are routed to an Account Executive based on territory and deal size.
5. The AE schedules a product demo, typically 60 to 90 minutes, often with a Solutions Engineer.
6. After the demo, the AE produces a tailored quote based on your projected usage, your willingness to pay, and how strong your alternatives look.
7. You negotiate. The first quote is typically anchored 30 to 50 percent above the price the vendor would actually accept.
8. After 2 to 4 negotiation cycles, you arrive at a price. Total elapsed time: 4 to 12 weeks.

The whole choreography is designed for one purpose: price discrimination. Different buyers pay different amounts for the same product based on what the vendor learns about their ability to pay.

There is nothing dishonest about this in itself. Almost every market has some price discrimination. What is dishonest is calling it "Enterprise pricing" or "Custom solution" when the actual product is identical and the variation is purely commercial.

The four ways it hurts buyers

1. It defers the decision past your evaluation window

Most buyers have an internal evaluation timeline: 4 to 8 weeks for a software purchase of this size. Contact-sales pricing typically takes 6 to 12 weeks from first form submission to signed contract. The maths is not coincidence; the long sales cycle is a feature of the model, not a bug.

The buyer cost is real. By week 8 of an evaluation, the project has accumulated sunk costs (demo time, internal review meetings, integration scoping). Walking away to evaluate a different vendor means starting over. Most buyers do not, even when the eventual quote is higher than expected.

2. It lets the sales rep anchor on your budget, not on the product cost

The discovery call is structured to extract your budget before the price is mentioned. Once the rep knows you have £50,000 a year approved, the quote will land at £48,000. If you had said £20,000, the quote would have landed at £19,000. The product is the same.

This is the price discrimination happening in real time. The rep is not lying; they are doing the job their compensation rewards them for. The buyer cost is paying somewhere between 10 and 100 percent more than the same vendor would have accepted from a more disciplined or smaller buyer.

3. It obscures who is getting what discount

Without published pricing, buyers cannot benchmark against peers. You do not know if your friend's company is paying half what you are for the same product. The vendor knows. The asymmetry is the point.

In transparent markets, this kind of asymmetry corrects through information sharing (G2 reviews, public benchmarks, honest peer conversations). The B2B SaaS market has structural blockers to this correction, partly because contracts often include non-disparagement clauses that discourage public price disclosure.

4. It biases the evaluation towards the incumbent

After 8 weeks of vendor sales process, the cost of starting over is substantial. The contact-sales motion produces this stickiness deliberately. By the time the price is on the table, the buyer's internal stakeholders have committed to the project, the timeline is tight, and the alternative ("let us evaluate three more vendors over another 12 weeks") is operationally painful.

The result is that the published-price competitors lose evaluations they should have won. Their lower friction is not enough to overcome the sunk cost of the contact-sales journey already in motion.

The vendor incentives that drive it

Why do vendors hide their enterprise pricing? Three reasons that all reinforce each other.

1. Margin. Price discrimination produces 15 to 30 percent more revenue per customer than flat pricing. For a vendor with thousands of customers, this is the difference between a strong and a weak year.

2. Sales-team economics. The sales team is structured around the contact-sales motion. AEs, SDRs, Solutions Engineers, customer success managers all have compensation models that depend on the long sales cycle. Switching to flat pricing would require restructuring the sales organisation, which is operationally painful and politically fraught.

3. Defensibility against newer competitors. Newer SaaS vendors with flat pricing (us, and others) are commercially differentiated mostly on the pricing model. As long as the established vendor controls the contact-sales motion, the newer vendor's price advantage is harder to surface in evaluations.

None of these are conspiratorial. They are the rational response to the incentives every vendor faces. The point is that they are vendor incentives, not buyer incentives, and the buyer is the one paying the cost.

The transparent alternative

The alternative is straightforward: publish the price for every tier on the public pricing page. No "Enterprise: contact sales" button. No tier where the price is hidden.

For most SaaS products, the pricing maths works out close to the same. The vendor earns slightly less per large customer (because they are not extracting the maximum from each one) and slightly more in volume (because the sales cycle is shorter and the conversion rate is higher). Net margin is comparable; what changes is the buyer experience.

The buyer benefits are concrete:

• Faster evaluation. 1 to 3 weeks instead of 6 to 12.
• Lower negotiation overhead. The buyer can compare prices across vendors in an afternoon.
• Equal pricing across customers. Your peer at a similar company is paying the same amount.
• Clearer budget conversations internally. The price is on the page; finance can review it without booking a vendor call.

The vendor benefits are also concrete:

• Smaller sales team. No SDR layer, no AE-led negotiation cycles.
• Lower customer-acquisition cost. Higher conversion from form-fill to signup.
• Better word-of-mouth. Buyers who self-serve become advocates more often than buyers who endured a sales process.
• More predictable revenue forecasting. Pricing changes happen on the public page, not in 200 individual contracts.

For a vendor making the switch, the operational change is significant. For a vendor starting fresh, it is the cheaper and faster motion.

What KimonDesk does

We publish every tier price on the pricing page. Free, Pro at £49 a month, Growth at £149 a month, Scale at £499 a month, all flat. Annual prepay knocks 20 percent off any paid tier. Every feature is included at every tier; the tier choice is about team size and ticket volume, not about which features you get.

There is no Enterprise tier. There is no contact-sales button. The Scale tier covers organisations with 25 to 250 plus agents, with the same flat pricing model. For organisations beyond that scale, we have not yet seen a case where a custom contract was needed; if we ever do, we will publish the framework rather than handle it in private.

The cost to us is modest: we earn slightly less per large customer than the legacy vendors. We make it back on faster sales cycles, lower CAC, and the kind of public reputation that this post is itself a small example of building.

Two specific cases

To make the model concrete, two scenarios.

Case 1: an 8-agent team comparing Zendesk vs KimonDesk

The Zendesk evaluation: form submission, 8 weeks of sales process, final quote arriving at £14,000 to £17,000 per year (covered in detail in The True Cost of Zendesk).

The KimonDesk evaluation: visit pricing page, see Growth tier at £149 a month flat, multiply by 12 (or apply annual discount), arrive at £1,428 to £1,788 per year. Decision time: 30 minutes.

Both vendors land an offer. The buyer's experience of the two journeys is materially different. The buyer who is value-disciplined, time-pressed, or both will choose the transparent vendor.

Case 2: a 50-agent team comparing Salesforce Service Cloud vs KimonDesk

The Salesforce evaluation: form submission, 12 weeks of sales process, final quote depending on what they think you can afford. Service Cloud Pro publishes a per-user starting price; the actual deployment cost (with required Einstein AI add-on, with required platform add-ons) is hidden behind quote.

The KimonDesk evaluation: Scale tier at £499 a month flat, including everything. Contact-sales is not part of the journey; you can sign up self-serve and migrate.

For a 50-agent team, the maths works out heavily in favour of the flat-tier model. £499 a month is £5,988 a year. Salesforce Service Cloud for 50 agents typically lands in the £40,000 to £80,000 range. The 7-to-13x multiplier is the cost of the contact-sales pricing model on top of the underlying product cost.

What this post is not

This is not a "Salesforce is bad" post or a "Zendesk is bad" post. The contact-sales pricing model is a rational response to the incentives those vendors face. They built large successful businesses around it.

It is also not a "all custom pricing is bad" post. For genuinely custom deployments, custom pricing is appropriate. The line is whether the customisation is real (custom infrastructure, dedicated success managers, contractual terms that genuinely differ) or whether it is purely commercial (different customers paying different prices for the same product).

What it is, is an honest description of the trade. The vendor benefits from contact-sales pricing. The buyer pays for it. The transparent alternative exists, costs the vendor a small margin hit, and produces a better buyer experience by every measurable axis.

The closing word

The next time you see a "contact sales" button on a pricing page, you can decode it: the vendor is using the long sales cycle to maximise price per customer. That is fine, and you might still buy the product. But you can do so with eyes open about what the model is and what it costs you in time, in money, and in evaluation discipline.

The transparent alternative is not theoretical. It is on our pricing page right now, and it is on a small but growing number of competitors' pages too. The market is slowly correcting. The corrected version is better for buyers.

For the broader context on switching off a per-seat helpdesk, the comparison hub and the About page cover where KimonDesk fits and why we built it this way.

References

• Forrester, "The Hidden Cost of Custom Pricing in B2B SaaS," 2024 brief.
• a16z, "Pricing Models in B2B SaaS," industry analysis 2024.
• KimonDesk customer-experience interviews, Q1 2026, comparing self-serve flat pricing vs contact-sales evaluations.
• Salesforce Service Cloud pricing page (Service Pro starting price published; full deployment requires quote), accessed Q2 2026.