Should we tag our new website as 'beta'?

What does tagging your new website as 'beta' say to your potential customers. We intend a 'soft' launch to our website and are not planning any significant marketing at this period. We intend to use this time to refine our business administration processes and sort out any teething troubles in terms of the correct functioning and operation of the website.

We intend to 'relaunch' 4-6 months after our 'soft' launch but beyond a marketing drive, a moderate extension our services (and perhaps a moderate update to the look and feel), there is not any major revisions to our website. Should we tag our website as 'beta' during this first period or not, and does it matter?

BETA is not a word to decorate your brand name. It is the word to represent your product is new, may have errors, we are working for its development There are few major risks if you didn't release your product as beta at first.

1) What happens if your product had bugs or crashed for some reason?
2) No first release is successful. It needs validation, verification and feedback.
3) Can you answer to your users if your website's server got down?

That is the reason why the term BETA helps you from many risks like above. No body has a right to question you/your product when it is in BETA. BETA just says your product is in testing purpose and requires bug fixing.

BETA can also be used for incomplete projects. You can launch your product now with BETA and can upgrade it daily until you reach your end. Once you reached your position and feel that your product is out of risks you can remove the term BETA.

All the best.

Tagging as beta is fine but don't do what Google did with gmail and tag it as beta for seven years - it just looks ridiculous.

It doesn't matter. Whatever you choose to name it, it will only be used by early adopters, because by definition those are the ones who use new stuff. Since early adopters have no problem with the beta sign at all, you can freely use it, or not, as you wish.

However, I would highly recommend reconsidering the plans for "no major revision of our website" after the first release. Actually, the only point of an early release is to get feedback and make even major changes if necessary. As far as I understand, you got no user feedback yet, and this will be your first release. How do you know your product is any good and doesn't need major changes?

Are you sure that the website you're launching is technically flawless? If you aren't, you should definitely tag is as beta. This will protect your image if some bugs are found by your early users.

I would not tag it as Beta. I think the Beta tag is an excuse for not getting rid of bugs or making it usable. There is a big push for launching a minimally viable product, which I agree with, but viable is not buggy or unusable.

I would get rid of bugs and make sure the basic functionality is usable, and then launch without a disclaimer. It's fine that there is still much more to come, but what you have launched should still add value, and if not, it's too soon to launch.

Don't hide behind a beta tag, get it to be a legitimate minimally viable product and then launch.

You see I tagged mine as beta. The reason is, since it is work in progress I don't want to give potential user impression that this is a finished products. Especially when I expect to find some flaws in design as the customer base grows. It really up to you how you look at it.

Also depends on whats your business model, but I think its easier to explain why you changed your pricing or products offer should you need to do so for various reasons when using beta tag.