Guide
How to let a client edit a site you built with AI
AI made building the site the quick part. The question that's left is the one every client asks at handover: "can I change it myself?" Here are the six ways to say yes, and a checklist for doing it without risk to your code.
Give them an editor on the site: Siteshare
The client opens their own site at /edit and chats, selects or draws. Drafts until they publish; a build check; one commit on main.
- Best for
- Any Node or plain HTML site on GitHub that you hand over.
- Price
- Free for 1 site; then from $9 a site a month (5 sites $36); clients unlimited.
- Keep in mind
- Sites on GitHub only; the client needs nothing but an email address.
Let an AI editor commit for them: CMS Chat
A chat editor for sites in Git, with safe zones you set per file or component.
- Best for
- Agencies in its invite-only beta.
- Price
- From €99 a month for one site (excl. VAT).
- Keep in mind
- Safe edits commit straight to the branch; no draft or build check described.
Use your host's agents: Netlify Agent Runners
Team members prompt an AI agent in the Netlify dashboard and review a Deploy Preview.
- Best for
- Sites on Netlify, edited by people in your Netlify team.
- Price
- Credit plans: Free, Personal $9, Pro $20 a month.
- Keep in mind
- Sites must be hosted on Netlify; editors work in the dashboard.
Invite them into the builder: Lovable, v0 or Bolt
Add the client as a collaborator in the tool you built with.
- Best for
- Clients who are comfortable with a full builder.
- Price
- Lovable uses your workspace's credits; v0 is $30 per user a month; Bolt uses the prompter's tokens.
- Keep in mind
- The client gets the whole builder, often including publishing and code.
Move it onto a platform: Fimo
A platform for AI-built sites with a visual editor, chat, agents and hosting.
- Best for
- Teams happy to host on the platform and add its SDK.
- Price
- Free (3 sites); Pro $149 a month.
- Keep in mind
- Needs its framework package and schemas; content edits live in Fimo's database.
Add a CMS: TinaCMS, Decap or Keystatic
A Git-based CMS with forms for the content you model.
- Best for
- Sites with clear, repeating content like posts or events.
- Price
- Free to start; TinaCMS from $24 a month per project for teams.
- Keep in mind
- You model every editable field; text inside components stays out of reach.
A handover checklist
Whatever you choose, check these five things before you send the invitation:
- A draft first. The client should see a change before anyone else does.
- A build check. Nothing should go live that doesn’t build, with the packages of today.
- Limits. Text and images by default; design and code stay yours unless you open them up.
- A way back. Earlier versions that come back in one step, as a new change, never a rewrite of history.
- A record. Who changed what, and when, so you can answer the question “what happened?”
Why not just a CMS?
A CMS answers the question with forms on a content model. That works for posts and events. Most of a site built with AI isn’t modelled content: it’s text inside components, sections and buttons. That’s the part your client wants to change, and it’s the part an editor on the site itself can reach.
Questions
Can a client edit a site built with Claude Code or Cursor?
Yes. Those sites are ordinary code in a repository. Siteshare gives the client an editor on top of that repository, without changing how you build or host.
Should I give my client access to my AI builder?
Only if they should be able to change everything. In Lovable, v0 and Bolt a collaborator usually gets the full builder, and in Lovable they use your credits.
How do I stop a client from breaking the site?
Use drafts, a build check before anything goes live, limits on what they may change, and a way back. Siteshare does all four by default.
Hand it over. Get your evenings back.
Free for one site, forever. No card needed.