3 pricing contradictions in SaaS and how a public audit catches them

Pricing pages rarely break because somebody made one dramatic mistake.

They break because public claims drift out of sync across pages, docs, reviews, and help content.

That drift creates avoidable sales friction:

• prospects stop trusting the plan table
• support answers the same pricing question again
• sales has to manually explain what the site should have made clear

Three contradictions that show up constantly

1. Feature gating mismatch

The pricing page says a feature is included. Docs or help content describe it as an add-on.

2. Limits that move depending on the page

One page says "up to 10,000". Another says "fair use". A third implies something else entirely.

3. Retired claims that still look current

Old plan names, old features, or old packaging language stay indexed long after the commercial model changed.

What a public audit actually checks

ContractSpec's public audit starts with public sources only.

It scans the pages a buyer would actually read, then highlights the contradictions that deserve review first.

The promise is intentionally narrow:

• public sources only
• no internal access required
• shareable findings
• a short list of the contradictions most likely to confuse buyers

Why this matters for ContractSpec too

One reason we built the public audit is that the same problem appears in AI products all the time:

big claims on one page, narrower truth somewhere else, and no trusted operational path to clean it up.

If your public pricing story drifts, buyers feel it before your team does.

That is exactly the kind of contradiction a public audit should catch early.