[offtop5]

The issue is you'll have to ask for credit card numbers in order to prevent abuse, so you're not really giving anything away. I would still evaluate anything you call free as I would any other product. Plus integrating into my workflow, pitching it to my manager, these things have a real cost.

I'd actually argue you shouldn't offer anything for free, but instead charge whatever makes sense factoring in you're going to have to support customers even if it was a free product. For example if your offering website uptime monitoring, but it's not accurate that can cause a real cost to me

[rapjr9]

If I was evaluating a free product I'd be wary of getting locked into it and then discovering missing features that I would have to pay for. That is essentially your business model, but even paying for a product I'd be wary of lock-in these days. Software can be complex enough that you don't discover missing parts or find the API is written in such a way that moving to a different platform is impossible without starting over, long after your business depends on it. So how does anyone know the product will remain free forever, is it open source? Can I fix problems on my own or will I have to pay you? Part of your marketing should be to show how those who try the free tier won't be locked in so when they grow they have a choice of buying from you, other vendors, or doing it themselves. Basically you are giving away a horse, but potential customers realize you have an ulterior motive and hence are going to be very wary of your gift horse.

[hinkley]

I've heard over and over again that the free customers cost more in support costs than the paying ones. Opportunity costs and burnout are both threats to the success of your projects.