Usually too early you don't want many low paying customer which would imply too much support while you iterate quickly. A low number of high paying customer is much better.
It's also easier to lower the cost later than increasing it. It's hard early on to find the right price point.
If he doesn't sale as much as he want, he will adapt.
$12 / month is a low-paying customer. An ultra low paying customer. You can only offer minimal support at that price point.
Also, it’s easier to raise prices than to lower them. If you lower prices, you need to do it for your current users too or they’ll complain. If you raise prices, you can grandfather people in AND it can be used to incentivize people to buy before the price goes up.
The early stage is the perfect time to start charging. You get to see if it's got any real-world value for users. If nobody signs up then you can change direction or move on to something else.
Besides you don't want to be dealing with desperately trying to convert free users later, or worse, having to grandfather everyone in at free forever from your initial launch. Gotta pay the bills somehow.
Exactly what I thought as well, for what it is at the moment it isn't worth anything. Also I doubt that Analytics is a B2B only product, the majority will be private persons running their blog or hobby forum using it.
From the user perspective, being an early adopter of something that isn't really worth anything now can have external value of increasing the likelihood that you can drive the product direction towards something that will be very useful to you in the future (and without having to pay upfront costs of hiring a contractor and figuring out exactly what you want now). Especially if you're paying, people tend to listen to paying customers' feedback a lot more than web randos.
You could argue that if it is very early stage, then it's maybe not the right time to charge $12/month.
Or maybe it's the right time to charge $12/month?
Usually too early you don't want many low paying customer which would imply too much support while you iterate quickly. A low number of high paying customer is much better.
It's also easier to lower the cost later than increasing it. It's hard early on to find the right price point.
If he doesn't sale as much as he want, he will adapt.
$12 / month is a low-paying customer. An ultra low paying customer. You can only offer minimal support at that price point.
Also, it’s easier to raise prices than to lower them. If you lower prices, you need to do it for your current users too or they’ll complain. If you raise prices, you can grandfather people in AND it can be used to incentivize people to buy before the price goes up.
Amen.
If he had offered it for free initially, haters would say the author must think it is worthless.
This place is the last bastion of civility on the internet. Let's keep it constructive. Pretty please?
The early stage is the perfect time to start charging. You get to see if it's got any real-world value for users. If nobody signs up then you can change direction or move on to something else.
Besides you don't want to be dealing with desperately trying to convert free users later, or worse, having to grandfather everyone in at free forever from your initial launch. Gotta pay the bills somehow.
Exactly what I thought as well, for what it is at the moment it isn't worth anything. Also I doubt that Analytics is a B2B only product, the majority will be private persons running their blog or hobby forum using it.
From the user perspective, being an early adopter of something that isn't really worth anything now can have external value of increasing the likelihood that you can drive the product direction towards something that will be very useful to you in the future (and without having to pay upfront costs of hiring a contractor and figuring out exactly what you want now). Especially if you're paying, people tend to listen to paying customers' feedback a lot more than web randos.