26 years of hard-won insights. No fluff - just what works.
Most AI workflows are prompts applied to empty rooms. This is what an operating system looks like instead — document tiers, named characters, a wiki the model can read, and a boot sequence that loads context before the first prompt arrives.
The AI reflects whatever substrate it meets. The dangerous case isn't where it refuses to answer. It's where it answers fluently and nobody in the room can tell it's wrong.
Every profession that charges for opaque expertise is about to discover the trail was always there. AI doesn't invent evidence — it surfaces what's already readable. The age of 'we did the work, trust us' is ending.
I'd never heard of grep and I've been building websites for twenty-six years. It turns out the simplest operation in computing — searching your own content — is the one most platforms make impossible.
I fed the same article to four frontier AI models. Three returned confident summaries — of articles I hadn't written. They didn't misread the content. They didn't know who I was. The insight that survived had vocabulary with no escape route.
I served every client in a single morning, and somewhere around the third one I realised I hadn't opened a browser. The speed wasn't the point — it was what I could see when the walls between my data sources came down.
I retrofitted 45 files in one commit — every insight on the site got a standfirst and a pull quote in minutes. That's what happens when your content lives in the same repository as your code.
Instructions tell the system what to do. Characters make the wrong thing impossible. Why I stopped writing rules for AI and started installing people instead — and why the obvious candidates all failed.
The prompts don't improve. The corrections do. Eight months of catching the system when it drifts — on voice, on meaning, on honesty — is why the output sounds like a specific person wrote it.
A rule without a face is an instruction. An instruction can be ignored. Why naming principles after characters — Joe Gargery, Robert Maxwell, Marco Pierre White — produces something that lasts longer than a policy document.
Cursor, Windsurf, Lovable — the debate about which IDE is best misses the point entirely. The interface that matters is the terminal. A Telford web developer on why dashboards are friction cosplaying as security.
I treated commits like save points for years. Moving to atomic commits so Claude Code could read the history changed how I run the business.
I built a 4,978-line context file for Claude Code. It collapsed. Then I built a 500-page wiki. That drowned. Three failures taught me an architecture I couldn't have designed from scratch.
Claude Code builds whatever you ask for. That's the problem. Getting it to reach for what already exists — and stay there — took four months, fourteen templates, and one very deliberate refactor.
Claude Code executes. Claude.ai reasons. But unless you close the gap between them, the left hand can't see what the right hand is doing. A Telford web developer on why your tools need a corpus callosum.
The less I say to the system, the better it performs. Not because brevity is clever — because the infrastructure is deep enough to carry meaning. Le Guin, Gene Wolfe, and the art of incluing.
Shopify leads the UK ecommerce market for good reason. But calling it a website builder misses the point. After twenty-six years building online stores, here's what I actually recommend — and when Shopify isn't the answer.
The conversation is all about AI models. The room the model works in barely gets a mention — but it's the room that determines whether the output is generic or genuinely useful.
Step-by-step Wix to Shopify migration — data export, SEO redirect mapping, digital downloads, and the traps Wix sets on purpose. Real migrations, fixed pricing at GBP1,490, 2-week delivery.
If your rankings drop tomorrow, can your web developer show you exactly what changed and when? Mine can. Here's how a tool I'd never heard of became the backbone of how I run my business.
There are two camps on AI: it replaces humans or it's just a fancy tool. Both are wrong. Here's what actually happens when you build with it every day.
Everyone has access to the same AI. The difference isn't the tool - it's whether you've given it somewhere to stand. Situating AI is the craft that separates generic from yours.
Every musician I admire made the same choice — intimacy over scale, craft over volume. The small room isn't a limitation. It's where I do my best work.
Before you rebuild, redesign, or start from scratch — look at what you've already got. I've found that retrofitting existing content and systems is faster, cheaper, and often more effective.
Month one, I explained my business every session. Month seven, one word loaded the whole context. The difference isn't the tool — it's what you build between the conversations.
Every dropshipper sells the same products and competes on price. I built a naming engine that makes my products unsearchable anywhere else. Here's why that changes everything.
AI wants to document everything. That instinct will bury your signal in noise. Here's how to keep it lean.
The AI conversation focuses on prompts. That's 30% of the work. Here's the architecture that makes the system useful instead of generic — including the layer that almost never gets built.
I stopped reading business books and started building things instead. Every ugly first version taught me something no framework ever could.
I had a level system. Level 8, Level 9, Level 10. Then I noticed I was defending the level instead of doing the work. Marco Pierre White solved this decades ago.
I migrated a client from EKM to Shopify and their 3,000 products became 100. Your product count isn't what you think it is — here's what I learnt.
I was losing 20 minutes every session re-explaining context the model had already seen. A wiki in a Git repository fixed it — and the speed difference was immediate.
SEO tools show data, not strategy. I built a keyword ranking model that found 10 orphaned keywords and turned them into 3 complete service pages in 90 minutes. Here's the framework.
Context, not tools, is the real secret to 10x faster development with Claude Code. The speed advantage is the infrastructure I've built underneath.
I've been building pay monthly websites since before it was trendy. Here's how the model works, what the tiers actually include, and why the £3,000 upfront quote is dying. Real pricing from a real person.
I bought Elementor Pro for £199 and lasted two hours. Here's how I used Claude Code and Astro to go from 69 to 99 PageSpeed — and what that decision made possible.
Why AI content fails and how to fix it. My systematic approach to context-driven content that actually ranks and converts.
It took 94 revisions of one document to build a marketing system that actually generates monthly recurring revenue. Here's what survived the editing.
Most AI projects fail because the foundation work never gets done. Here's the structured planning approach that makes AI deliver real results.
I built a production system in four weeks with Claude Code. Twelve months and 2,700 commits later, here's what I actually know about getting reliable code from AI — and why almost none of my original advice still applies.
The algorithm is coming for your business. Here's how to use AI as an amplifier instead of fighting it — lessons from decades of digital evolution.
I walk through selling across multiple channels — Amazon, eBay, your own site — and how to manage inventory, shipping, and pricing without losing your mind.
I stopped guessing what to write and started mapping real customer problems to content that ranks and converts — five data sources, worked examples, and a step-by-step framework.
I sat through a business course and watched the same marketing failure repeat itself. Here are seven things I'd change — starting with the person in the mirror.
I spent years reading AA Gill thinking he was brilliant but unapproachable. Then I found my own voice. Here's the only copywriting superpower that actually matters — and it's not what the courses teach.
I'm not much of a fan of the writing part. But the idea generation, the prompting, the prodding — that's where AI writing tools earn their keep. Here's what they're good at and where they fall short.
How I help clients get more Google reviews — and how you can start generating more enquiries for your business today.
Your customers can't pick it up, turn it over, or feel the weight. I walk through the product image strategy that actually builds trust — from studio shots to lifestyle context, with real before-and-after results.
EKM vs Shopify — which is better for your store? I compare both platforms and walk you through migration step by step. Data transfer, SEO, costs and timelines covered.
Shopify's default UK shipping setup costs you money on every non-mainland order. I show you exactly how to set up postcode-based shipping rates — with the four-zone template that fixes it.
Pricing a website in the UK? I break down the real costs — from logos to SEO — so you know what to expect before you ask for a quote.
100% satisfaction guarantee. Not happy within 30 days? Full refund, no questions. Details