Loading...
Answers
MenuAre there ways to have a software prototype tested by a large sample of potential users, in order to generate feedback, suggestions, problems etc?
I have a software product in alpha/beta stage. I want to test the current minimum viable product. I want the prototype to be tested by a large sample size, so I can gain feedback, suggestions, find problems, and build on my current prototype. My goal is to achieve maximum product - market fit, and pivot if necessary. What are the challenges to doing this and are there any services currently available ?
Answers
You can get real people to interact on a site like usertesting.com — it's a paid service to get you real feedback from real humans.
If you want access to your demographic, you'll need to find out where they hang out and come up with an offer to encourage them to try your service (a closed beta, free access in exchange for submitting evaluations and feedback, etc.). Ads and/or sponsored posts could be useful here.
Or you can set up your own user testing arrangement and offer to pay people a small amount in exchange for using the app. This should probably be your last-ditch effort, though.
Good luck!
Yes: Applause - formerly Utest. www.applause.com
I strongly recommend http://www.utest.com/
Related Questions
-
How can I become an idea person, as a professional title?
One word: Royalties This means you generate the idea and develop it enough to look interesting to a larger company who would be willing to pay you a royalty for your idea. This happens all the time. Rock stars, authors and scientists routinely license their creative ideas to other companies who pay them a royalty. Anyone can do it. Your business, therefore, would be a think tank. You (and your team, if you have one) would consider the world's problems, see what kinds of companies are trying to solve those problems, and then develop compelling solutions that they can license from you. You have to be able to sell your idea and develop a nice presentation, a little market research and an understanding of basic trademark and patent law. The nice thing about doing this is that if you develop enough cool ideas you will have royalties coming in from a lot of different sources, this creates a stable, passive revenue stream that requires little or no work to maintain. Start in your spare time and plan on the process taking 3-5 years. Set a goal to have a few products in the market that provide enough revenue (royalties) to cover your basic living expenses. Then you can quit your day job and dedicate more time and increase the momentum. A good idea business should have dozens, if not hundreds of license contracts generating royalties. It's possible to pull this off. And it is a fun job (I'm speaking from experience).MM
-
What does it mean to 'grandfather you in' in the tech world?
It stands for allowing someone to continue doing or use something that is normally no longer permitted (due to changing regulations, internal rules etc.)OO
-
Whats are some ways to beta test an iOS app?
Apple will allow a developer to register 100 UDID devices per 12 month cycle to test via TestFlight or HockeyApp. Having started with TestFlight, I would really encourage you NOT to use it, and go directly to HockeyApp. HockeyApp is a much better product. There is also enterprise distribution which allows you far more UDID's but whether you qualify for enterprise distribution is difficult to say. As part of your testing, I'd encourage to explicitly ask your testers to only register one device. One of the things we experienced was some testers registering 3 devices but only used one, essentially wasting those UDID's where we could have given to other testers. Who you invite to be a tester should be selective as well. I think you should have no more than 10 non-user users. These people should be people who have either built successful mobile apps or who are just such huge consumers of similar mobile apps to what you're building, that they can give you great product feedback even though they aren't your user. Specifically, they can help point out non obvious UI problems and better ways to implement particular features. The rest of your users should be highly qualified as actually wanting what you're building. If they can't articulate why they should be the first to use what you're building, they are likely the wrong tester. The more you can do to make them "beg" to be a tester, the higher the sign that the feedback you're getting from them can be considered "high-signal." In a limited beta test, you're really looking to understand the biggest UX pain-points. For example, are people not registering and providing you the additional permissions you are requiring? Are they not completing an action that could trigger virality? How far are they getting in their first user session? How much time are they spending per user session? Obviously, you'll be doing your fair share of bug squashing, but the core of it is around improving the core flows to minimize friction as much as possible. Lastly, keep in mind that even with highly motivated users, their attention spans and patience for early builds is limited, so make sure that each of your builds really make significant improvements. Happy to talk through any of this and more about mobile app testing.TW
-
How much equity should I ask as a CMO in a startup?
Greater risk = greater equity. How likely is this to fail or just break even? If you aren't receiving salary yet are among 4-6 non-founders with equivalent sweat investment, all of whom are lower on the totem pole than the two founders, figure out: 1) Taking into account all likely outcomes, what is the most likely outcome in terms of exit? (ex: $10MM.) Keep in mind that 90%+ of all tech startups fail (Allmand Law study), and of those that succeed 88% of M&A deals are under $100MM. Startups that exit at $1B+ are so rare they are called "unicorns"... so don't count on that, no matter how exciting it feels right now. 2) Figure out what 1% equity would give you in terms of payout for the most likely exit. For example, a $10MM exit would give you $100k for every 1% you own. 3) Decide what the chance is that the startup will fail / go bankrupt / get stuck at a $1MM business with no exit in sight. (According to Allman Law's study, 10% stay in business - and far fewer than that actually exit). 4) Multiply the % chance of success by the likely outcome if successful. Now each 1% of equity is worth $10k. You could get lucky and have it be worth millions, or it could be worth nothing. (With the hypothetical numbers I'm giving here, including the odds, you are working for $10k per 1% equity received if the most likely exit is $10MM and the % chance of failure is 90%.) 5) Come up with a vesting path. Commit to one year, get X equity at the end. If you were salaried, the path would be more like 4 years, but since it's free you deserve instant equity as long as you follow through for a reasonable period of time. 6) Assuming you get agreement in writing from the founders, what amount of $ would you take in exchange for 12 months of free work? Now multiply that by 2 to factor in the fact that the payout would be far down the road, and that there is risk. 7) What percentage share of equity would you need in order to equal that payout on exit? 8) Multiply that number by 2-3x to account for likely dilution over time. 9) If the founders aren't willing to give you that much equity in writing, then it's time to move on! If they are, then decide whether you're willing to take the risk in exchange for potentially big rewards (and of course, potentially empty pockets). It's a fascinating topic with a lot of speculation involved, so if you want to discuss in depth, set up a call with me on Clarity. Hope that helps!RD
-
For every success story in Silicon Valley, how many are there that fail?
It all depends on what one decides to be a definition of a "success story." For some entrepreneurs, it might be getting acqui-hired, for some -- a $10M exit, for some -- a $200M exit, and for others -- an IPO. Based on the numbers I have anecdotally heard in conversations over the last decade or so, VCs fund about 1 in 350 ventures they see, and of all of these funded ventures, only about 1 in 10 become really successful (i.e. have a big exit or a successful IPO.) So you are looking at a 1 in 3500 chance of eventual venture success among all of the companies that try to get VC funding. (To put this number in perspective, US VCs invest in about 3000-3500 companies every year.) In addition, there might be a few others (say, maybe another 1-2 in every 10 companies that get VC investments) that get "decent" exits along the way, and hence could be categorized as somewhat successful depending on, again, how one chooses to define what qualifies as a "success story." Finally, there might also be companies that may never need or get around to seeking VC funding. One can, of course, find holes in the simplifying assumptions I have made here, but it doesn't really matter if that number instead is 1 in 1000 or 1 in 10000. The basic point being made here is just that the odds are heavily stacked against new ventures being successful. But that's also one of the distinguishing characteristics of entrepreneurs -- to go ahead and try to bring their idea to life despite the heavy odds. Sources of some of the numbers: http://www.nvca.org/ http://en.wikipedia.org/wiki/Ven... https://www.pwcmoneytree.com/MTP... http://paulgraham.com/future.html Here are others' calculations of the odds that lead to a similar conclusion: 1.Dear Entrepreneurs: Here's How Bad Your Odds Of Success Are http://www.businessinsider.com/startup-odds-of-success-2013-5 2.Why 99.997% Of Entrepreneurs May Want To Postpone Or Avoid VC -- Even If You Can Get It http://www.forbes.com/sites/dileeprao/2013/07/29/why-99-997-of-entrepreneurs-may-want-to-postpone-or-avoid-vc-even-if-you-can-get-it/MB
the startups.com platform
Copyright © 2025 Startups.com. All rights reserved.