Built to run without me: my first client handovers

I've now built and handed over three client sites that run entirely without me, and that “without me” part turned out to be the whole point.

Three sites, one pattern

Serendipity Life started it. A trilingual brochure site for a holiday-resort photographer. The deep dive has the full story. It went well enough that I did it again: Tiny Tails Pet Care, a fast site for a home-visit pet-sitting business that was stuck on a slow Squarespace, and then Popcorn Simulation Gaming, a fan hub for a charity streamer. Different clients, same shape underneath. And somewhere in the middle of the first one I worked out what actually mattered.

The bit that sold me: it costs nothing to run

I'll be honest: what really did it was discovering how far you can get on free hosting. I'm a bit cheap. A static site on Cloudflare or Netlify, content in Sanity, no server, no database at runtime: the whole thing costs the client nothing to keep online. No monthly Squarespace bill, no surprise invoice, no me sending one either.

That constraint quietly shaped the good decisions. Prefilled WhatsApp and email instead of a paid form service. Images optimised to WebP at build. Nothing that needs a subscription to stay alive.

Delivering a product, not just code

Here's the thing I keep coming back to. The code working is not the same as delivering something the client can run.

So each site is genuinely theirs. They own it. They log into a hosted Sanity Studio and edit everything themselves: copy, prices, testimonials, gallery photos, services, reviews. When they publish, a webhook rebuilds and redeploys the static site automatically. No CMS at runtime, no ringing me up to change a phone number, no me becoming the single point of failure for a typo.

That last part is the freelance lesson I didn't fully appreciate going in. If the client has to call me every time they want to swap a photo, I haven't finished the job. I've just made myself a permanent dependency.

Handover, so far, has been easy

I write a short guide, and Sanity does most of the heavy lifting. It's genuinely friendly to non-developers. It's also helped that we had a lot of back-and-forth during the build, so by the time I handed over, nobody was desperate to change anything. I'm not naïve enough to think it'll always go this smoothly.

Because I'm still learning this. This is my starting point as a freelancer, and I will make mistakes. I've made peace with that. It's often how I learn best anyway. People can hand you the answer, but it rarely sticks like finding out yourself. It's like telling my kid ten times not to touch something hot; they only really learn when they do.

What I actually got out of it

I'm not sure what's next. There are plenty of ways to find clients, and I haven't committed to a direction. But that wasn't really the goal this time.

The goal, it turns out, was answering “can I do this?”: end to end, on my own, for a real person paying real attention. Turns out I can. Along the way I've learned as much about communicating with clients and managing expectations as I have about the code. That feels like the more valuable half.

So: three sites, live, owned by the people they were built for, running without me. For a first go at freelancing properly, I'll take it.