[tlogan]

From my experience, anyone looking to spend more than $1000 per month will want to have a conversation with someone.

They might not require any additional features, but many companies will need an account manager's email address to enter into their procurement system.

So “contact us” helps both sides.

[wussboy]

But I still want to know what sort of a ballpark I’ll getting in to. Is it $1/month per user? Or $100? Hiding all prices behind “contact us” makes window shopping expensive to me and I’ll likely just move along.

[derefr]

What does "looking to spend" mean? As a CTO, I don't shop SaaS "looking to spend" any particular amount of money; service providers can charge amounts for their services that are multiple orders of magnitude (!) apart, so I keep a completely open mind about how much it might cost to solve my problem (and in fact what type of service I need to solve my problem.)

For example: if my problem is "my egress-bandwidth bills are too high and my servers are falling over from the traffic", I could pay Akamai "contact us" dollars a month (probably thousands; maybe more than my egress-bandwidth costs!); or I could — potentially, depending on what I'm serving — pay Cloudflare $0 or $20 per month, with very legible rules about what would qualify me for those free/cheap plans. These aren't the same type of service: one's doing static pre-caching, mostly of large assets; while the other is doing short-term read-through caching, mostly of small assets. But they both solve an egress-bandwidth problem; and if you have no other constraints, then they are effective replacement goods for one-another.

[tlogan]

You are absolutely correct. ‘Looking to spend’ was not the accurate term to use. I should have said ‘looking to solve the problem,’ with a budget exceeding $1000/month.