What do you hand over with an AI-built site for a client?
by•
Building a site with AI is quick. Handing it to a client who is not technical is where I see gaps: nobody knows how it is hosted, how to restore a backup, or what to check after an update.
If you build for clients, what do you give them at the end? A short doc, a video walkthrough, admin access in their own name, a maintenance plan?
Curious what has actually prevented support calls for you.
12 views
Replies
The item I'd put at the top isn't a doc, it's an access inventory. Every account the site depends on (domain registrar, DNS, hosting, database, email sending, analytics, any AI API key) listed with who owns it, and ownership moved to the client's email before you leave. The support call you really want to avoid comes two years later, when a card expires on an account in your name and the site goes down, or a key created on your personal account is still live in their frontend. Two things worth doing on the last day: rotate every secret generated during the build, since it has almost certainly been pasted into a prompt or a chat somewhere, and log in as a non-admin user to confirm the admin pages actually refuse you. Do your clients usually want admin access themselves, or would they rather you keep it?