One problem with what you're saying is how you define "beta". Everyone defines it differently (What Google considers beta is different than what I would consid

One problem with what you're saying is how you define "beta". Everyone defines it differently (What Google considers beta is different than what I would consider beta which is different than what you consider beta. A larger problem (you're not alone in making this mistake) is trying to lump software development into set, solid stages. Development is more fluid then "OK. we're beta. next up is final release and we're done forever." It's doubtful that you ever stop adding features or making something better. And if that is the case, I'm not entirely sure I'd want to use your product knowing it'll never be improved beyond 1.0. As for why you might want to limit invites? Maybe you're trying to figure out how much it can scale with what you currently have before you work on it some more? Or maybe you want to try the limited scarcity thing out. Who knows the motivations.