[ArekDymalski]

Just few quick, (hopefully) thought-provoking questions: 1. Is this a business or a hobby project? 2. Do you really need Beta 2? 3. Do people like it enough to pay (assuming it's a business)?

Without any info about your product/users/market it's quite hard to give you anything more precise.

[majesticbeans]

I figured. You'd be surprised how your reply still provided me great stuff to work with. It's what I was aiming for, actually.

It's a business. Not sure if I need a beta 2, how can I tell? My market is small, but I'm doing this to see if I can start and run a successful business. As for willingness to pay, I've asked most them personally or by survey and most of them have said YES.

[ArekDymalski]

Glad I could help - I strongly believe that often the best answers are already between asker's ears :) Regarding the beta I guess that if your product is already working properly you can drop this label. IMHO "beta" used to be a nice way to inform the users that they can expect some bugs in a work in progress. But with a popularization of the Lean approach and with availability of A/B testing tools, there's no need to call self a "beta". Someone once said "Don't build a startup, build a business". I think "beta" badge is one of the things that distinguishes one from another.

[majesticbeans]

Totally taking your advice on that. I just assumed that to be the status quo, but I can't believe I never realized that it really cuts into the sense of continuity I want my business to have.