Topic
AI strategy
Not whether a company has an AI plan — most now do, in the loose sense of licences and a policy email — but whether it would survive a bad week. These pieces are about the difference between a plan that exists and one that changes what the company does: what to require before relying on an app someone built, what a real AI plan actually contains, and the questions worth asking before you buy or believe anything sold to you as AI strategy.
-
Sep 11, 2026 Note For companies
AI writes instant legacy code
Code written with AI is being thrown away or rewritten within weeks at twice the old rate, and the share of code being refactored is falling. The draft is faster. Owning it is not.
-
Sep 11, 2026 Note For companies
Fast food architecture
AI is a very good drafter and a poor architect. Treating its output as finished engineering is like living on fast food: it works today and costs you later. The fix is a place the reasoning lives that the model can read back.
-
Sep 11, 2026 Note For companies
The build is the cheap part
A tool built in 48 hours feels free until the first API change. The initial build was always the small share of the cost of owning software, and AI just made that share smaller.
-
Sep 11, 2026 Note For companies
The tool nobody in IT knows about
Shadow IT used to be a spreadsheet. Now it is a working app that runs part of the business, built by one person with an AI tool, and that person is the only one who can change it.
-
Sep 8, 2026 Start here For companies
How robust is your AI plan?
Most companies have something they call an AI plan. Few have one that would survive a bad week. Twelve questions to test yours, the gaps they usually find, and where to start.
-
Sep 5, 2026 Note For companies
A chatbot for everyone is not an AI strategy
It is the most common AI decision a company makes, and the most common place it stops. What the licence buys, what it does not, and the four things it quietly leaves undone.
-
Sep 5, 2026 Note For companies
Seven questions to ask anyone selling you AI
The vendor has a demo. You need answers. Seven questions that separate an AI feature from an AI liability, and what a good answer sounds like.
-
Sep 5, 2026 Note For companies
The app is the visible part
Companies that build or buy an AI feature usually stop at the feature. Three invisible parts decide whether it is an asset or a liability, and none of them is optional.
-
Sep 5, 2026 Note For companies
The coding standard is a file the tool reads
Three people building with AI produce three different codebases unless the standard lives somewhere the tool reads it every time. Not a wiki page. A file in the repo.
-
Sep 5, 2026 Note For companies
The employee who can now build apps
Someone in your company who is not an engineer has built something the business now relies on. It is an opportunity and the biggest new risk in most small firms. What to require before you rely on it.
-
Sep 5, 2026 Note For companies
What a company keeps when the coder leaves
Git keeps the code. It does not keep the reasoning, the gotcha that cost a day, or why the last approach was abandoned. That is a different kind of backup, and most companies do not have it.
-
Sep 5, 2026 Note For companies
Your staff already have an AI plan. You just have not read it.
In most companies without a policy, AI is already in daily use on whatever data is to hand. That is not a discipline problem. It is the plan you get by not writing one.
-
Sep 5, 2026 Playbook For companies
An AI policy in one page
A template for the rules part of an AI plan, written to be followed rather than filed. Fill in the named tools and the named person and it is done.
-
Sep 5, 2026 Playbook For both
The infrastructure around the app
A homework checklist for anyone building an application a business will rely on, and for the leader deciding whether to let them. The app is the easy part; this is everything else.
-
Sep 5, 2026 Playbook For both
Standards and continuity for a small AI-coding team
The repo files that make AI-written code consistent, how a shared vault survives more than one author, the automated handoff that catches unfinished work, and the drill that proves any of it actually works.
-
Sep 5, 2026 Playbook For companies
What an AI plan actually contains
Five short things with owners, not a fifty-page strategy. The plan for a company of ten to two hundred people, what each part is, how long it takes, and the order to do them in.