Many people probably will think "If you have to ask the price, you can't afford it". It also sounds like you might need to have time-intensive negotiations, which turns away people who want to get the product quickly.

If you have good reasons why prices are different for different people explaining that is ok, but if most people get the same plans anyways it is unnecessarily complicated.

In summary: If it's a low value item that doesn't offer much in the way of customization, it's often best to publish your prices to reduce the difficulty of sales.

As more customization comes into play and larger amounts of value are delivered, you'll want to think more and more about hiding prices so that they can be adjusted on a per-user basis.

I wrote a blog post about that a while ago... http://taprun.com/articles/should-consultants-hide-their-pri...

Thanks for the replies. While researching further, this guy suggests to not publish it until the product is in beta or in the very early stages, because we can learn a lot from the users. We are sort of here, although the UI is polished and the flow is tested, but I feel that not posting prices is not a good approach.

http://sixteenventures.com/beta-testing-pricing

Increasing Price Transparency: Implications of Consumer Price Posting for Consumers' Haggling Behavior and a Seller's Pricing Strategies

by Xubing Zhang and Bo Jiang

(Short answer: yes, post prices)