[thomaslord]

It sounds like the issue noted above is less the actual pricing, and more that it's difficult to find out what the pricing is.

This matches up with my personal experience - I had to get in touch with an actual human and ask them for the pricing just to see if a project would be viable. I did get a relatively fast response that made the pricing very clear, but because it didn't come with any caveats (e.g. volume-based pricing or "we need to negotiate pricing on a per-client basis") it almost made the experience more frustrating.

Basically if your pricing is simple and universal enough that you could post it directly to the pricing page, you should post it to the pricing page. Especially for developer-focused products, hiding the pricing can lead to a serious reduction in conversion.

My use case is transaction data so the pricing for Stripe's competing product isn't posted yet, but if I was choosing between the two products and only one had pricing clearly posted on the website I'd immediately go with that one unless the pricing was so ridiculous that it wasn't affordable. And if the pricing was ridiculous, I'd probably assume that Plaid's pricing was just as bad.

Basically, I should be able to evaluate your product and its pricing without engaging with any of your employees wherever possible. I routinely remove companies from consideration because I can't plug them into a spreadsheet of prices without going back and forth with a sales team whose time I'll just be wasting anyway.