Section 1
The trade-off, stated clearly
Showing prices does two opposing things. On the plus side: it builds trust (transparency signals confidence and honesty, which matters in an era of high buyer skepticism), and it qualifies, prospects who see your price and proceed are pre-qualified on budget, so you waste fewer calls on prospects who can't afford you. On the minus side: it can cause prospects to self-reject before you've made your case, a prospect who sees a high number without context may balk and leave, when a conversation might have demonstrated the value and won them. So the trade-off is: transparency and qualification (you screen out the unaffordable, build trust, save call time) versus the risk of pre-emptive self-rejection (you lose prospects who'd have converted if they'd grasped the value first). Which dominates depends on your situation. The principle: showing prices trades transparency-and-qualification against the risk of pre-emptive self-rejection. (This applies the conversion, trust, and qualification research cited across this library.) Showing prices is honest and it qualifies, but it also lets a prospect reject you before you've shown your worth. Hiding prices gets you the conversation to demonstrate value, but it frustrates the transparency-minded and wastes calls on prospects who can't afford you. There's no universally right answer, only a trade-off you resolve for your business.
Section 2
How to decide for your business
Lean toward showing prices when: Your pricing is relatively standard/productized (a clear number that doesn't require heavy customization). Your value is clear enough that the price makes sense without a long conversation. Your prospects expect or value transparency (some audiences strongly prefer it). You want to qualify out unaffordable prospects and save call time (high inbound volume). Trust/transparency is central to your positioning. Lean toward not showing prices (or showing ranges/"starting at") when: Your pricing is genuinely custom (varies a lot by scope), so a single number would mislead. Your value requires a conversation to convey (high-consideration, where the number out of context invites self-rejection). Your price is high and benefits from value-framing before the reveal. You convert much better in conversation than on the page. The middle path (often best): show ranges or "starting at" pricing, or pricing tiers, giving enough transparency to build trust and qualify, while leaving room for the conversation to frame value. This captures much of transparency's benefit while limiting self-rejection. For many service businesses, this is the strongest default. (This decision framework and the ranges-as-default are my judgment.)
Section 3
The pricing-transparency decision, in one view
The takeaway: whether showing prices helps your conversion depends on a specific trade-off, transparency and qualification (build trust, screen out the unaffordable, save call time) versus the risk of pre-emptive self-rejection (losing prospects who'd convert if they grasped the value first). Lean toward showing prices when your pricing is standard and your value is clear; lean toward not showing (or ranges) when pricing is custom or value needs conversational framing. For many service businesses, the middle path, ranges or "starting at" pricing, is the strongest default, capturing transparency's benefits while limiting self-rejection. Decide deliberately based on your trade-off, not by gut or by whichever camp shouted loudest. (The framework and ranges-default are my judgment built on the cited research.)
Section 4
Execute This With AI
Step 1, Inputs. Note your pricing structure (standard/custom), your price level, your inbound volume, and how you currently handle pricing. Step 2, Run the prompt: You are a conversion strategist on pricing transparency. Showing prices trades transparency + qualification (trust, screening out unaffordable, saving call time) against pre-emptive self-rejection (losing prospects who'd convert if they grasped value first). Show prices for standard/clear pricing; don't (or use ranges) for custom/high-consideration; ranges/"starting at" is often the best middle path. My pricing structure: [standard/custom]. My price level: [X]. My inbound volume: [X]. How I handle pricing now: [DESCRIBE]. Do four things: 1. Recommend show / don't-show / ranges for my situation, and defend it. 2. Explain my specific trade-off (qualification benefit vs. self-rejection risk). 3. If ranges, tell me how to present them to build trust while framing value. 4. Tell me the one scenario that would change your recommendation. Take a clear position for my business. Step 3, The trade-off test. "For my business, do I lose more from prospects who balk at a shown price, or from wasting calls on prospects who can't afford me? That answer points to my choice." Tools and expected output. Any frontier chat model. Expect a show/don't/ranges recommendation, your specific trade-off, ranges-presentation guidance, and the scenario that flips it. The QA discipline: if uncertain, test it, pricing transparency's effect is business-specific, so where you can, try showing pricing (or ranges) versus not and measure the conversion and lead-quality impact. The model frames the trade-off and recommends; your test confirms which side your business is on. Whether to show prices on your service website isn't a flat yes or no, it's a trade-off: transparency and qualification (trust, screening out the unaffordable, saving call time) versus the risk of prospects self-rejecting before you've shown your value. Show prices when they're standard and your value is clear; withhold or use ranges when pricing is custom or value needs conversational framing. For many service businesses, ranges or "starting at" pricing is the strongest default, capturing transparency's benefits while limiting self-rejection. Decide deliberately based on your specific trade-off, and where you're unsure, test it, because the right answer is the one your own conversion data reveals.
Section 5
Keep reading
Keep reading in the Conversion-Centered Design cluster and across the library: [The Anatomy of a High-Converting Service Page in 2026](/blog/the-anatomy-of-a-high-converting-service-page-in-2026), [Conversion-Centered Design: A Field Guide for Service Founders](/blog/conversion-centered-design-a-field-guide-for-service-founders), [Designing for the Skeptical B2B Buyer](/blog/designing-for-the-skeptical-b2b-buyer). Also relevant: [Speed-to-Lead: Why Page Speed and Reply Speed Are the Same Conversion Lever](/blog/speed-to-lead-why-page-speed-and-reply-speed-are-the-same-conversion-lever), [The Service-Business Website Priority Stack: What to Fix First When Everything Needs Work](/blog/the-service-business-website-priority-stack-what-to-fix-first-when-everything-needs-work), [Pricing Page Lessons From Basecamp, Stripe, and Firms That Show Their Numbers](/blog/pricing-page-lessons-service-businesses).