Vibe coders building for clients: how do you hand the project over to someone non-technical?
by•
More of us are shipping client projects with AI coding tools now, and the build part has gotten fast. The handover hasn't. The client gets a working app but no idea where it lives, how to update a line of copy, or who to call when a domain renews.
Curious how others handle this:
Do you host it yourself and charge a care plan, or move everything to the client's own accounts?
What do you actually give them: a Loom walkthrough, a doc, an admin panel, nothing?
How do you keep them from coming back six months later with "the AI broke it"?
Would love to hear what's worked and what's bitten you.
5 views
Replies
Not client work for me, but the same problem shows up inside my own product, and the answer that held up is to decide early what the non technical side will want to change, and move exactly that out of the code. In my app that is an admin panel for the day to day things, like answering support, and a config document for things like a holiday promo, where a new campaign is one entry with dates and an amount, no release. Everything else stays code and is off limits. For a client I would put the accounts in their name from day one, and hand over that short list of things they can change themselves. If the list is honest, "the AI broke it" turns into "I changed X", which is a much easier call.