You Can’t Make Money Charging $1 Per Month
softwarebyrob.com
softwarebyrob.com
Also, with regards to selling to teachers: I know you think they're stingy. I thought they were stingy. Empirically, there are at least 5,000 or so teachers in America who have paid $30 for a bingo game they used once. $1 is not not not not not not not not not not not an appropriate price point. For those teachers who think $30 is a lot of money, wish them happy fulfilling lives and move on.
Our potential global market ranges from people who tend to have very limited time, and who might therefore put a substantial value on services like ours that help them save it, right through to university students with very limited funds (and, let's be honest, a tendency to obtain media content through not entirely legal channels).
We've been working on ideas for pricing plans, and soliciting feedback from people within our market, but you never really know how things are going to go until you launch and ask people to put their credit card numbers into your system. That goes double when much of the informal feedback you get in the early days comes from friends/family who will have a tendency to be kind.
If anyone has any experience of this sort of decision and how they changed their plans over time, I'd love to hear it.
(Shameless plug: We're also interested in any experience of making informed decisions using metrics in the broader sense. Unfortunately my question last week only got a couple of votes before it fell off the New page, but please feel free to comment there as well: http://news.ycombinator.com/item?id=2686151)
Do you think that's appropriate, or it needs to be even faster?
I get the point cashflow limits rate of growth, of course.
Viral word of mouth is nice, but it usually takes years to get there.
You launched Pinboard to a crowd which already knew & loved you, at a time when everybody thought Delicious was about to fall over and die. Furthermore, you had novel marketing features - the "the price increases per user" thing, which was clever enough that people checked Pinboard out JUST to see it in action.
That is marketing -- and if you subtracted how much those early customers paid from the amount newer customers pay, that is your advertising cost. A discount is still a marketing expense.
And as for the Bedbug Registry, it's not a product - it's free. Furthermore, you serve desperate and angry and frightened users. They are much more likely to seek you out by Google than any other kind of customer. There is no equivalent level of desperate users for most software.
However, college students, gamers, and programmers (i.e. HN readers) are some of the stingiest people on the planet. Github charges $7/month for repo hosting, and still gets customers. There's a lot more teachers than programmers, and they won't feel like n00bs for paying for something they could roll themselves, so they will pay more than $7 for a basic service.
I ran a website for a couple of years without thinking about turning it into a business. Finally, shortly before I graduated, I decided that I need to make money from it, otherwise I can't sustain it any more. Over the years, 30,000 people used my "startup" and in the end, I had a round 5,500 active users.
I thought a lot about the pricing model, but turning a free service into a paid one, is not easy and truth is, I'll never find out how it would perform with a different pricing model. So I just made a decision and tried it. I decided against freemium and started charging 1€ at the beginning of this year. The intention was to make it a no-brainer and convert as many users as possible. I converted about 50% of them. People pay either 6 or 12 months in advance (to lower the transaction costs).
My greatest fear was that there would be a lot of people who are not satisfied and want their money back or that I'll end up spending a lot of time on support emails.
Thruth is, from now 4,000 paying customers. I had exactly 1 person who wanted his money back. I receive about 2-5 emails per day, mostly telling me how great the service is and what kind of features they would like to see.
I literally spend 10 minutes per day on customer support.
Fact is, it depends on your business and something that doesn't get mentioned in the blog is that people don't care too much about a lousy dollar or euro per month to complain about something (some do, however, but rarely).
The other option is wire transfer (which is very common in many European countries unlike in the US). The advantage here is that nobody needs to share any personal information. I just receive the money on a bank account. So far, there was no need to process that money automatically. I just wrote a little script, which greps for the transaction ID and the amount of money and prolongs an account accordingly.
I do not have an automated recurring payment system. All payments are "one shot", like a prepaid service. I can imagine that this is something people really appreciate. They feel more in control of their money and manually entering the payment information once every 6 or 12 months isn't too much of a hazzle.
Furthermore, I ask for as few personal information as possible. I don't store credit card information on my site. Heck, I don't even store real names in my database (but they are shown in PayPal).
For example, every day I'm dealing with someone who is convinced that the login system is broken. It's always user error, but it requires input from me pretty much every time, to the point of "here is a new temporary password. i've tested it and it works. please copy and paste it in"
Yes, we have an automated "forgot password" feature, but no matter how much automation you add there will always be people who avoid all that and demand personal attention.
It depends on the target audience. If it consists of geeks/people familiar with computers from an early age, then, yes, they might read that, otherwise you're going to do what MicahWedemeyer does (and what myself I'm doing, for a Groupon-clone website targeted to women): emailing your users predefined passwords, hoping they'll actually change them after the first time they use them.
You shouldn't be "hoping" anything.
> you should immediately route them into a password-change workflow on login
We already have that by default (we're using Drupal), but, as I said, most of our target audience finds it too complicated.
"Do any of these articles answer your question? If not, click the 'Submit my ticket' button below." One of the articles is titled "Can't log in? Try these steps..."
I assume that's catching some of them, but plenty still click the submit button. You will always have some people who navigate through every automated trap you set up. You can choose to ignore if you want, but your customer service reputation will suffer.
Beyond that, I think I'd start "firing" customers who are a huge support drain like that, especially those who are non-paying customers. Unless your site depends heavily on network effects, and a large percentage of visitors have password issues, it sounds like your time could be much better spent elsewhere.
Maybe it helps if you ask some people to perform a specific task while you're watching them (for example your friends). You can learn a lot from that about your design.
That said, you can't please everyone... if you're the one left serving the lowest-IQ users with the lowest-or-no-budget, you just give others an easier time making good money off more savvy software users. Before you know it, you have to close down shop for good...
YMMV.
Now, it's time to consider the extremely likely possibiliy that you could charge 5x the amount and without decreasing conversion by 5x. Which means you could probably be earning 5x than you are now (or more) without any extra work.
You have credit card fees - 2.9% + $0.30 (fair?) So that's $0.67 or 2985 customers (round up to 3000)
And IF you ever reach a substantial income, you could be in about the 25% tax bracket.
Now you take another .17 off of that, and you're down to $0.50 per customer.
You need 4000 customers per month to earn around $2000 per month at $1 per month per customer.
Now, if even a quarter of those people require even a lick of customer support, you've worked that money away with your time.
So I agree, at $1 per month, you really can't make any money.
I think it's possible to make that work, with some caveats.
First, you have to have modest expectations. Maybe you've got a service that you developed for personal use (as in my case) or as a hobby, but you figured it might be useful to other people as well. Maybe you'd be completely content with it making just a couple hundred bucks a month, with no aspirations of making it be anything more than that.
Second, you can't sink a lot of money into advertising your service, at least not at the outset. Which, of course, means you have to come up with more inventive ways to get the word out. Tough, but not impossible.
Third, you've got to primarily target people who understand that for $1 a month, they're not going to get very robust technical support.
And fourth, you're more likely to be able to pull of a $1-a-month price point if you also offer higher price points for premium services. In the case of FAB Apps Bundle, the premium service is targeted to small-business owners and people who manage their organization's Facebook Page.
You might as well just build some iOS apps for you niche at those numbers.
For example, I was looking for a service to do something very specific. It was something I could probably code in a weekend or so, but I figured there was some free or cheap site out there that could do it better. I did find a site that did exactly what I wanted, but it charged $5/month, or $50/year. Now for me, the service was at best a novelty, but I wouldn't have minded $10/year. I figured other people must be like me as well, and figured if I launched a website I could get some passive income and capitalize on that $10/year no-brainer type of thing.
Now, I never expected that I'd be making thousands of dollars each month, but wouldn't it make sense that I could capture a good portion of the market with a low cost point?
I think that's a key point. You look at the solution, think about the effort required for the value it gives you, and $10 feels about right.
For someone who can't produce it themselves, the value is usually much higher - and related to the size of the problem solved, not the amount of effort required to solve it. I don't know whether that applies in your specific case (for example, selling a 'one use' service on a subscription basis may not be the best plan), but it's a useful general point I thought of reading your comment.
The technical side is always much easier than everything else involved in running a business.
I think for everyone, there is a level at which they will not pay for something relative to what it actually does and how much they need it. For my example, it was something fairly trivial but still useful, probably the lowest MVP I've seen in quite some time. Even if I couldn't immediately make useable money with it, I feel that a low price point would be a great way to take a piece of the market that it was in, although I will fully admit marketing would have it's place as well.
I guess the better worded question would have been "Given all factors equal, what percent of the market would be swayed by a lower cost point?"
And the second question I would ask would have been "Even though you will not make money at $1/month, are there not services that are not worth $5-$7 dollars a month, but are worth more than free?" or even "Couldn't there be money in making cheap apps that together don't make much money, but combined add up to good income?"
By far, our biggest "competitor" is lack of knowledge. People don't know about us or our competitor. We're not trying to steal customers from each other. Instead, we just need to educate people that we exist at all. That's been my experience in most of these cases, especially for smaller apps that do one little thing. A huge amount of our effort in the beginning (and still to this day) involves letting people know we exist. Trust me, that takes a lot more work than just a weekend.
As for the "doubtful in a weekend" comment, I just find it highly doubtful that anyone can build a useful app that includes billing in a weekend. Payment systems are a real bitch. Plus, it's easy to gloss over the fact that "built in a weekend" usually means MVP, or even sub-MVP. From that point you have to keep building, market, promote and make sales. It's not like you just build it, flip the switch, and sit back collecting checks. It just doesn't work that way.
Or if you would have enjoyed doing something else even more. Opportunity costs. :-)
It's a shame, since I was enjoying the profits.
I was working my ass off, helping these clients, earning next to nothing.
When you start a new SaaS, a low price point can help you acquire a lot of customers/credit cards on file. Your customers will often tell you more services you can add, that they will be happy to pay extra for.
Better for you to actually VALUE your product from the get go, get customers who also value it, and work together to make it better.
Think I'm crazy? Ask Groupon businesses how much repeat business they get from their cheap promos. It's the same problem.
You can provide limited support for basic accounts and charge much more for full support like $5-$9/month. The idea is to give your customers the only-pay-for-what-you-need model which is very realistic on the web.
If your cost increases significantly with each new customer you acquire then find what will increase your costs and charge extra for it, maybe bandwidth, computation, disk space etc.
Or can we say that once you have acquired x number of customers at %5-7/month, it may then be easy/feasible to switch over to $1/month model since you already have a "traction" at this point