How to hand off a website to a non-technical client — without a page builder

The reason agencies keep reaching for page builders isn’t love of Elementor. It’s fear of the alternative: a hand-coded site where every text change routes back through you, forever. But the builder trade is bad too — you get client self-service by giving the client the power to break the design, and you get a build experience that fights you the whole way.

The false choice

Page builders couple content and design so the client can edit “everything” — which in practice means they can drag a section 40 pixels left and ruin the spacing on mobile. Hand-coded sites decouple perfectly and give the client nothing. The handover problem isn’t solved by either extreme; it’s solved by drawing the line in the right place.

Draw the line at content

What clients actually change, measured across our client base: text, images, posts, opening hours, menu items, team members, prices. What they essentially never change: layout, typography, spacing, structure. So give them a surface that edits exactly the first list — structured content with types — and keep the second list in code, where it’s safe.

What that looks like in practice

The site is code in your repo; the content lives in a CMS with types you define (a “team member” has a name, a photo, a bio). The client’s admin looks like WordPress — posts, pages, media, drafts — because that vocabulary is pre-trained into every client on earth. They can rewrite every word and swap every photo. They cannot touch a margin.

The handover checklist

Invite the client as admin so it’s clearly theirs. Add their team as editors. Scope any AI key down to author, so agent drafts need human publishes. Put hosting on their card. Send one login link. If handover takes more than an email, the architecture is wrong.

This is the workflow Prelo is built around — see how it works or start with the WordPress alternative comparison if you’re coming from builder land.