The input is intentionally small
The public creation flow asks for the business name, what the business does and the owner email, together with the already selected product and level. The browser also supplies the timezone. The goal is to collect what the provisioning system actually needs rather than turn setup into a questionnaire.
Provisioning creates a real product instance
A successful request goes through controlled states including validation, account resolution, tenant creation, product-instance creation, capacity application, domain reservation, owner creation, blueprint attachment, data seeding, content/media preparation, TLS readiness, product health checks and final READY state. This is why BADWEB can show progress rather than pretending a static mock-up is the finished product.
What the Business Website blueprint contains
The Business Website blueprint includes identity, role-based access, files, notifications, audit, analytics, legal and billing modules plus pages, services, gallery, locations, SEO and revisions. The generated product exposes public pages such as home, about, services, gallery and contact, while administration surfaces let the customer manage business, legal and SEO settings.
The customer gets administration, not just HTML
The value is not only that a public page exists. Once the product reaches READY, the customer receives the product URL and administration URL and gets a one-time activation link by email. The customer chooses a password and then manages the product through authenticated controls.
What automation does not mean
Automation does not mean every external dependency is instantaneous. DNS/TLS, email and cloud services can affect timing. BADWEB therefore starts the free trial at READY, after its readiness checks, rather than consuming trial time while the product is still being assembled.