How we talk about product status

A concept, a build in progress and a live product are different things. They ask for different trust from the person reading about them. BAYNUX uses a small set of public statuses so that difference stays visible.

The words we use

• Concept — a direction we are willing to describe. There is no working system to adopt.
• In Development — the product is being built. It is still not an operational service.
• Beta — a limited release for feedback. Access is explicit, and the product is still unfinished.
• Live — a service someone can use under the terms published for it.
• Coming Soon — a release is planned. The page should say what is actually scheduled, and it should change if the plan changes.

Why a status belongs on the page

Status is part of the product's interface with the world. If it lives only in a sales conversation, the website is doing a different job from the company. We would rather a visitor understand the limit in one reading than discover it after they have imagined a system that does not exist.

The same rule applies in reverse. When a product does go live, the page should say so plainly, with the access path and the terms. A live product does not need theatrical language. It needs instructions.

What this asks of client work

Client systems get the same honesty about scope. A prototype is a prototype. A production handover is a production handover. We write down which one we are doing before the build starts, and we keep the public description aligned with that agreement.

If you are evaluating BAYNUX, read each published product page as it stands. The status badge is there to be believed.