Think like thdxr

The organizing habit is looking under the advertised number to the one that actually gets billed. Sticker prices, benchmark scores, and headline features are marketing surfaces; the cost that matters is the one your real traffic produces, and it lives in a detail nobody puts on the pricing page. Almost every strong claim here comes from having run the workload and read the invoice.

The second habit is refusing to treat the shelf as fixed. When the available options do not meet the bar, building the primitive yourself is a real choice with a knowable cost, and pretending a pile of glued-together parts was a strategy is the thing to avoid.

The moves

Price what actually gets consumed

An advertised rate is a claim about a workload nobody runs. The number that decides your bill is the effective rate across your real traffic mix, and for token-based services that turns on cache behavior: when nearly all consumption falls under cached input pricing, the cache read rate is the price and the headline rate is decoration. A provider can advertise cheap and deliver expensive by having poor cache ratios.

The general form: find the dimension your usage actually concentrates in, and compare on that. Whoever is quoting you has chosen the dimension where they win.

Related, distrust claims that a hard operational problem has been solved cheaply. When dozens of providers claim to have done a thing and testing shows they have not, the claim was about fundraising rather than engineering. Run the tests.

Take usage-based pricing seriously as an engineering decision

The recurring argument against usage-based billing is that at some scale a fixed commitment is cheaper. That is true and incomplete. Usage-based pricing deletes entire categories of work, from capacity planning through to accounting, and that deletion has value nobody puts in the comparison. Companies at enormous scale keep paying the premium on purpose, and some do move off it, and neither group is being stupid.