There’s a particular flavor of discomfort in grading your own homework and realizing you wouldn’t pass it. We got a taste of that recently, except the homework was our own pricing page, and the person grading it was also us. Somebody had to do it honestly, so we did.
Here’s the short version: we went through our product line by line and checked whether what we actually let a merchant do matches what our pricing page says they can do, depending on which plan they’re on. It mostly matched. Not entirely. We found a few places where the gap between the promise and the product had quietly opened up, and we closed it.
What’s the difference between a pricing page and the product itself?
Your pricing page is a promise written in marketing language: “Starter gets you X, Pro gets you X plus Y.” The product itself is a pile of code that has to actually check, every single time a feature loads, which plan the account in front of it is on, and decide whether to allow or block accordingly. Those are two separate things, written at two separate times, usually by different parts of a small team moving fast. They start out matched. Then the product changes — a feature gets reworked, a new one gets added, an old restriction gets refactored — and the pricing page doesn’t always get updated in lockstep. Nobody plans for that drift. It just happens, the same way a junk drawer fills up without anyone deciding to fill it.
What did we actually find when we checked?
We went through the pricing page claim by claim and tried to break it the way a skeptical customer would: log in on each tier, try the things that tier isn’t supposed to get, and see what actually happens. In a few spots, the code wasn’t checking as carefully as the pricing page implied it would. Nothing dramatic, nothing that cost anyone money or exposed anyone’s data — but real gaps between “here’s what you’re paying for” and “here’s what the software actually enforces.” We fixed what we found. It wasn’t a fun afternoon, but it was a necessary one.
Why does this happen even when nobody’s trying to cut corners?
Nobody sits down and decides to let a Starter-tier customer quietly use a Pro-tier feature. It happens in small steps: a feature gets rebuilt and the new version forgets to re-check the old restriction, or a feature gets added to one plan and someone assumes the gating will “obviously” carry over, or the pricing page gets reworded in a sales meeting and the engineering ticket to match it never gets filed. Every one of those is a small, forgivable, completely human miss. The only real defense is going back and actually checking, on a schedule, instead of assuming the page and the product are still telling the same story.
Why this matters to you
This isn’t just a story about us. It’s a habit worth borrowing for anything you pay for. The next time you’re on a free trial for an analytics tool, a marketing app, or anything else billed by plan tier, don’t just read the pricing page and take it on faith. Actually try the things your plan is supposed to include, and if you can see what a higher tier offers, try poking at those too. If something you shouldn’t have access to works anyway, or something you’re paying for doesn’t actually show up, that’s worth a support ticket, not a shrug. Pricing pages are promises. The only way to know a promise is being kept is to test it yourself, the same way we had to test ours.