How to deliver an AI-built site to a client

What are you actually delivering?

Agree on the deliverable before sending the first preview. Write down the pages, the main visitor action, the supplied content and who approves it. A freelancer building a brochure site and a studio delivering an application with customer accounts are taking on different work, even if both begin with an assistant.

SayLive fits static sites: HTML, CSS, browser JavaScript and images. It does not run accounts, databases or server code. Check the brief against that boundary early. If the client expects a feature the chosen host cannot run, settle the hosting decision before asking them to approve the design.

Name who gathers feedback and who approves publication. Agree which corrections are included and what starts a new round of work. The briefing guide turns that agreement into instructions for the assistant.

How do you make the review useful?

Send the client a review link and tell them what to inspect. SayLive includes a review link with screenshots, so feedback can refer to the visible problem. Encourage comments that name the page, identify what is wrong and give the desired replacement. A screenshot of the heading plus its corrected wording is easier to act on than a request to make everything feel different.

Ask the client to check content as well as appearance: business name, contact details, services, images and the main contact action. Record the version under review and keep one list of requested changes. If two people are looking at different versions, resolve that before the assistant starts another revision.

The staging option described on the Studio page lets you publish for review without making that version live, then promote it after approval. Decide whether to use staging before the review begins. The review before publishing gives you a fuller checklist for your own pass before the client sees it.

How do versions turn feedback into approval?

Treat each revision as a response to an agreed list. Ask the assistant to make those changes, inspect them, then identify the resulting version when you return to the client. SayLive has versions and rollback, so an earlier publication remains a reference you can return to. That is useful when a later change needs undoing.

1. 1Collect feedback for the version under review and resolve contradictory requests with the client.
2. 2Ask the assistant for the agreed corrections, preserving the parts already approved.
3. 3Check the revised pages on a phone and a computer, including navigation and the contact action.
4. 4Send the revised review link with a short list of changes and identify the version being approved.
5. 5Record the client’s approval before publishing or promoting that version for visitors.

Record the approved version, the date and any work left for later. That gives both sides the same starting point when the client requests an update.

When should you connect the client’s domain?

Connect it when the approved site and launch timing are settled. With SayLive, connecting your own domain is included once the site is paid. Arrange for the client to hold their domain at the registrar, the company where the name is registered, and record who will manage its renewal.

The hosting payment and the domain are separate responsibilities. The domain guide explains that distinction and the connection process. After the address is connected, open it yourself and repeat the important checks rather than relying only on what worked at the review address.

Put the tested final address in the delivery note alongside the approved version. Give the client one address to copy for printed material or announcements.

What belongs in the handover?

SayLive can transfer the finished site to the client’s own account, with their billing, domain and space; the transfer is included. Agree whether you will continue maintaining it. A client can invite you into their account, where your assistant can switch workspaces and work under your name without using the client’s password.

Any SayLive version can be downloaded as a ZIP. Include the approved files in the handover and use the documentation for publication, versions and domain workflows. If you built from a project that needs a build step, keep that source and its instructions too, so future edits have a clear starting point.

What does Studio offer today, and what is coming?

The Studio page describes transfer, cloning and working in a client’s workspace as available today. Cloning copies a site into a fresh draft with its files, media and brand memory, and does not put it online until you say so. Before using a previous project as a starting point, replace the client-specific material and check what you have permission to reuse.

The Studio plan is coming. No price is set, and proposed volume terms, a partner directory and early access are ideas under discussion, not benefits to promise in a client quote. Applications currently come through a support ticket saying Studio from an account that already publishes.

Base the quote on what exists: 30 days free with a small banner, then €99 once per site, without a subscription. That includes 150 publications, 50 MB of media, 25 form messages and 25 review tickets. Top-ups are €19 each and do not renew. You can resell at your own price; explain your design, revision and maintenance work separately from that hosting cost.