Loading...
Answers
MenuWhat are some methods to limit beta roll-out where the app will rely on viral sharing via social media for it's ultimate success?
The app will be applicable globally, but initially is being built for US and Canada. We're non-developers and are outsourcing the initial development, where our objective will be to bring the IT staff in house later. We want to provide beta, but in a closed fashion. However, much of the power of the app will be from SM sharing and viral activity created from it. To not enable SM sharing, even from closed beta, simply isn't feasible.
Answers
If your product relies heavily on a successful growth-loop through social sharing, you simply *must* run the social component "live in the stream." The value of the data you will collect far outweighs any concerns over someone guessing what you're doing by the social shares.
See my answer about what makes a great technology product here on Clarity about the importance of a great growth loop.
The ultimate thing you'll be able to learn via the public test is the effective of your messaging and a general click through rate. You can bring them to a page that playfully says that the link was generated by an app in private-beta and if they want to learn more, they can sign-up. That in fact, would be another great data point.
The point is that just by making your social stream messaging and link public doesn't make your product in any way public.
And by the way, the more effective your social share is at generating click-throughs or full-blown conversions (a click on the landing page of any kind), then the higher and stronger signal you have to the fact that you're on to something.
In a call, I'd be happy to share my experiences in building MVP's with contract labor and testing growth loops via social streams.
Do you know how Mailbox App did it?
They had a closed beta but they hard a website, a landing page and an iOS Application that enabled people to register in queue waiting for a slot be to accepted into the closed beta.
People had a newsletter delivered to them and were able to share and invite others (this social actions pulled them ahead on the queue). This way people could interact, share and receive newsletters on Mailbox App even though they were not included on the closed beta. It was a successful strategy and other companies did it also with success.
Read this article to know more about it and how you may be able to do it also:
http://techcrunch.com/2013/04/01/queueing-theory-lets-any-app-offer-a-mailbox-like-reservation-system-even-if-its-just-for-building-buzz/
Related Questions
-
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
-
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
-
I'm having problems with ideation for a startup, I'm a web developer, what needs of yours aren't being met? Or how can I find a big problem to solve?
It's really ill-advised to solicit your vision from anyone. In my 20 years of building, investing and supporting tech companies, I don't know of a single success story that has it's origins in someone with your approach. Running a tech startup is incredibly hard. It demands sacrifices few are truly able to make and come with it tremendous risks that most people are unwilling to take. It sounds to me as if you want the startup life because you have an impression of what it's about but haven't yet experienced it first-hand. I'd encourage you to first join an early-stage startup. Developers are incredibly in-demand. Find an entrepreneur who has some experience, funding and a compelling vision that you believe in and get to know what the journey is really like.TW
-
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
-
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
the startups.com platform
Copyright © 2025 Startups.com. All rights reserved.