When one ladder counts in different periods: the allowance that looks twenty times bigger

A pricing page's allowances usually get less attention than its prices, and on one ladder in our records that is a mistake worth about a factor of twelve. DocuSign's entry plan includes five documents a month. The two tiers above it include a hundred per user per year. Set those numbers side by side as the page does and the step up looks enormous — twenty times the allowance. Convert the monthly figure to a yearly one and the same step is from sixty to a hundred, which is less than double.

Nothing about that is concealed: both periods are printed and each is correct for its own tier. But a reader scanning a table of allowances is comparing a monthly number with an annual one and will reach a conclusion the arithmetic does not support. Most of what looks like generosity in that upgrade is the unit changing underneath it. The check is to put every allowance on one footing — annual is usually easiest — before comparing any of them, and it takes about ten seconds.

This is the same shape as a trap that appears elsewhere in these guides, where a free tier's monthly cap sits in a table beside paid tiers' annual allowances. The direction of the error is always the same: whichever tier is quoted on the shorter period looks meaner than it is, and whichever is quoted on the longer period looks more generous. If a ladder mixes periods at all, the mixed rungs are the ones to normalise first.

The same category produced a lesson about our own readings rather than the vendors'. A first automated reading of SignWell's page returned a confident, well-formed result: a monthly price and an annual price where the annual figure was higher. That cannot be right on a page that advertises a discount for paying annually, and the contradiction was the only thing that flagged it — the figures themselves were perfectly plausible. The reading was rejected and the page re-read with a specific question about which figure belonged to which billing state. A number that contradicts a claim printed beside it is a signal, not a result, and that check catches errors no format validation would.

DocSend cannot be priced by us at all. Its pricing page returns a bot check that our reading did not clear, so we hold no figure for it, and none has been carried over from a third-party page. The consequence is worth stating plainly: a comparison between DocSend and anything else cannot be written from our records, and the build would refuse to publish one, because it requires a price ladder for both vendors in the market being published. The absence is the honest output rather than a gap to be filled.

Papermark is a different kind of difficulty and a more interesting one. Read from a European connection, its page served euros and carried an explicit currency toggle — so the price it shows is a function of where the reader is standing, and it changes if you stand somewhere else. That is the opposite of the vendors read the same morning that served one currency to everybody. For a vendor whose price genuinely depends on location, a single figure filed under one market would misrepresent it, so the record files the ladder under where it was actually read rather than pretending to a market it does not describe.

Taken together these four make a short checklist for any pricing page with allowances on it. Convert every allowance to a common period before comparing tiers, and be suspicious of any ladder that mixes periods between its own rungs. Check whether a figure contradicts something else printed on the same page, because internal inconsistency is the cheapest error detector available. And where a price is unavailable or depends on where you are, treat that as information about the vendor rather than as a blank to be filled with something plausible.