Some good points here, but doesn't help the frustration as a potential customer.<p>The old adage when the price listed says '$ call us', it's a big number. For a certain class of application (ERPs, CMS, etc), sure does make sense, because pricing is very complex. At the opposite end of the spectrum, I would be baffled by a company that tells me the cost is tens or hundreds of dollars, but this doesn't exist.<p>The middle ground is products that are in the low hundreds to several thousands of dollars. There's a number of times where I have come across something that appears to fulfill a need I have, but that I could also do myself (whether by spending a week or because there's an open-source version that does 80% to base on).<p>Keep in mind there's always extra friction and admin overhead to dealing with commercial software, which has to be considered as part of purchasing: does it need a license to run on my build server? Does it have any kind of per-user charge, requiring extra system work to track? Are there redistribution licensing problems? Is there some stupid DRM that's going to cause me grief? Are you capable of dealing with a separate technical user (me) and paying user (my accounting department)? Am I going to have to deal with annual renewals? etc..<p>So if it turns out the direct cost is less than building it myself, it's a much easier decision. If it's significantly higher, now I have to really weigh the above against the opportunity cost and risk.<p>When I can't even see where in the spectrum the software lies, but I'm going to have to spend at least 30 minutes on the phone with some sales person to figure that out (plus probably deal with them periodically harassing me for the next year), the whole thing is that much less appealing.<p>I tend to move on to the next one, and only come back if there are no remotely similar options. It makes me sad a bit because there's no way this company can know they lost me as a customer merely by putting '$ call us' (even if the price would have been acceptable).