Browse all business articles
27 articles in this category
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.
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.
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.
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.
100% satisfaction guarantee. Not happy within 30 days? Full refund, no questions. Details