My pricing page confused people and I only noticed from support tickets
We argued about our pricing page for a month. Three tiers, each with a paragraph of features, and every internal review ended with "looks fine to me." Then support tickets started arriving: people asked which tier they n
We argued about our pricing page for a month. Three tiers, each with a paragraph of features, and every internal review ended with "looks fine to me." Then support tickets started arriving: people asked which tier they needed, or said the middle one looked like a trap. The page was clear to the five of us who'd written it and unclear to everyone else.
PriceLens is the tool I built to get an outside read without another meeting. You paste a pricing page URL or your plan copy and it returns a teardown: a tier-clarity score, the positioning gaps, and three concrete copy fixes, benchmarked against common SaaS tiers. The value is the bluntness β it's not invested in the tiers you already have.
Why internal review fails at pricing
Everyone who works on pricing knows the logic behind each tier, so the page reads as obvious to them. That exact familiarity is what makes internal review useless here. You need a reader who doesn't know why tier two exists.
The teardown forces that outside view. It scores whether the tiers are distinguishable, flags where two plans blur together, and names the copy that makes a plan sound like a penalty. I've had it point at a sentence I'd defended in three meetings and tell me, plainly, that it reads as "the expensive one."
What the teardown actually returns
Beyond the score, I value the three copy fixes most, because they're actionable today. PriceLens also benchmarks against common SaaS tier structures, which helps when your instinct is that four tiers is fine and the data says three is cleaner.
It's a teardown, not a strategy session. It won't tell you what to charge or model your margins. Those are your calls. What it removes is the blind spot that comes from staring at your own page too long.
Honest limits
This is decision-support, not a pricing consultant. The score reflects clarity and copy, not market fit or willingness to pay. A page can be perfectly clear and still priced wrong, and the tool won't catch that. I use it to fix the communication layer, then make the money decisions with my own numbers.
How I act on the output
After a teardown I pick the single worst copy line and rewrite just that, then re-run. Small loops beat a big redesign I'll never ship. I also show PriceLens results to a friend who's never seen the product, because the score means little next to a stranger's "wait, what does this tier do?" The tool surfaces the candidates; the stranger confirms which one actually confuses. I've learned to trust the stranger over the score, since the number can be green while a real reader is still lost. That combination β a blunt automated read plus one naive human β has caught more problems than either alone, and it's cheap enough to do before every pricing change.
FAQ
What does PriceLens actually score?
It scores tier clarity β whether your plans are distinguishable β and flags positioning gaps and confusing copy, benchmarked against common SaaS tier structures.
Do I need to paste a URL or can I use copy?
Either works. You can paste the live pricing page URL or just your plan copy, and the teardown runs on what you provide.
Does it tell me what to charge?
No. It evaluates how clearly you communicate tiers and price, not whether the price itself is right for your market. Pricing strategy stays your decision.
Is the output a finished redesign?
No. It gives a score, the gaps it found, and three copy fixes as a starting point. You still apply judgment and test the changes with real users.
Originally published by Dev.to WebDev. Aggregated on AIWithGhost for educational purposes β full credit and traffic to the original publisher.