Loading...
Answers
MenuWhat is the ideal number and mix of betatesters for our mhealth self management platform?
We have a v1 being coded by an active advisor and are recruiting on testflight for beta testers. Our app is for reversing lifestyle disease as type two diabetes and hypertension, so I have 20 patients enrolled to test. Also we want to consider B2B model for later sale for health organizations and payers to utilize the app in their populations and have access to the data points of health improvement. I know a number of Health care influencers and CMO's of large organizations, but do we want to engage them this early? Could their seeing a buggy app turn them off from a potentially major B2B Sale? Or should they be encouraged to give us feedback on features early on to lead to B2B sale later on?
Answers
Here's my rule for numbers.
100 target customers that I've done customer discovery interviews with.
10 customers (who've paid / given me money)
25 who are active beta testers.
I usually use that order of things as well. I like to get early adopters to give me money to validate their feedback, then 25 to give product feedback to test usage & retention, but in parallel I talk to as many potential customers as possible to learn.
Getting enterprise customers into early TestFlight builds is generally speaking not recommended because first impressions often become lasting ones. The reality of it is that even with good product/market fit, most people are too busy to play with build after build in the early days.
Assuming you have validated the core product thesis before building the app, I would try and recruit whomever you know to be great product people into TestFlight first. Building a great mobile product is exceptionally hard and I've benefited so significantly by having so many of my TestFlight users be great mobile developers, and product owners. There is a lot of very generalizable experience around what makes a great mobile app, and having people who can quickly spot bad UX will reduce your iteration time significantly.
For mobile, it's important that the polish is there before onboarding users whose favorable impression might lead to enterprise sales. It's better to test screenshots and static designs on these important users than a really buggy app.
Lastly, I strongly encourage you to switch from TestFlight to Hockey App. We made the transition after too many headaches with TestFlight.
I spend almost all of my time obsessing about attaining mobile nirvana and also built a website in the late 90s that provided personalized nutrition plans via a website to corporate employees so happy to talk to you in a call about what you're doing.
Excellent question! I've seen these issues firsthand (both myself using lean startup in my health 2.0 co., and with my clients) and I honestly don't feel there's a 'one size fits all' answer. Based on the info you've posted, I think you need to really understand what your main goal is. If it's for reversing disease, leave the B2B piece until you've worked the bugs out with your patient beta testers and make your product work best for them. Make it a great product. Get a community of users. Then bring to influencers and your potential B2B customers when it's working and has a user base that allows you to better demonstrate the value to that set of customers in the data, etc. Happy to chat further if you have other questions!
Related Questions
-
How can I smoothly transition from full time worker to self-employment?
The ways I've done this in the past are 1) Find some customers that are willing to hire you (or your product) but know that you'll only be free nights & weekends to support/work with them. 2) Find a "partner" (co-founder or other) that's got a flexible schedule that can help build the business while you're at work. 3) Block out nights, mornings and weekends to build the business till you have enough orders to cover 50% of your salary. This might mean 7pm-11pm most nights, and 4 hours each day Sat & Sun. Make progress (sales $$$) and momentum. All that being said, it's risk reward. Sounds like you want to avoid taken the risk, and I get that .. but the upside is always smaller. Unless you put yourself in a position to have to succeed (ex: quitting your job) then you may never make the scary decisions that are required to build a company (like cold calling, going in debt, making a presentation, etc). I'm on company #5 with many other side projects started nights & weekends .. so I get it - but don't be afraid to bet on yourself and go all in.DM
-
Any advice on starting up small businesses in two countries at the same time?
Please realize that my suggestion would be slightly different if I knew which two countries. However, without knowing that here's what I'd suggestion: 1. Since you're just getting started figure out which country provides the best legal benefits for starting a company. This should include tax benefits, legal protection, and ease when it comes to filing paperwork (incorporating, managing payroll, taxes, etc.). This will undoubtedly save you time and money moving forward, and staying lean. 2. Once you've established your home base country, you'll still need to hire people in the other country as you scale. You may want to think about using a service like oDesk or Elance, not necessarily to recruit people but to manage ALL the paperwork associated with hiring international people. They will of course be given contract status. If you are going to be providing employees equity then I'd suggest consulting a lawyer for how people in the non-home base country will be treated. 3. Reporting revenue. You need to be very careful about whether you are providing goods and services. If it's goods keep in mind that you might be subject to tariffs. If you're providing services then I think you might be in the clear, but please double check. Finally, some countries might have an issue with where the revenue was actually made i.e. are you sitting in your office in your home based country while servicing clients in the non-home base country, or are you actually in the non-home base country. 4. No matter what you'll need to setup a remote working environment for yourself. Invest in the best technology you can, and find clients who are willing to utilize your services on a remote basis. Here are a few additional posts on running a remote team that I've written: http://femgineer.com/2013/09/running-remote-and-making-progress/ http://femgineer.com/2013/03/how-to-transition-to-a-remote-team/PV
-
What are ways to find and engage B2B beta users for a brand new application?
Find apps that are B2B and go to the review sections. Specifically going to Google's play or Chrome store and look at reviews and follow them to Google+ to engage. I took that same angle for B2C app I was building last year. Check it out. http://blendah.com/post/37331434653/lean-startup-hackTM
-
Is there any typical questions for customers' pain points discovery or it's impossible to standardise?
I have built several multi-million dollar businesses using (2) very simple questions: "What makes you say that...." and "Tell me more...." No matter what someone says to you, you just keep asking one (or both) of the questions. If you do it 4 or 5 times in a row you'll learn everything you ever wanted to know.DW
-
Is it advisable to outsource to an agency to create our MVP? Are my security concerns unfounded?
It's not unusual at all. If you do outsource, try and make sure you have a project lead that you can trust. Once revenues get up to a certain point they might want to see the project through and come on board full time OR they will have enough pride in their work to make sure a proper transition takes place. As far as security, make sure you have an airtight non-disclosure/non-compete agreement with a penalty clause that includes financial remuneration.MM
the startups.com platform
Copyright © 2025 Startups.com. All rights reserved.