Who should I consult with to scrutinize my unique web and mobile business (model) method?

I would suggest launching in a foreign app store only (ex: Canada). That will allow you to get more organic users to continue iterating without a big push. I got this idea from Matt Brezina (Founder of Sincerely, previously Xobni) https://clarity.fm/brezina - he's the man when it comes to testing & iterating mobile apps.

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/

Apps are difficult to fund on IndieGoGo as few are successful, and we rarely take them on as clients. Websites like http://appsfunder.com/ are made for that very reason, but again, difficult to build enough of a following willing to pay top dollar for an app that could very well be free, already existing in the marketplace. A site that is gaining more traction you may want to look into would be http://appsplit.com/. Again, Appsplit Is Crowdfunding For Apps specifically.

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.

You are right that the range is wide. You need to figure what are good values to have for your category. Also, you can focus on the trend (is your DAU/MAU increasing vs decreasing after you make changes) even if benchmarking is tough. Unless your app is adding a huge number of users every day (which can skew DAU/MAU), you can trust the ratio as a good indication of how engaged your users are. For games, DAU/MAU of ~20-30% is considered to be pretty good. For social apps, like a messenger app, a successful one would have a DAU/MAU closer to 50%. In general most apps struggle to get to DAU/MAU of 20% or more. Make sure you have the right definition of who is an active user for your app, and get a good sense of what % of users are actually using your app every day. Happy to discuss what is a good benchmark for your specific app depending on what it does.