Strength Base: build it, then hand over the keys.

Strength Base is a website I designed and built for a strength and physio gym in Melbourne's north — brand, pages, and a way to book a visit by phone or WhatsApp, delivered and handed to the owner in August 2026. It's a client build outside my own ventures. This is a first-person account of what that actually involved: the problem, the build, where I had to get out of the way, and where things were genuinely hard.

The problem

The gym had no real web presence — no site an AHPRA-registered pharmacist-turned-builder was doing anything with, just a name and a location. The owner needed something a prospective member could land on, understand at a glance, and book a session from, without needing me on call forever to keep it running.

That last part is the part that shapes everything else here. A lot of "we'll build you a website" arrangements quietly turn into a permanent dependency on the person who built it. I didn't want to sell that, and the owner didn't want to buy it.

What was built

Brand to booking, in one build: the visual identity, the page structure, the copy, and a contact flow that routes enquiries straight to WhatsApp or a phone call, using the same AI-assisted approach I use on my own projects and describe on the work page. It's live and running — you can see it at strength-base-pink.vercel.app.

I'm not going to attach numbers to it. There's no booking count, no conversion figure, no before/after I can stand behind — I don't track the gym's business metrics, and inventing them would break the one rule I hold myself to on this site: evidence over hype, even about my own work.

Where the human gates sat, and what was hard

The build itself wasn't the hard part. AI-assisted design and development gets you to a working site fast — that's the whole premise of what I offer. The hard part was the handover, because a handover is where you find out whether "you own everything" was actually true or just something I said in a pitch.

Concretely: code, hosting, and accounts had to end up somewhere the owner controls, not somewhere that quietly stays mine. That's a discipline decision, not a technical one, and it's the same principle I write into how an engagement runs on the work page — you own everything, no lock-in, no forced retainer. Holding to it on a real handover, with a real non-technical owner on the other end, is a different thing from stating it as a policy. It's the part I was most careful about, and the part I'd point to if you asked me to prove I mean it.

The other real constraint was scope. This was a fixed, bounded build for one owner — not an ongoing product with a backlog. That's a deliberate trade-off: it kept the delivery honest and fast, but it also means there's no continuous iteration loop the way there is on something like LocumOS, which I build and use myself every day.

Current status

As of August 2026, Strength Base is live and the owner has it. I'm not running it, hosting it under my own account indefinitely, or billing a retainer to keep it alive. If something needs changing, that's now the owner's call to make — with me or without me. That's the outcome I was building toward, not an afterthought.

Work with me

If you want a website or a booking/contact flow built the same way — fast, AI-assisted, and handed over properly at the end — see how an engagement runs, or tell me what you need directly.