If I had to use my credit card to get a free trial with Buffer for example, I would have never tried it (and eventually converted), but I guess it depends on the product.
If I had to use my credit card to get a free trial with Buffer for example, I would have never tried it (and eventually converted), but I guess it depends on the product.
But, those 120 signups you get from 1000 trial signups, meaning, for each signed up customer you need to support over 8 trials (support here means your time and to a lesser extent, your service's resources).
For the 60 signups in the case where the credit card was asked upfront, there were 200 free trial signups, ie a bit over 3 trials per customer.
So which is better depends on how much money (or time) you invested in getting the 10000 interested visitors to site (prior to them signing up), and how much money (ie. time and other resources) you need to spend to get them to become paying customers.
I think jasonkester below nailed it when stating if you need to interact individually with customers or in any other way have significant expense supporting trials, then that's really something to address. Again, at least in these kinds of products, obviously it does not apply to enterprise etc.
Less customers who are actually happy to pay me money for my product > More customers who don't care about the product as much, or at all.
As OP mentioned in his post: > Also, as an independent developer, it’s also very important for me to minimize time spent dealing with users who will never give me money for my product.
As an indie dev, it's a big difference.
The sorts of questions that people frequently ask in the first month, tend to be things that would fit in a FAQ. If you find yourself sending the same paragraph long email more than once, it's probably worth finding a UX tweak to the product to ensure you never have to send that mail again.
For my products, for every 100 trial customers, I'll exchange emails with maybe 5 of them. That mail is usually very short, pointing to the piece of documentation that explains the issue. Only in rare cases is any actual involvement required on my part.
That's baked into the product intentionally.
X-posted on FS: http://firespotting.com/item?id=1144