Vendzi

Run the business

Tell Vendzi what you do. Get the pages, the calendar and the till.

A short conversation produces the website pages, the services behind your booking calendar and the products behind your point of sale. Every proposal is a structured change you can read, edit or reject — and publishing goes through the same review as any manual edit.

Live demo

Watch a brief become a shop

Typed into the prompt, clicked, revealed as a change set — the same four beats the builder runs in the product, driven by DOM state instead of a recording.

Interactive demo of the Vendzi admin. A short brief is typed into the AI builder, the build button is pressed, and a proposed change set of 5 operations — pages, services and products — appears beside a live preview of the generated storefront.

Capabilities

What it does

Everything below is in the product today — not a roadmap item.

One brief, three surfaces

Describe what you sell, who you serve and where you work. The builder drafts the pages, creates the services with their durations and prices, assigns staff, and adds the products — in one pass, not one wizard per feature.

It asks instead of inventing

Prices, opening hours and addresses it does not have are requested from you as questions. A missing fact is a question, never a plausible-looking default baked into your live site.

Structured changes, not a black box

Every proposal arrives as a typed operation against your own records — create this product, update this service, add this page. You see the change before it happens, and you can refuse it.

A readiness gate before publishing

The run reports what is still missing: facts you have not confirmed, document kinds the flow expects, capabilities your plan does not include. Nothing is published while a requirement is open.

Credentials stay server-side

The model runs through a server-side credential resolved for your shop. It never receives a key and cannot pass one into a tool call, and every tool argument is validated against the same schema the runtime enforces.

Workflow

How it runs in real life

The same order it happens in the shop — from setting it up to closing the day.

  1. Write the brief

    A few sentences: what you sell, who your customers are, the city you work in. Short is fine — the builder asks for the rest.

  2. Answer the gaps

    It comes back with the facts it needs and cannot know: opening hours, the price of a specific service, your address. Answer in the same conversation.

  3. Review the proposal

    Pages, services, staff assignments and products appear as a change set against your records. Read it, edit it, reject what you do not want.

  4. Publish

    Publishing uses the same path as the manual editor, so a page the builder created behaves exactly like one you wrote by hand — editable, versioned and revertible.

The specifics

Facts, not vanity metrics

Structure facts from the product itself. No customer counts, no invented percentages.

One conversation

for pages, services and products together

Every change

a typed operation you review before it applies

No invented facts

missing prices and hours come back as questions

Questions

Questions about ai builder

If yours is not here, ask when you sign up — you will get a person.

No. It proposes changes and reports what is still missing. Publishing is a separate step you take, through the same publish path the manual editor uses.

Run your whole front of house on one system.

Create your shop, add your services and hours, and start taking bookings today. Connect the payment provider you already use.