For alpha/beta testing, should I charge users or pay users?


8

I'm creating a mobile app for small business wholesalers and the alpha will be finished soon.

I have done some face-to-face market research by visiting trade shows they exhibit in and showing them a prototype and asking questions. I get positive reactions and when I ask the question "Would you like to alpha test?" Most of them say "Yes". But I'm finding that when I follow up with these users, I can't get a hold of them. So I'm assuming that maybe they really aren't interested in being an alpha user any more.

Someone suggested that I should be asking for some token amount of money like $20 to show that they are committed. Yet, someone else suggested that I provide incentive by compensate them some how - maybe money or random prize or discount on the software. What is the best approach? I only need about 5-6 businesses for alpha testing.

Software B2B Beta Small Business Mobile Apps

asked Dec 30 '12 at 01:49
Blank
Sguptaet
242 points
  • Just want to share a comment a mentor of mine made: My take on this is that both parties (you and your customers) are already getting value for participating in the alpha/beta. You get valuable feedback and your customers get early access to the software and a chance to contribute to the product roadmap. As such there is no need for any monetary exchange. – Sguptaet 8 years ago

4 Answers


4

(disclaimer: not knowing what your product does nor what your customer group is, this will be a more generic answer)

Alpha-testing

This is very often an incomplete stage of the cycle and IMO will require experienced testers that is familiar with the development process as there could be missing some functionality. Ideally alpha-testing should be done in-house or by a small group of people not necessarily associated with the companies you're targeting - as it is much a technically and operational oriented testing.

In other words: bringing an alpha version to potential future customers can fail as they, in general, are not fully familiar with the development process and it can leave them with a negative impression of the app. Alphas are too incomplete to bring outside IMO.

Beta-testing

Now the application is complete in the sense of functionality and bugs are to be found and removed. IMO this is the stage where you should involve a few select potential customers. It's easier to get apps at this stage tested as everything is in place and bugs are the focus, not so much functionality. But not without an internal initial beta-test to catch the most obvious bugs.

To pay or not to pay

You are asking people to do work for you. Charging them would be wrong in my opinion. For businesses to spend resources/time on doing testing for you would make them want something in return. Maybe you can offer them 50% for the first year, free first two months, free setup (something more in terms of what you deliver) and so forth.

As they already have spent time on your product and are getting more familiar with it, they are more likely to continue with it if they think of it as a good product. See the compensation as a sales investment. As you work closer with customers that do testing you can also get valuable references/case-studies to use with future customers.

Make it a win-win.

Testers

In my experience people tend to say yes to do testing as it initially makes them feel part of an exclusive group, ie. have access to something that not everyone has access to. The reality bites when they discover they need to sit down, spend time and work with an incomplete app that may give unpredictable result, or even loss of work (if that applies).

Finding the right person to do testing is not always easy, but if the company has an "evangelist" (s)he can often be a good starting point to either test or help find the right persons for you to do the testing.

answered Dec 30 '12 at 19:20
Blank
Ken Abdias Software
246 points
  • Thanks for clarifying the alpha and beta terms. I guess the problem with giving incentives to test, is what you mention - you'll get users who really don't want to. – Sguptaet 8 years ago
  • It's quite normal, don't give up. I may be a bit black-and-white in my answer (written 3am) in the payment part, there are always exceptions depending on product and market of course. My experience is mostly from Europe and I realize there are big differences in some areas other places in the world (I'm now in America). In any case good luck with your product! (and thanks Zuly for the grammer-corrections :) ). – Ken Abdias Software 8 years ago

3

You will always get a lot more people saying they will test than actually testing. With this in mind, make sure you get a lot more committed to testing than you need.

As for paying, I wouldn't have them pay and I wouldn't pay them. I don't think payment is the answer to this problem.

You need to inspire them with the vision of your product and you need to make it very easy for them to be a tester (go set it up for them if you need to).

Getting testers isn't easy, but don't get discouraged, what you are finding is perfectly normal. Just hustle and make it work.

answered Dec 30 '12 at 17:59
Blank
Joel Friedlaender
5,007 points
  • I think this is the correct answer for me. It is they way I've been doing it, without compensation either way. Maybe I need to just stick to it. Providing incentive will get you testers you don't want, and charging users while weeding "bad" testers out, might discourage testing. I should work on articulating my vision and just selling better. Thanks! – Sguptaet 8 years ago
  • And perhaps creating some document/process that adds formality to the relationship. Maybe my approach is too wishy-washy right now. – Sguptaet 8 years ago
  • It depends on your audience and the product. Documentation and process may help or hinder. I would really just try to get them excited by it, and let them know what a great deal they get to use the software for free during the beta period. If the product is filling a need, you should find some people. You also really don't need many. I wanted a lot of beta testers for my product and ended up with 2. In hindsight it was plenty, as long as they actually use it properly. – Joel Friedlaender 8 years ago
  • I just want to make a comment on this regarding Joel's first point in the answer. Its true. So many users said they wanted to test, but when it came down to actually signing up, only a few did. – Sguptaet 7 years ago
  • @SundeepGupta do persist though. I had one person that said they would beta test but didn't. Every few weeks I would email them and check in. I really ended up harassing them for quite a while (in a nice way) and eventually they cracked and have now been one of my longest paying customers. So if they haven't said no, they just haven't done anything... do stay in touch with them. – Joel Friedlaender 7 years ago

1

I think it is better to charge. You could say, I want to alpha test my application/service so that it can better suit your and our customers need(s). You can alpha test for $(x/2) - ie. Half the price. As a reward, you can make the service cheaper for them for a small time or if you charge one time, charge them less, give them 25% discount or something.

This will get you people who actually want to help you and get rid of those people who aren't too serious. This will give you a realization of how many people would actually pay for what you have to offer (when this happens, most people realize they were not realistic about their sales at all before!). Some people alter their actual opinion to appeal to you (i.e. they don't want to seem rude, cheap, etc.).

Also, I suggest you read "Purple Cow". According to that book, it's better to have sneezers test your application. Sneezers actually like testing newer alternatives and spread the word for free!

answered Dec 30 '12 at 13:56
Blank
Bhargav Patel
784 points
  • This completely make sense to me. But I'm thinking it applies more to [Blue Ocean](http://en.wikipedia.org/wiki/Blue_Ocean_Strategy) products. Because the user can't get it elsewhere, they will want it so bad they are willing to pay to help you. What I'm building is not Blue Ocean, it's improving on and being more niche than competition. I wonder if users will still want to pay to test. – Sguptaet 8 years ago
  • And thanks for the reference to the book and concept of sneezers. – Sguptaet 8 years ago

0

Well you need two things -

  1. You really have to convince them that your product is worth their time. If it is something new, then they need to be convinced that there is a problem they could solve with your app. If it something for which there are other options available, then they must be convinced why they should choose your product over others, specially over the one they are using right now, if they are. If it were the latter case, I'd go over forums related to competing products to see if there are any local businesses which are not happy with the product they are using and target those.
  2. You need to give them incentives to test out your product, which is unproven. They are taking a risk and there should be something in it for them too. It could be discounted subscriptions, free or discounted future add-ons, free swag or if you can have spare cash - free accounts on services that their business could use like Dropbox. With just ~5 businesses shouldn't cost more than a few hundred dollars. Don't offer money, that would raise all kinda flags, at least it would for me.
answered Dec 30 '12 at 13:28
Blank
Elssar
367 points

Your Answer

  • Bold
  • Italic
  • • Bullets
  • 1. Numbers
  • Quote
Not the answer you're looking for? Ask your own question or browse other questions in these topics:

Software B2B Beta Small Business Mobile Apps