The Developer Behind Your Digital Growth

Like most developers who end up running their own practice, I didn't start with a grand plan. I started by building a WordPress site for a local business that needed one, charged far less than I should have, and learned more in that first project than any course could have taught me. What I noticed quickly was that most small businesses weren't being let down by a lack of effort from their previous developer — they were being let down by a lack of follow-through. Sites got built and then abandoned. Plugins went unmaintained. Nobody checked whether the site actually ranked on Google once it went live.

That gap between "a website exists" and "a website actually generates business" became the entire focus of my work. By 2018, word of mouth had brought in enough clients that freelancing became a full-time practice rather than a side project, and the scope expanded naturally as clients asked for things beyond just a website: could I also help with their eBay store that was underperforming? Could I set up email automation so they weren't manually following up with every lead? Each of these became a new specialism, learned properly rather than offered superficially, because half-hearted execution of an additional service does more damage to client trust than simply not offering it at all.

The eBay and eCommerce management work that started around 2019 taught me something that still shapes how I approach every project today: algorithms and platforms reward sellers and businesses who treat optimisation as continuous, not a one-time setup task. eBay's Cassini search algorithm, Google's ranking signals, and now AI-generated search overviews all share this characteristic — they reward sustained, structured effort over time far more than a single clever trick applied once and forgotten.

By 2021, GoHighLevel certification and a growing focus on automation reflected a broader shift I was seeing across nearly every client: the businesses growing fastest weren't necessarily the ones with the biggest marketing budgets, but the ones who had removed the most manual, repetitive work from their operations and redirected that time toward genuinely high-value activity — talking to customers, refining their offer, building partnerships. Automation stopped being a nice technical add-on and became a core part of how I think about every engagement.

Today, the practice spans website development, SEO and AI-search optimisation, AI business automation, GoHighLevel setup for agencies, and eCommerce account management across eBay, Amazon, Etsy, and TikTok Shop. What hasn't changed since that first underpriced WordPress site is the underlying belief that drove me to start: a website, a listing, or an automated workflow is only worth building if it measurably moves your business forward. Everything else is just decoration.

Every engagement starts with the same question: what specific business outcome are we trying to move, and how will we know if it worked? A website project framed around "we need a new site" produces a very different result than one framed around "we need to convert 20% more of our existing traffic into booked calls." The second framing shapes every decision that follows — the page structure, the calls to action, even which pages get built first.

This same discipline applies to SEO and AI search optimisation work. Rather than treating SEO as a checklist of generic technical fixes, every strategy starts by mapping the specific questions your actual customers are asking, in the actual language they use, across both traditional Google search and the AI-generated answer surfaces (Google AI Overviews, ChatGPT, Bing Copilot) that are increasingly where those questions get answered first. A UK business competing for local customers needs a different content and technical strategy than a SaaS company competing nationally, and treating both the same way wastes effort that could otherwise compound.

For automation projects, the starting point is always mapping your current manual process in detail before writing a single line of automation logic. Automating a broken or unclear process just makes the inconsistency happen faster — so the unglamorous work of clarifying exactly what should happen, in what order, with what exceptions, always comes first, even though it's the less visually impressive part of the project.

Across all of this, communication stays deliberately plain. You'll get progress updates in language that explains what was done and why it matters for your business, not jargon designed to make the work sound more impressive than it needs to be. If something isn't working as expected, you'll hear that directly and quickly, along with a clear plan to fix it — not a vague status update designed to avoid an uncomfortable conversation.