Learn from peers
Discuss and share learning resources with the top professionals across the world
Open business or job opportunities
Earn reputation points to get consulting projects, attract talent or land jobs.
Accelerate your growth
Grow your network and get exclusive deals from our learning partners.
signup now
I can see at least 3 scenarios.
1. Load : when the system you have created is getting the traction but is not capable of handling a huge jump in demand. Any system that is now cloud deplyoyable or scalable elastically is in this category. This is a solvable issue. improvement in the system architecture would be able to solve this. So for some time you drive on invit-only while fixing the things and role it out to everyone.
2. Core recource : When the end user product/service/experience you are offering is inherently difficult to scale up. e.g. There was a Shark Tank pitch for "i want to draw a cat for you" (http://iwanttodrawacatforyou.com/). That thing is inherenty not scalable. This is very very tricky to solve.
3. Exclusivity : A product that is not for all and is a luxury item/service can go this way to maintain exclusivity. e.g. membership to some high-end club, Golf course etc.
That's true invite only method is not for all.
Most of the time it works for the gaming applications like Never Do well for Android and some other applications. They are based on the invite only option but thats make it more interesting for people to try.