Thread Maker

The angle

Most SaaS pricing pages are hiding the one thing buyers actually want to know, and it's not because they're enterprise-level, but because they're using undefined units like "per seat" or "per contact".

Why this one: This angle is specific and surprising because it's not just about simplicity, but about the lack of clear definition in pricing, which is a critical factor in buyer decision-making.

Strongest moment

Forty-one of the sixty could not answer that.

Where: The source content, when discussing the results of auditing 60 SaaS pricing pages.

Standalone insights

1. A significant majority of SaaS pricing pages fail to clearly define their pricing units, leading to buyer confusion.
   Source: "Forty-one of the sixty could not answer that."
2. Including a worked example in pricing can be more valuable than a feature comparison table.
   Source: "One sentence. That sentence is worth more than the entire feature comparison table underneath it."
3. Showing annual prices by default without clear labeling can be misleading and optimize for screenshots rather than real buyer needs.
   Source: "Twenty-three of the sixty showed the annual price by default with the monthly price hidden behind a toggle, and eleven of those did not label it - the number said $29 and the fine print said billed annually at $348."

Verbatim quotes

Thread

1/ I audited 60 SaaS pricing pages and found that 41 of them hid the one thing buyers actually want to know: the total cost. Not because they're enterprise-level, but because they use undefined units like "per seat" or "per contact".

2/ The problem isn't simplicity, but clarity. Four SaaS tools had genuinely complicated pricing, yet they provided a worked example - one sentence that said "a team of 8 with 20,000 contacts pays $312 a month". That sentence is worth more than the entire feature comparison table.

3/ Including a worked example in pricing can be more valuable than a feature comparison table. It gives buyers a clear understanding of the cost and helps them make informed decisions.

4/ But that's not all - 23 of the 60 SaaS pricing pages showed the annual price by default with the monthly price hidden behind a toggle. And 11 of those didn't even label it, making it easy to mislead buyers.

5/ This practice optimizes for screenshots, not for real buyer needs. It's like showing a monthly price of $29 when the actual cost is $348 annually. Buyers will find the truth, and you'd rather they find it from you.

6/ So, what can you do? Put one worked example under your pricing table, in a full sentence, with a real number. Define your unit in the same sentence. And show the monthly price by default, even if you'd rather not.

Preview line

I spent three weeks auditing 60 SaaS pricing pages and found a surprising trend: 41 of them hid the one thing buyers actually want to know.

The post

I recently conducted an experiment where I opened the pricing page of every B2B SaaS tool I could think of between $20 and $500 a month. Sixty of them. What I found was surprising - 41 of the sixty could not answer the one question buyers actually want to know: what will I pay?

The problem isn't simplicity, but clarity. Four SaaS tools had genuinely complicated pricing, yet they provided a worked example - one sentence that said "a team of 8 with 20,000 contacts pays $312 a month". That sentence is worth more than the entire feature comparison table.

Including a worked example in pricing can be more valuable than a feature comparison table. It gives buyers a clear understanding of the cost and helps them make informed decisions. But that's not all - 23 of the 60 SaaS pricing pages showed the annual price by default with the monthly price hidden behind a toggle. And 11 of those didn't even label it, making it easy to mislead buyers.