I have worked in a similar project myself. We developed a very specialized tool for developers. Our boss decided that he did not want to mention prices on the website at first. Once we did some people complained publicly about the price although we invested months of development and the tool was pretty neat...
In general I think it makes more sense to tell the prices upfront and try to come up with a simple price model even if it means making compromises. You can always have something like this on your website: "If you think you do not fit in any price tier please contact us to find an individual price. The prices listed are meant to show what we have in mind for the general customers."
I would love to know the reason why some people think not having prices is a good idea. Care to elaborate?
But without any pricing guidelines published on http://www.viva64.com/en/order/, it could be anywhere between $1k to $100k, and people assume without even asking that they cannot afford it.
And what do you mean by "hard time?" How can a temporal concept take on attributes of a physical surface?
beep boop
Viva64 is not cheap, but it looks like an extremely solid tool; I'd imagine that for anyone with a reasonably large C/C++ codebase, it'd quickly pay for itself by offsetting time developers would otherwise spend troubleshooting, tracking down, and fixing bugs.
Talking to a vendor a couple months ago, they wanted $15k for a tool whose bug/security problem coverage they couldn't enumerate.