Should You Publish Your Enterprise Price, or Just Say Contact Sales?

Should you publish your enterprise price, or just say contact sales?

Publish a number or a range unless you have a specific reason not to, and if you cannot, publish everything else about the tier. The damage from hiding a price is rarely the price itself. It is that the whole tier becomes unevaluable, so buyers who would have qualified themselves in cannot.

This is one of the few pricing decisions where the common advice and the common practice point in opposite directions. Almost every marketing writer says to be transparent. Almost every enterprise tier in software says contact sales. Both groups have reasons, and the reasons are not the same for every company.

Here is how I think about the trade, and what I would publish if a real number is genuinely impossible.

What does hiding the number actually cost you?

Three things: self-qualification, comparison, and trust. A buyer who cannot estimate cost cannot decide whether to start a conversation, cannot build you into a budget, and cannot include you in an internal comparison they are running without talking to anyone.

The self-qualification loss is the expensive one and it is invisible in your analytics. Nobody fills in a form to tell you they gave up because they could not tell whether you were a ten thousand dollar decision or a two hundred thousand dollar decision. They simply do not appear, and your pipeline looks fine because it only contains people who did appear.

The trust cost is smaller than transparency advocates claim but it is real. Most experienced buyers read contact sales as a signal that the price varies by what they can afford, which is often accurate and rarely flattering. That impression sets the tone for the first call.

What does hiding the number actually buy you?

Pricing flexibility, some protection from competitors, and room for genuinely custom scope. If every enterprise deal really is a different shape, then a single published number is either misleadingly low or it scares off everyone below it, and neither of those outcomes serves you well.

The flexibility argument is the honest one. Enterprise contracts often bundle implementation, support commitments, security review, and seat counts that vary by an order of magnitude. A number that covers all of that is a number with no information in it.

The competitor argument is weaker than people think. Your competitors will find out what you charge from the buyers who are comparing you, usually within a quarter. What hiding the number really protects is your ability to charge different customers differently, which is a legitimate strategy and worth naming honestly rather than dressing up as confidentiality.

What do real pricing pages actually do?

The dominant pattern is numbers for the self-serve tiers and contact sales for the top one. On the day I checked, Linear's pricing page listed its Enterprise plan as Custom, annual billing only, with a contact sales action, while showing explicit numbers below it, including Free at zero dollars and Basic at ten dollars per user.

What Linear does well is that the Enterprise tier is not empty. The page lists what you get for the custom price: all Business features plus invoice and purchase order billing, SAML and SCIM, granular admin controls, enterprise-grade security, advanced org modeling, and migration and onboarding support. A buyer cannot price it, but they can absolutely tell whether it is aimed at them.

Webflow's pricing page follows the same general shape, carrying Contact Sales and Talk to sales actions for its enterprise-facing offerings, including Optimize. The pattern is so consistent across software that the interesting question is not whether to follow it, but what you put in the space where the number would have been.

Which buyers are you actually filtering out?

The ones who cannot start a conversation without a number, which skews toward smaller companies, technical buyers, and anyone evaluating several vendors in a week. You are also filtering toward buyers comfortable with a sales process, which may be exactly right for you.

That is the part worth being deliberate about. Hiding the price is a filter, and filters are useful when they are pointed at the right thing. If your enterprise tier genuinely requires a conversation to configure, filtering out people who will not have one is not a loss.

The failure is when the filter is pointed at the wrong thing. If your enterprise tier is really just your business tier with SSO and an invoice, then contact sales is filtering out qualified buyers to protect a flexibility you are not using. I made the adjacent argument about tier count in how many pricing tiers B2B software should have.

What should you publish instead of a number?

A starting point, a shape, or a unit. "Starts at" with a real floor is the strongest option. Failing that, say what the price depends on, say what the typical contract length is, and say what the minimum commitment looks like. Any of those restores the ability to estimate.

The single most useful sentence you can add is the one that says who the tier is for. Not in feature terms, in organisation terms: how many people, what kind of company, what triggers the move up from the tier below. A buyer who can locate themselves does not need the number nearly as badly.

The second most useful thing is honesty about the process. Saying how long a typical enterprise conversation takes and what happens on the first call removes most of the reluctance to start one. People do not avoid contact sales because they hate sales. They avoid it because they cannot predict what they are signing up for.

When is contact sales genuinely the right call?

When the scope really is negotiated, when implementation cost dominates licence cost, when regulated procurement is involved, or when your enterprise deals are few enough that each one is a project. In those cases a published number would be fiction.

The test I would apply is whether you could write a starting price that you would honour. If you can, publish it. If you genuinely could not, because the same tier has been sold at wildly different prices for defensible reasons, then contact sales is honest and you should focus on making the rest of the tier legible instead.

There is a related decision about how people enter the funnel at all, which interacts with this one, and I worked through it in self-serve trial versus demo request for B2B software. Hiding the price and requiring a demo are two separate choices that often get made as one.

How do AI answer engines change this decision?

They raise the cost of an empty tier, because an engine summarising your pricing can only repeat what is on the page. A tier described as Custom with a contact sales button gives an answer engine nothing to say about it, so your competitor's published range becomes the only concrete thing in the comparison.

This is a genuinely new consideration. Ten years ago a hidden price meant a buyer had to click. Now it often means your pricing is absent from the summary a buyer reads instead of visiting the page, and absence reads as more expensive rather than as unknown.

The mitigation is the same as the advice above. Publish enough structured detail about the tier that a summary can carry something useful, even without a number. I went into how pricing pages get read in this environment in designing a SaaS pricing page for the AI answer era.

What is the compromise that usually works?

Publish a floor for the enterprise tier, publish the variables that move the price, and keep contact sales as the action. You get most of the qualification benefit and you keep the flexibility you actually need for genuinely custom work.

The floor does not have to be your average. It has to be a number you would honour for the simplest possible version of the tier. Framed that way, most companies find they can publish one, and the ones that cannot usually discover that their enterprise tier is not a tier but a services business.

If you truly cannot publish a floor, publish a range of contract values you have actually signed. It is less precise and it is still enormously more useful than silence, because it lets a buyer decide in ten seconds whether to keep reading.

What should you do next?

Open your pricing page and read the enterprise tier as a stranger with a budget in mind. If you cannot tell whether it is for a company like yours, the problem is not the missing number, it is that the tier is described entirely in features.

Then try writing a starting price you would honour. If you can write it, publish it this week. If you cannot, write the two sentences that say who the tier is for and what moves the price, and publish those instead.

If you are arguing internally about whether to show the number, tell me what your enterprise deals actually vary on and I will tell you which side I would take. Let's chat.