The title is somewhat misleading because only 48&#x2F;250 had actual pricing pages, the others had what really amounts to &quot;contact us&quot; pages for their sales teams. Fortunately it&#x27;s still an informative read, and even 48 pages are enough for meaningful discussion of pricing pages. The original post has additional infographics at the end of the article (a helpful way to reason about ideas contained within after going through it all in text): <a href="https:&#x2F;&#x2F;www.process.st&#x2F;2015&#x2F;12&#x2F;saas-pricing-pages&#x2F;" rel="nofollow">https:&#x2F;&#x2F;www.process.st&#x2F;2015&#x2F;12&#x2F;saas-pricing-pages&#x2F;</a><p>As a consumer I often feel like contact-style &quot;pricing&quot; pages are a way of trapping customers into a hard-sell. Granted some pricing structures are complicated out of necessity, especially those where usage plays a significant role in the cost to the provider (substantial bandwidth transfer, hardware&#x2F;setup, human resources). More often than not I immediately abandon any such service if contacting for pricing is the only option. It was surprising to see 80%+ (202&#x2F;250) of companies didn&#x27;t list their pricing because my personal real-world experience feels like the inverse.<p>The article discusses the reasons for the contact-only approach, which boil down to preventing biases for enterprise customers. While that&#x27;s understandable in some situations, not all SaaS is intended to target enterprise customers. It goes on to consider pros&#x2F;cons of the multifaceted concept that is tiered pricing. If read this much of my comment but not the article, go read it now!<p>(A couple typos for the author: &quot;boost revenue&quot;→&quot;boosts revenue&quot;, &quot;Abscense&quot;→&quot;Absence&quot;)