Once the alpha ends and the beta begins, I'll have a chance to reconsider these price points, and with data like this to back it up. It's expected that payment will become mandatory at that time as well.
Chaos Communication Congress had (has?) a model where regular tickets were priced very reasonably, and there were special "business tickets" that were marked up by a factor of 5 compared to regular ticket prices. The only difference is that you only get an invoice for a business ticket, so attendees who have their costs covered by a company need the business ticket, while individual attendees benefit from lower prices.
I don't know how invoicing works for a web service, but maybe that would be a model to consider? Keep the low price point for individual users, but use a lever like this to add some considerable markup for companies purchasing your services.
A while back the (large) company I worked for was evaluating two web service companies, one was ~4 times more expensive than the other. They both had all the functions we needed and from a practical point of view neither was better than the other. However the cheap one could only be paid for by monthly billing to a credit card and the expensive one was happy to send us quarterly invoices. We went with the expensive one.
Comments
Once the alpha ends and the beta begins, I'll have a chance to reconsider these price points, and with data like this to back it up. It's expected that payment will become mandatory at that time as well.
Chaos Communication Congress had (has?) a model where regular tickets were priced very reasonably, and there were special "business tickets" that were marked up by a factor of 5 compared to regular ticket prices. The only difference is that you only get an invoice for a business ticket, so attendees who have their costs covered by a company need the business ticket, while individual attendees benefit from lower prices.
I don't know how invoicing works for a web service, but maybe that would be a model to consider? Keep the low price point for individual users, but use a lever like this to add some considerable markup for companies purchasing your services.
A while back the (large) company I worked for was evaluating two web service companies, one was ~4 times more expensive than the other. They both had all the functions we needed and from a practical point of view neither was better than the other. However the cheap one could only be paid for by monthly billing to a credit card and the expensive one was happy to send us quarterly invoices. We went with the expensive one.