The argument over whether to publish pricing on the website is one of the most predictable disagreements in B2B SaaS marketing. The marketing team usually wants to publish it. The sales team usually doesn’t. It comes up at every quarterly planning meeting and nobody changes their mind.
The right answer, at most company stages, is to publish at least a directional version of pricing. The reason the sales team resists is rarely the reason they say they do.
The stated argument vs. the real argument
Sales teams usually frame the case against published pricing as one of these:
- “Our pricing is too custom to publish.”
- “Published pricing will scare prospects who don’t yet see the value.”
- “It’ll give our competitors ammunition.”
- “Procurement will use it as the anchor and we’ll lose negotiation leverage.”
The actual reason, in my observation: published pricing forces sales teams to defend value before they’ve built rapport. When pricing is hidden, the sales conversation establishes pain, builds rapport, and then introduces price — at which point the prospect is psychologically committed. When pricing is published, the prospect arrives with a number in their head and the sales conversation has to justify it from the first call. This is harder. It’s also better for everyone — prospects who self-disqualify on price never reach a sales call in the first place.
What “publishing pricing” actually means
I am not arguing that you publish a full custom-pricing matrix. Three formats work depending on your business model:
- If you have packaged tiers (low touch, < $50K ACV): publish the tier prices in full. Three to four tiers, clear feature delineation, single-button CTA per tier.
- If you have semi-custom enterprise pricing ($50K–$250K ACV): publish a “starts at $X” anchor for each tier. Don’t publish ceilings — keep the negotiation room on the upper end. “Engine plan starts at $32,000” is honest, gives the prospect the anchor they need, and doesn’t tie your hands.
- If you have fully custom enterprise pricing ($250K+ ACV): publish ranges by deployment scale. “Typically $X–$Y for companies between [size A] and [size B].” Not as precise as packaged pricing but qualitatively a different experience from “contact us for pricing.”
The thing you should never publish is the word Custom in place of a price. This is the worst-of-both-worlds answer — it tells the prospect you’re expensive without giving them a number to react to.
What changes when you publish
Three predictable shifts from the engagements where we’ve worked through this transition:
- Inbound volume drops 15–35% in the first 60 days. Self-disqualification at top of funnel.
- Sales-qualified rate improves dramatically. The leads that come through are now pre-qualified on price.
- Sales cycle compresses by 10–25% because pricing isn’t a multi-call discovery process.
The first 60 days look bad if you only measure inbound volume. They look great if you measure pipeline quality. The transition requires alignment with whoever sets the pipeline-volume targets, which is usually the board.
The exception
One case where I’d hold back: if you’re early enough that you genuinely don’t know what your right price is. Pre-product-market-fit, post-pivot, or in active price experimentation. In those cases publish a placeholder ($X starting price) and reserve the right to change it. But don’t hide pricing because the conversation is uncomfortable — that’s an internal-team problem disguised as a market-strategy decision.
— Isabela
