So far our team has been using Yodiz for about 2 weeks, and we're liking it quite a bit. In fact, since I manage presales and professional services also, I'm considering adding some more projects to it from those teams. It seems like it would be a good way to manage them.

However your pricing model is very odd. It's free for the first 5 users, then $3 per user per month for up to 15, then $7 per user per month after that. I would ask if this pricing is gradated (i.e. do the first 5 stay free or do I just start paying $18/month at the 6th user?) but a more general feedback is that this pricing model is just structured incorrectly.

For cloud pricing for a service like yours, you have 2 main options. You can price by edition or by user volume.

An example of edition pricing would be my own former employer, Salesforce.com:

http://www.salesforce.com/crm/editions-pricing.jsp

where they offer different capabilities at the different price points, but once you're in an edition, you pay the same amount per user per month.

An alternative would be a model like Github's, which I suspect is more appropriate to Yodiz:

https://github.com/plans

Here they price by repositories, but it's fairly close.

The way you're pricing now seems to discourage more users, especially if you're at the boundary -- "crap, if we go over 15 users we pay double!" Instead you should price it like:

$0/month: up to 5 users
$25/month: up to 15 users
$50/month: up to 100 users
$150/month (or whatever): unlimited users

That way companies are incented to add users, because the more they add, the more value they get out of their $X per month (until of course they hit the cap, but you have to make money somehow).

In any case, if I do add more users, I'll pay willingly, because in truth it's not that expensive; but if we come to rely on you, I'll have an increasingly vested interest in ensuring that you guys stay in business. So price like the big guys.