The Pricing Anchor That Reframes "Expensive"

Nobody knows what anything costs. That sounds like an exaggeration, but think about the last time you saw a price for something you don’t buy regularly. A plumber quotes you $400. Is that a lot? You have no idea. You don’t price plumbing jobs for a living. So you do what everyone does: you grab the nearest reference point and compare. Maybe it’s the last home repair you paid for. Maybe it’s your monthly car payment. Maybe it’s nothing at all, in which case $400 just feels like a big number, and big numbers feel expensive.

This is the problem with most pricing pages. They present a number and stop. The visitor, left alone with the number, reaches for whatever comparison is closest at hand. And the closest comparison is almost never the one you want. If you sell software for $99 a month, the visitor might compare it to Netflix, which costs a tenth of that. By that anchor you’re wildly overpriced. But if the visitor compared it to the salary of the employee whose time your software saves, $99 a month would look like a rounding error. Same price, same product, opposite conclusion. The only thing that changed was the anchor.

The word “expensive” doesn’t describe a price. It describes a relationship between a price and a reference point. When a visitor closes your pricing page muttering that it’s too expensive, what actually happened is that they anchored on the wrong thing, and you let them. You had one chance to hand them a comparison before their brain went looking for its own, and you spent that chance on a feature grid.

The fix is not to lower the price. It’s to control the comparison. The most honest version of this is to state plainly what the buyer is currently paying for the problem you solve. If your product replaces four hours a week of manual work, say so, and let the reader do the arithmetic with their own hourly cost. If it replaces an agency retainer, name the typical retainer. You’re not manipulating anyone. You’re doing the work the visitor would have to do anyway, and doing it with better information than they have, because you know your market and they’re seeing it for the first time.

There’s a cheap version of anchoring that I want to distinguish from the honest one. The cheap version is the crossed-out fake price: was $500, now $99. Everyone has learned to discount this, in both senses. When a visitor sees a struck-through price that was clearly never real, the anchor doesn’t just fail to work; it actively costs you trust, and trust was the thing your pricing page needed most. The honest version anchors against a real alternative the buyer genuinely faces: doing it themselves, hiring someone, using the incumbent, or ignoring the problem and eating the cost of ignoring it. That last one is the most underused anchor there is. Doing nothing always has a price. Most pricing pages never mention it.

Order matters more than people expect. An anchor works only if it arrives before the price does. Once the visitor has seen $99 and had their flinch, explaining afterward that it’s actually cheap is arguing with a first impression, and first impressions don’t argue back, they just leave. This is why the sequencing on a pricing page is a design problem, not a copywriting problem. What does the eye hit first? If the biggest element on the page is the number, the number is the anchor, and the number anchored against nothing reads as expensive. If the eye first crosses a plain sentence about what the alternative costs, the same number reads as a bargain.

I think about this in terms of what a skeptical visitor is doing in the moment. They have other tabs open. One of those tabs is probably a competitor. Their comparison process is fast, shallow, and biased toward whatever is easiest to compare, and the easiest thing to compare is the sticker price. Deep value is hard to compare across tabs; digits are easy. So the sticker price wins the comparison by default, unless you deliberately make something else comparable. Put the cost of the alternative in plain text near the price. Make the unit of comparison the one that favors truth: per seat, per project, per hour saved, whatever unit actually maps to how the buyer experiences the cost.

When I run scans with GazeSite, which I built to audit websites the way a picky stranger would read them, pricing pages fail in a consistent way: the price is prominent and the context is absent. The finding is usually some variant of a call to action floating next to a naked number. The remedy is almost never “hide the price.” Hiding the price is its own failure; visitors assume the worst about prices they can’t see, and the worst is a much scarier anchor than anything you’d write yourself. The remedy is to accompany the price with the comparison you’d make out loud if the buyer were sitting across from you. In person, no founder just says “$99 a month” and goes silent. They say what it replaces. The page should too.

The deeper point is that pricing objections are rarely about money. They’re about uncertainty. A visitor who understands exactly what your price buys, relative to what the alternatives cost, can decide it’s not for them, and that’s fine. But most visitors who bounce off a pricing page never got that far. They saw a number, felt a flinch, and closed the tab. The flinch was preventable. It came from a comparison you didn’t make, so they made it for you, badly.

Expensive is not a property of your price. It’s a property of the silence around it.