Shopping lists get shopping-list outputs. Generic. Shallow. The kind of thing you could have produced yourself in five minutes and wouldn’t be proud of.

There’s a better way. It’s called Socratic prompting. It’s the difference between ordering a cheap takeaway and asking a proper consultant to think through your problem.

Here’s the trick. Before you ask for output, you ask for thinking. You force the AI to reason step-by-step, the way a senior consultant would, before producing the answer.

The output gets better. Immediately. Dramatically. And it costs you nothing extra.

Let me show you how.

Task prompts versus thinking prompts

A task prompt gives an instruction. “Write a product description for my widget.”

A thinking prompt gives a process. “Before writing the product description, list the three main use cases for this widget, identify the ideal customer, and name the one objection a buyer is most likely to raise. Then write the description.”

Same tool. Same model. Completely different output.

The task prompt gets you generic marketing waffle. The thinking prompt gets you something that sounds like it was written by someone who actually understands your product.

The magic is in the “before.” You’ve forced the AI to do the analysis it would normally skip. The final output is informed by that analysis. Everything gets sharper.

This is how consultants work. They don’t start drafting the slide deck on day one. They ask questions first. Who is this for? What are they trying to achieve? What’s in their way? What’s worked before?

Those questions shape the output. Without them, you get a template. With them, you get insight.

Why shallow prompts produce shallow output

AI models work by pattern matching. You give them an input. They produce the most likely output based on everything they’ve read.

When the input is “write a LinkedIn post about sales,” the most likely output is a generic sales post. There are millions of those. The AI averages them.

When the input is specific — with constraints, context, and thinking — the output can’t be the average. It has to fit your constraints. It has to reflect your context. It has to pass through your thinking before it writes.

Specificity forces quality. Vagueness invites average.

Most owners complain that AI produces boring writing. They’re right. But the AI isn’t being boring. The prompt is being vague. Fix the prompt, and the quality changes overnight.

Three Socratic templates

Here are three templates you can steal today. Each one follows the same pattern: question first, output second.

Template one: strategy

Use this for anything where you need a strategic opinion.

I'm working on [problem/decision].

Before recommending an approach, answer these questions:
1. What are the three most common ways businesses solve this?
2. What are the weaknesses of each approach?
3. What information would a good consultant need before giving advice?
4. Based on what you know, what would you ask me next?

Then, given your analysis, recommend an approach.

The AI has to think. It names the options. It critiques them. It identifies what it doesn’t know. Only then does it recommend.

Run this instead of “what should I do about my pricing?” and watch the quality jump.

Template two: content

Use this for writing tasks.

I'm writing a [blog post / newsletter / LinkedIn post] about [topic].

Audience: [specific description — who they are, what they know, what they care about]

Before writing, answer:
1. What are the three most common takes on this topic already published?
2. What's a non-obvious angle most people miss?
3. What's the one thing my audience needs to understand or do after reading?

Now write the post, using the non-obvious angle, ending with a clear next action.

This forces the AI to scan the obvious and pick something sharper. It also sets a purpose: not just to inform, but to change behaviour.

Template three: problem-solving

Use this for operational or technical problems.

I have a problem: [describe it in plain terms]

Before suggesting a solution, work through:
1. What are the possible root causes, ranked by likelihood?
2. What questions would help me diagnose the real cause?
3. What are the costs of misdiagnosing this?
4. What's the lowest-risk first step to test the most likely cause?

Then, recommend the first step.

Instead of jumping to a solution, the AI has to diagnose. You get a tested recommendation instead of a guess.

How to build a prompt library

Good prompts are assets. Treat them that way.

Start a shared document. Google Doc, Notion, a plain text file in your vault. Call it “Prompts.”

Every time you write a prompt that produces a great output, save it there. Note:

• What you were trying to do

• The full prompt you used

• What worked about the result

• Anything you’d tweak next time

After a month, you’ll have twenty or thirty reusable prompts. After six months, you’ll have a hundred.

Organise by use case. Sales. Content. Strategy. Research. Admin.

When a team member needs to do a similar task, they don’t start from scratch. They grab the prompt, adjust the specifics, run it.

This is how small teams outperform big ones. Shared assets. Shared thinking. Compounding value.

The CLAUDE.md pattern

Here’s a next-level move. Most teams don’t do this. The 11% do.

Create a single file that describes your business, your voice, your standards, your context. Save it in your prompt library. Every time you use AI for anything non-trivial, paste the context at the top.

For me, that file is called CLAUDE.md. It lives in my T40 OS vault. It covers:

• Who I am and what my business does

• My voice (British English, Hemingway Grade 4, no AI slop)

• My target customers

• My current priorities for the quarter

• My key people and active projects

• My values and what I won’t compromise on

Every significant AI conversation starts with that context. The AI knows who it’s helping. It knows the rules. It knows the goal.

Outputs get sharper. Errors drop. Consistency goes up.

This is the shared team brain the 11% build. You don’t need fancy software. You need a text file, a commitment to keep it updated, and the discipline to use it.

What to avoid

Three common mistakes when you start using Socratic prompts.

Asking too many questions. Three to five guiding questions is the sweet spot. Ten is overkill. The AI starts producing a checklist instead of reasoning.

Leading the witness. Don’t ask questions that telegraph the answer you want. “What are the weaknesses of the competitor’s product?” is fine. “Why is the competitor’s product terrible?” is a loaded question. The AI will produce whatever confirms your bias.

Skipping the thinking output. Let the AI show its work. Don’t say “think about this but don’t tell me your thinking.” The act of writing the analysis changes the final output. You benefit from reading it too — sometimes the analysis is the answer.

Why this works

Two reasons.

First, AI models produce better output when they’re forced to reason step-by-step. This is well-documented in research. Chain-of-thought prompting improves accuracy on complex tasks by thirty to fifty percent in some benchmarks.

Second, the process of writing a Socratic prompt forces you to think clearly. Half the benefit is in the prompt construction. You clarify what you actually want. The AI is then more likely to deliver it.

It’s a two-way upgrade. The AI reasons better. You brief better. The gap between mediocre and excellent closes.

The practical bit for this week

Next time you sit down with an AI tool for a non-trivial task, pause.

Before you type the task, type three guiding questions.

Example. You want a value proposition for a new service. Instead of “write me a value proposition,” try:

Before writing a value proposition for [service], answer:
1. What does a strong value proposition always contain?
2. Who is the ideal customer for this service, and what are their top three pains?
3. What are the two most common objections someone might raise?

Now write three value propositions. Each should be one sentence.

Compare the output to what you’d have got from a plain task prompt.

Do this five times this week. After five, you’ll never write another shopping-list prompt.

The big shift

The difference between an AI user and an AI operator is the prompt.

Amateur users give AI tasks. Operators give AI thinking frameworks.

Amateurs get drafts. Operators get insight.

Amateurs cancel their subscription after three months because the outputs feel shallow. Operators compound their skill every month because their prompt library keeps getting sharper.

It’s the same tool. The same £20 a month. Completely different businesses built on top of it.

The bottom line

Better prompts produce consultant-level thinking. Not faster drafting. Actual analysis. Actual reasoning.

Ask guiding questions first. Request the output second. Save what works. Share it with your team. Maintain a shared context document.

That’s the Socratic prompt. Simple. Free. Transformational.

Use it today. Your next AI output will be better than your last one. Keep using it, and your AI stops being a novelty and starts being a consultant.

Sources:

• Industry research on chain-of-thought and Socratic prompting — forces step-by-step reasoning, significant quality improvement

• Team best practice — shared prompt library drives adoption and consistency

• CLAUDE.md pattern — shared context file as a team brain

Practical action for this week: Before your next five AI requests, write three guiding questions first. Compare outputs to your usual prompts. Save the best results to a prompts document.

Next week: why one person should own your AI automation.

Three months later, the owner says, “What happened to our AI project?”

Nobody’s sure. It sort of petered out.

This is diffusion of effort. It kills AI projects faster than anything else, including bad tools and thin budgets.

The fix is almost embarrassingly simple. One person owns it.

Not “everyone.” Not “the team.” Not “whoever has time.”

One person. Named. Accountable. Given a small number of hours a week and a clear remit.

That’s the AI champion. Every business that gets real value from AI has one. Every business that doesn’t, doesn’t.

Let me show you how to set this up in the next fortnight.

The “too many cooks” problem

When everyone owns it, nobody owns it. That’s true of any initiative, but doubly true of AI.

Here’s why.

AI tools need continuous tuning. Prompts drift. Workflows break when tools update. New features launch monthly. Integration breaks when someone changes their password.

Without an owner, this maintenance doesn’t happen. Workflows rot. People lose faith. The tools get cancelled.

With an owner, someone notices the breakage on Monday morning and fixes it by lunchtime.

This isn’t a governance problem. It’s an attention problem. Somebody needs to be paying attention. If everyone’s paying a bit of attention, nobody’s paying enough.

The AI champion’s remit

Here’s what the AI champion actually does. Four responsibilities.

Research. They read about what’s new. One newsletter, one podcast, one LinkedIn account. That’s it. Not twenty. They spend an hour a week staying current.

Testing. They try one new tool or workflow per month. Not in production. In a test environment. They score it honestly and either roll it out or bin it.

Training. They run a short monthly session for the team. Fifteen minutes. “Here’s one new prompt that works. Here’s one new workflow we’re rolling out. Here’s one thing to stop doing.” Copy-and-paste ready.

Metrics. They track what the automations save, in hours or pounds. They report monthly. They kill workflows that don’t earn their keep.

Four responsibilities. No management. No engineering. No heroics.

The champion isn’t a technical wizard. They’re a curious operator with a tidy mind and thirty minutes a day.

Who should be the champion?

Usually, in a small business, it’s one of three people.

The owner. If you’re under five employees, this is probably you. Embrace it. Block the time. Don’t delegate before you understand it.

The ops manager. Anyone whose job involves looking across the whole business, noticing patterns, and organising systems. Natural fit.

The enthusiast. The person who already uses ChatGPT on the side, experiments at home, brings in half-formed ideas. Give them the remit and watch them grow.

Who it shouldn’t be:

• Someone who’s already drowning in other work

• Someone who hates technology

• Someone who outsources all their thinking

Pick the right person. Pay them attention. Give them the authority to make small decisions without asking.

How to carve out four hours a week

Four hours a week is the magic number. Under that, the role starves. Over that, the role bloats. Four hours is just enough to do the work without it becoming a job on its own.

Most owners panic at “four hours.” They already don’t have the hours. Here’s how to find them.

Hour one: research. Replace one hour of existing reading (LinkedIn scrolling, industry news) with AI-focused reading. Net-zero time cost.

Hour two: testing. Pick an existing repetitive task. Instead of doing it manually, the champion builds an AI-assisted version. Testing time replaces doing time.

Hour three: training. Add fifteen minutes to an existing team meeting. Four of those a month equals one hour.

Hour four: metrics and maintenance. Friday afternoon, when focus dips anyway. Review the dashboard. Check what broke. Note what saved time.

None of this requires hiring. None of it requires overtime. It’s a reallocation of existing attention.

If you can’t find four hours a week for the thing that will make your business faster, cheaper, and sharper, you’ve got a deeper problem than AI.

Success metrics for the first 90 days

Set these on day one. Measure them at day thirty, sixty, and ninety.

Metric one: workflows live. How many automations are running in production by the end of each month? Target: one new one per month. No more, no less.

Metric two: hours saved per week. Track the time the workflows save, across the business. Target: ten hours a week saved by day ninety.

Metric three: cost per workflow. Tool costs plus the champion’s time, divided by hours saved. You want this trending down.

Metric four: adoption. How many team members actively use at least one AI-assisted workflow? Target: everyone, within ninety days.

Four metrics. Simple. Reported monthly.

If the numbers are moving in the right direction, the role is working. If not, the champion and the owner sit down and figure out why.

What success looks like at day 90

Ninety days in, a working AI champion has delivered this:

• Three AI-assisted workflows live in production

• One documented prompt library with at least twenty entries

• A monthly review rhythm that’s actually happening

• Ten hours a week of time returned to the business

• The whole team is comfortable with at least one AI tool

That’s a transformation most businesses never achieve. All because one person owned it.

What success looks like at day 365

A year in, the picture is different.

• Fifteen to twenty live workflows

• A mature prompt library, organised by function

• A team that instinctively asks “can we automate this?” before doing anything three times

• Thirty-plus hours a week returned to the business

• Budget for the AI stack earning 5-10x its cost monthly

• The champion has grown into a more strategic role, with a junior helping on maintenance

This compounds. Not because AI gets better (though it does). Because one person has been paying attention for a year and the institutional knowledge has grown alongside.

That’s an unfair advantage. Most competitors never set up the role, let alone keep it going for a year.

What to avoid

Three traps.

Promoting the wrong person. If you pick someone who resents the extra work, they’ll do the minimum and the role will die. Pick someone who finds this interesting. Volunteers beat conscripts every time.

Making it a committee. “The AI working group” is a death sentence. Working groups meet. They don’t ship. One person, maybe with a sounding board, ships more than a committee of five.

Ghosting the role. You name a champion and then never ask about progress. They get the signal that it’s not important. They deprioritise. Twenty minutes a month of the owner’s attention is enough to keep the role alive.

The owner’s job

You might be the champion. Or you might not. Either way, you have a specific job.

Clear the path. If the champion needs a £30/month tool, approve it without a three-week debate. Speed matters more than precision at this stage.

Protect the time. Four hours a week means four hours. Don’t interrupt with urgent-but-not-important work. Champions who get pulled off their work don’t ship.

Ask about the metrics. Once a month. Friendly. Curious. “How are we doing on hours saved? What’s working? What’s not?”

Celebrate the wins. When a workflow saves six hours a week, say so in a team meeting. Publicly. People repeat what gets praised.

That’s the owner’s role. It’s small. It’s consistent. It makes the difference.

The practical bit for this week

Do three things.

One. Name your AI champion. Write it down. Tell them. It might be you.

Two. Put a thirty-minute recurring meeting in the diary, weekly. Topic: “AI progress.” The champion shows up with one automation idea, one metric update, or one question. That’s the whole meeting.

Three. Give the champion a tiny budget. £150 a month, no questions, no approvals. Enough to try a new tool without friction.

That’s your whole implementation plan for week one. Three things. Thirty minutes of work.

The big shift

AI doesn’t succeed because of tools. It succeeds because of ownership.

The 11% of UK SMEs deploying AI extensively aren’t running special software. They’re running the same Zapier and ChatGPT as everyone else. The difference is one person wakes up every day thinking about it.

You don’t need to hire that person. You need to name them, give them time, and pay attention to what they ship.

Do this today. Not in a month. Not after the next quarter’s planning cycle. Today.

The businesses that win with AI over the next three years are the ones that started owning it properly in April 2026. The ones that waited until autumn will spend the next year trying to catch up.

Pick your champion. Block their time. Get out of their way.

The rest takes care of itself.

Sources:

• Industry best practice — designate one person as the AI workflow owner to avoid diffusion of effort

• AI implementation research — appoint an AI champion responsible for research, testing, and rollout

• BCG/MIT findings — 85% of AI projects fail to move beyond pilot stage, usually due to ownership gaps

Practical action for this week: Name your AI champion. Block thirty minutes a week for an AI progress check-in. Give them a small tool budget with no approval friction.

Next week: what the UK AI copyright confusion means for your business.

The thing is, model upgrades are now too fast to track. GPT-5.5 Instant became ChatGPT’s default on 7 May 2026. The third model change in three months. By the time you’ve tested the new one, adjusted your prompts, and trained your team, there’s another one coming. Luma’s Uni 1.1 reasons about prompts before generating. The model layer is differentiating so fast that any advantage you get from “using the latest” evaporates in weeks. You’re not building a moat. You’re running on a treadmill that keeps getting faster. And you’re getting tired while your competitors are getting faster.

The four parts of a workflow that survive any model change are simple. The input format. How you feed data in. What structure, what context, what examples. The prompt library. What you ask for. The exact wording that gets the best result. The output checks. How you verify what comes back. The three things you look for before you send it to a client. The fallback path.What you do when the model fails. The manual process you revert to. If you have these four documented, you can swap models in an afternoon. If you don’t, every model change breaks your process. You spend a week re-tuning prompts that worked fine yesterday. You miss deadlines because the new model formats JSON differently. You look amateur because your tool suddenly produces gibberish and you don’t know why.

The cost of always moving is hidden. You never finish anything because you’re always testing the new thing. Your team learns half a dozen tools and masters none. Your clients get inconsistent output because you’re changing the engine under the bonnet every month. They notice. They just don’t say anything until they leave. Meanwhile, the cost of standing still is obvious. You miss real improvements. Your competitors build better workflows while you’re still debugging prompts from last quarter. The trick is to move deliberately. Upgrade when the workflow is stable, not when the model is new. Build the machine first. Then swap the engine. Document the four parts before you buy the premium subscription.

The workflow audit. Pick your top 3 AI workflows. For each, write a one-page playbook. Inputs, outputs, prompts, checks. Store them where your whole team can find them. When the model changes, your playbook doesn’t. That document is your moat, not the AI underneath. Do it this week. Before the next model drops and breaks your favourite prompt.

Ben

PS. The best AI teams I know treat models like they treat cloud providers. Swappable. Documented. Boring. The magic is in the workflow, not the engine. If that makes sense.

The thing is, British scepticism works differently. It’s not loud. It’s polite. A nod, a smile, and a slow drift toward the exit. UK buyers have a low tolerance for hype. A sharp ear for marketing speak. And a particular distrust of anything that feels too smooth. AI-generated everything fails all three tests. The email is too well-structured. The follow-up is too perfectly timed. The personalisation mentions their company but not their actual problem. They notice. They just don’t tell you. They delete the email and move on. You think they didn’t see it. They saw it. They rejected it in three seconds.

There are five tells of AI outreach a UK buyer spots in seconds. The greeting is too warm for a cold email. “I hope you’re well” from a stranger is a red flag. No one believes that. The flattery is generic. “I loved your recent post” without naming the post. The value proposition is vague. “We help businesses like yours grow” without saying how. The call to action is too soft. “I’d love to grab a coffee” instead of a specific ask. The signature is too polished. A full title, a Calendly link, and a company logo in every email. Real people send messy emails. Real people don’t have time to format a signature block.

So what works instead? Voice notes. A thirty-second voice message shows you’re a real person with a real voice. It breaks the pattern of text. Hand-drafted emails with one typo. Not deliberate mistakes, just natural writing. Named people. “Sarah suggested I reach out” instead of “I found you on LinkedIn”. Specific problems. “You missed your Q1 target” instead of “I help with revenue”. British buyers respond to specifics. They punish polish. They reward preparation. Show them you did your homework, not that you automated it.

How AI should support, not replace, British outreach. Use it for research. Find the pain points. Map the org chart. Identify the trigger events that make this the right week to reach out. Write the first draft if you must. But then rewrite it. Add the awkward phrase. Remove the perfect sign-off. Make it sound like you wrote it on your phone while waiting for a train. Because that’s what a real person would do. The goal isn’t to sound perfect. The goal is to sound present.

The pub test. Before any outreach campaign launches, read three of your emails out loud as if you were ordering a pint. If they don’t sound like a real person talking, kill them. Rewrite them from scratch. Take out the polished phrases. Put in one sentence you’d actually say. AI for research, human for the words. Your pipeline will thank you. And your reply rate will go up.

Ben

PS. Three paid creator promotions were rejected because their content was AI-generated. Kieran Drew documented it. British buyers are doing the same thing to your outreach. They just don’t reply to tell you. They just ghost you. And you never know why.

The thing is, the old maths said “buy SaaS, save time”. The new maths says “build your own with AI for the price of one software seat”. I’m not talking about learning to code. I’m talking about using Claude, v0, or Bolt to generate working software from a description. You describe what you want. The AI builds it. You test it. You tweak it. You deploy it. In a weekend. Maybe two if you’re fussy. The result won’t have every feature. But it will have the features you actually use. And it won’t cost you a monthly fee for the rest of your business life.

LTX Desktop was vibe-coded by 2.5 people in 10 days. That’s a professional video editor. Not a prototype. A working product that edits real footage. Charlie Hills used Claude Code to build infographics and launched a SaaS from inside Claude. He didn’t hire developers. He didn’t rent an office. He didn’t raise funding. He just described what he wanted and kept refining it until it worked. Then he started charging for it.

Five workflows worth building yourself instead of paying monthly. A simple CRM that tracks exactly what you care about, not the forty features you don’t use. An internal dashboard that pulls data from your existing tools and shows the three numbers that matter. A document processor that handles your specific forms and formats without forcing you into a template. A client onboarding flow that matches your exact process, not a generic one. A reporting tool that generates the one chart your board actually wants, not a dashboard full of metrics no one reads. None of these need to be perfect. They need to work for you. And “works for you” is a much lower bar than “works for everyone”.

The skills you need are smaller than you think. You need to be able to describe what you want in plain English. You need to test what comes back and spot the gaps. You need patience for three or four rounds of refinement. You need to know when “good enough” is good enough. You do not need to know React, Python, or database design. The AI knows that. You just need to know your business. You need to know what good looks like for you.

But there’s a risk. Who owns the code when you leave the AI vendor? If you build your tool inside Claude’s ecosystem and Claude changes its terms, what happens? If the AI stops supporting the framework it built for you, who’s responsible? The answer right now is: you are. You own the code, but you also own the maintenance. If it breaks, you fix it. There’s no support ticket to raise. No account manager to call. No one to blame but yourself. So build small, build simple, and build things you can afford to rebuild. Don’t replace your accounting system. Replace your meeting notes tool. Start with the thing that costs you fifty pounds a month and annoys you every time you log in.

The “one tool, one Saturday” rule. Pick the cheapest SaaS you use. The one that nags you every month because you only open it twice. Spend one Saturday building a Claude-powered replacement. Describe what it does. Test what comes back. Refine until it works. If it works, cancel the SaaS. If it doesn’t, you’ve still learned what your team can build in-house now. Either way, you win.

Ben

PS. Canva’s AI tools have been used 24 billion times to date. That’s 24 billion tasks people used to do in Photoshop or Illustrator or by hand. The tools are already here. The only question is whether you’ll use them or keep paying someone else to do what you could do yourself.

Anthropic announced a $1.5B joint venture with Blackstone, Goldman Sachs and Hellman & Friedman. A consulting arm. Same day, OpenAI launched a $10B vehicle backed by TPG, Bain, BCG, McKinsey, Accenture and Capgemini. They literally call it “The Deployment Company”. Nineteen investors. Source

Read that list again. Bain. BCG. McKinsey. Accenture. The labs aren’t partnering with consultants. They’re becoming them.

Spare me the hype takes about “AI maturity” and “enterprise readiness”. Here’s what’s actually happening.

They’re not selling software. They’re selling people.

The old model was simple. You pay for an API. You build something. You hope your team figures out how to use it.

The new model is different. The Deployment Company sends actual engineers into actual offices. They sit next to your operations director. They watch how invoices get paid. They map the workflow your finance team has been doing in spreadsheets for fifteen years. Then they rebuild it.

This isn’t software-as-a-service. It’s people-as-a-service, with software wired in behind them.

If that sounds familiar, it should. It’s the Palantir playbook, copied and pasted.

The Palantir move

For years, Palantir got mocked. “They’re just consultants in hoodies.” “It’s not a real software company.” “They send forward-deployed engineers to do bespoke work, that doesn’t scale.”

Then their market cap passed $300B.

Here’s the thing nobody says out loud about Palantir. They didn’t win by having the best models or the cleanest UI. They won by sitting inside the customer. They learned every workflow. They became the wiring. Once you’re the wiring, you don’t get ripped out. You get more budget every year.

OpenAI and Anthropic just looked at that and decided, right, we’ll have some of that.

So they’re hiring forward-deployed teams. They’re partnering with the four firms whose entire business model is putting smart people inside other people’s businesses. And they’re going after the same logos Palantir went after first. Healthcare. Manufacturing. Finance. Retail. Real estate.

Fortune 500 first. That’s where the money is. That’s where the political cover is. That’s where one good case study buys you ten more.

But the labs are not stupid. Mid-market is next.

Why this matters for you

Anthropic’s annualised revenue passed $30B last month. NYT Thirty billion. They are not going to stop at the FTSE 100. They will follow the money down the size curve, the same way Salesforce did, the same way Microsoft did with Dynamics, the same way every enterprise software wave has done.

The question is when they reach you and your customers.

My honest read: 24 to 36 months. Two to three years before “an Anthropic-McKinsey team” or an “OpenAI-Accenture pod” is selling directly into UK firms with 50 to 500 staff. Manufacturers in the Midlands. Accountancy practices in the Home Counties. Care groups, recruitment firms, regional law firms, the kind of business that turns over £5m to £50m and currently has no idea any of this is coming.

That’s your window.

What to do with the window

Let’s be honest, most SME owners are still thinking about AI as a thing they buy. A subscription. A tool. Something to bolt on so their team can write emails faster.

That’s the wrong frame.

The labs just told us what AI actually is at the business level. It’s a deployed system, embedded in workflows, sold by people who understand the industry. The product isn’t the model. The product is the integration. The product is the person sat next to the ops manager mapping the process.

Which means there’s a service business hiding inside this announcement, and right now there are very few people in the UK doing it well for sub-£50m firms.

You have three honest choices, and you need to pick one before someone else picks for you.

Pick advisor. You sit on the outside and help SME owners think clearly about where to spend, where not to, and what to ignore. You’re the calm voice in the room when a vendor walks in waving a deck. Lower revenue per client, but you sleep at night and you keep your independence.

Pick implementer. You roll your sleeves up and become the forward-deployed engineer for firms too small to ever get one from Anthropic. You map their workflows, you wire in the agents, you stay on retainer. Higher revenue, more grit, more accountability. This is where the real money lands for the next three years.

Pick educator. You teach. Cohorts, courses, fractional training inside companies. You build a content engine and you become the person owners trust before they hire anyone. Lower ceiling per engagement, but it scales and it feeds the other two.

You can blend two of these. You probably can’t blend three without going mad. Pick.

(Personally, I think the implementer slot is the most undervalued in the UK right now. Most consultants won’t get their hands dirty in someone else’s CRM at 9pm on a Tuesday. The ones who will are going to own this market.)

The bit nobody wants to say

The labs moving into consulting is not a threat to SME consultants and operators. It’s a green light.

If OpenAI is willing to put $10B behind the idea that real value comes from sitting inside businesses and rewiring them, that idea is now legitimised at the highest level. The market just got told, by the largest AI company on the planet, that this is the work.

You will never out-resource Bain. You don’t need to. Bain is not phoning a fabricator in Sheffield with 80 staff and three production lines. Bain is not driving to a builders merchant in Hull. Bain is busy with insurers and pharma giants for the next three years.

You can be the person who picks up that phone.

The Practical Bit: the 2-3 Year Window audit

Block one hour this week. Just one. Do this:

1. Pick one industry you already sell to, or one you understand deeply from a past life.

2. List the five most painful workflows in that industry. The ones where staff sigh when you mention them. Quoting, scheduling, compliance, debt chasing, onboarding, whatever it is.

3. For each one, write a single sentence describing how an AI agent could do it today. Not in five years. Today, with tools that already exist.

4. Look at the list. That’s your shortlist of services to take to market in the next 90 days.

You don’t need a strategy deck. You don’t need a product. You need five sentences and the nerve to ring three people in that industry next week.

The labs are coming. They’ll arrive in 24 to 36 months. By then you want to already be the person known in your patch for doing this work. Not the person scrambling to learn it while a Capgemini badge walks past you into your customer’s reception.

Pick your role. Run the audit. Make the calls.

PS: If you read the announcement and felt slightly sick, that’s the right instinct. The smart move now is to use that two to three year head start, not stare at it.

“Most enterprises run AI at the margin.” Source

Translation: the big processes, the ones that actually move the P&L, are barely touched. Everyone’s running tiny experiments around the edges. Chatbot here. Summary tool there. A pilot somewhere in marketing that nobody’s reviewed since July.

The thing is, he was talking to billion-pound corporates. But the diagnosis applies just as cleanly to a 20-person business in Stockport.

Maybe more so.

The dirty secret of the AI rollout

You’ve done it, haven’t you. Don’t lie.

Somewhere in your business right now there’s a Notion full of “AI experiments.” A Zapier flow somebody set up in March that nobody can remember the password for. A ChatGPT Team subscription with eleven seats and three active users. A meeting transcription tool. A “smart” CRM add-on. An invoice parser that works 70% of the time, which is the worst possible number.

You’re not alone. You’re the rule.

And the reason isn’t that you’re behind. It’s that the whole industry has been selling you the wrong shape of project.

Spare me the hype about portfolios of AI bets. That logic works for venture funds. It does not work for a business with 23 people, one finance lead, and a roadmap that already has too much on it.

What Krishna actually said

His sharper line, the one that should sting a bit, was this.

“If others are seeing success, why is your company so special that those use cases wouldn’t work?” The Deep View

Read that twice.

The honest answer for most SMEs is: we’re not that special. We just haven’t picked. We’ve been hedging because picking feels risky, and hedging feels prudent. It isn’t. Hedging across twelve half-baked AI tools is the most expensive thing you can do, because none of them ever reach the depth where they pay back.

Krishna’s prescription was almost insultingly simple. “Pick two or three areas where AI could scale massively, as opposed to doing 100 experiments.” The Deep View

Two or three. Not twelve. Not “an AI strategy.” Two or three places where you go deep enough that the thing actually changes how the work gets done.

The pilot trap

Here’s what doesn’t work.

Running a pilot. Nodding sagely at the demo. Sharing a Loom in the team WhatsApp. Promising to “look at it again next quarter.” Quietly never looking at it again.

Ray Wang from Constellation Research had a number for this one. The companies seeing 10x gains in speed and cost? They’re the ones who got past the pilot stage. The Deep View

Past it. Not in it. Not “evaluating it.” Past.

Most pilots die because nobody wanted them enough. They were ordered from the top, or sneaked in by an enthusiast in operations, or bolted on because a competitor mentioned theirs at a Chamber of Commerce lunch. There was no head of department waking up on a Tuesday genuinely wanting the thing to work.

That’s the test. And it’s brutal.

The leadership test (and why your existing rollout probably fails it)

Walk through your current AI experiments. Now ask, for each one, a single question.

Does the person who runs that function actually want this?

Not “agreed to try it.” Not “is happy to host the meeting.” Wants it. As in, has skin in the game, has told you they want it, has a metric they care about that this would move.

If the answer is no, you don’t have an AI project. You have a graveyard plot with a ribbon on it.

The reason this matters is that AI projects are not software projects. They’re change projects with software inside them. The 10/80/10 split that runs through every decent deployment, 10% human framing, 80% AI execution, 10% human refinement, only works when somebody on the human end gives a damn about both ends.

Without that owner, the 80% middle becomes wallpaper. Pretty, ignored, slowly peeling.

What “going deep” actually looks like for a UK SME

Let’s be honest about what this means in practice. You’re not IBM. You don’t have a Chief AI Officer. You probably don’t have a Chief anything except yourself.

Going deep, for a 30-person business, looks like this.

You pick one revenue process. Maybe quoting. Maybe lead qualification. Maybe the first 48 hours of customer onboarding, where the drop-off is killing you and you’ve known it for a year.

You give it to the person who runs that bit. You tell them: this is yours. You have a budget, a deadline, and a number you’re moving. Not “we’ll see what happens.” A number.

Then you stop them touching the other eleven AI things on the list. Because the entire problem is that they’re context-switching across twelve shallow tools instead of getting one thing into the bones of how the team works.

Depth means the AI is no longer a thing you “use.” It’s a thing the work runs through. There’s a difference, and the difference is where the 10x lives.

Why this is good news

Here’s the thing nobody says out loud at the AI conferences.

You’re not behind. You’re early. The corporates are mostly faking it. Krishna basically said so, on his own keynote stage. The sentiment in the C-suite right now is closer to “why isn’t this working yet” than “look at us go.”

Which means a small, focused UK SME that picks two bets and ships them properly will, by mid-2027, be ahead of most businesses ten times its size. Not because of cleverness. Because of nerve. The nerve to kill ten things so two can breathe.

At the end of the day, AI strategy for an SME is mostly subtraction.

The Practical Bit: the Two-Bet Rule

Here’s the action. Do it on Friday. Block 45 minutes.

Step one. Open a blank doc. List every AI tool, subscription, pilot, experiment, prompt library, GPT, automation, agent and “we should look into” running in your business right now. Be honest. Include the ones nobody touches.

Step two. Cross out everything except two. Maybe three if you can genuinely justify it. The criterion is not “which is most exciting.” It’s “which one, if it actually worked at depth, would meaningfully change my P&L or my customer experience.”

Step three. For each survivor, write down three things on a single line.

1. The named owner. A real person who wants it. Not you, unless you actually run that function day to day.

2. The success metric. One number. Hours saved per week, conversion rate, cost per ticket, quote turnaround, whatever.

3. The review date. Six weeks out. In your calendar. With the owner.

Step four. If you cannot name an owner who actually wants the project, kill it today. Cancel the subscription. Archive the Notion page. Tell the team. Don’t let it limp on draining attention.

That’s the whole exercise.

It will feel like you’re doing less. You are. That’s the point. Two bets going deep beat twelve bets going nowhere, every single time, in every business I’ve ever looked at.

Krishna’s giving you permission. Take it.

PS: If you want a second pair of eyes on which two to pick, reply to this email with your list. I’ll tell you which ones smell like real bets and which ones smell like ribbons on graveyard plots.

They call it “AI fog”. The idea, coined by Toby Stuart at UC Berkeley-Haas, is simple. AI is rewriting the future faster than any of us can plan for it. So the long-range decisions you used to make on autopilot, the ones that assumed tomorrow would look broadly like today, suddenly feel impossible. Source

If you’re running a UK business with 5 to 100 staff, you’ve felt this for months. You just didn’t have a label for it.

You sit down to write the 2027 plan. You stare at the screen. Then you close the laptop and go and do something useful, like answering an email or fixing the coffee machine.

The thing is, that’s not procrastination. That’s a rational response to a foggy world.

What HBR actually said

Stuart’s argument is worth reading slowly. He’s not saying AI will eat everything. He’s saying we genuinely can’t see far enough ahead to plan in the way our parents did.

His advice, and HBR’s, is to “swap long-term planning and optimise for optionality.” Source

That’s a fancy way of saying: stop trying to pick the right answer for 2030. Start making smaller bets you can change your mind about.

Let’s be honest, most strategy decks are theatre anyway. Lovely fonts, five-year hockey-stick charts, a slide called “Our North Star”. And then year one happens and the whole thing goes in a drawer.

The fog just made the theatre obvious.

The world we built assumes a stable tomorrow

Look around. Almost every big decision a normal person makes has a long tail attached to it.

A four-year degree. A thirty-year mortgage. A five-year business plan to wave at the bank. A pension you won’t touch for two decades. A strategy offsite where everyone agrees on goals for 2030 over a lukewarm pastry.

All of these assume the world in 2030 looks roughly like the world today, only a bit shinier.

Now look at what’s happening in AI in a single week.

Anthropic, the company behind Claude, just reported revenue growth of 80x in a single quarter. Yes, eighty. They shipped three significant product features the same week. NYTand The Neuron

You cannot plan a five-year operating model around a tool that doubles in capability between board meetings.

So either the assumption is wrong, or your plan is. Probably both.

What the big firms are doing wrong

Big corporates are responding to AI fog by doing the corporate thing. Hiring a Head of AI Transformation. Commissioning a 60-page report. Forming a steering committee. Building a roadmap for 2028.

Spare me the hype. By the time the steering committee has agreed on a logo for the initiative, the underlying tech will have shifted twice.

You don’t have a steering committee. You’ve got you, maybe a partner, maybe a head of operations who’s also doing payroll. That’s not a weakness here. That’s your edge.

You can change your mind on a Tuesday afternoon.

A 200-person company can’t. A 2,000-person one definitely can’t. They’re paid to be consistent. You’re paid to be right.

The optionality move

Optionality is a posh word for keeping your hands free.

Instead of one big bet for five years, you make several small bets for ninety days. You set up each bet so that if it works, you double down, and if it doesn’t, you walk away without bleeding out.

Three rules sit underneath this.

Smaller bets. If a project would sink the business when it fails, it’s too big. Cut the scope until it wouldn’t.

Faster reviews. Ninety days is the longest you should commit to anything you can’t reverse cheaply. Friday afternoons exist for a reason.

Willingness to abandon. This is the one most owners can’t do. You fall in love with a project. You’ve told your team about it. You’ve told your accountant. So you keep funding it long after the evidence says stop.

Here’s what works. Treat every initiative like a tenancy, not a marriage. Three months. Renew or leave.

Here’s what doesn’t. Treating the business plan as a sacred document because you spent £4,000 on a consultant to write it.

A 90-day rhythm you can actually run

You don’t need software for this. You need one whiteboard, or one side of A4, and a recurring Friday slot.

The cadence looks like this.

Day 0. Pick three bets for the next ninety days. Write them down. Each bet has a clear, boring outcome you can measure. Not “explore AI”, that’s not a bet, that’s a vibe. Try “automate the quote-to-invoice process for our top ten clients” or “test one AI sales agent on cold replies for one channel”.

Every Friday. Fifteen minutes. Are we still on the bet, or has the world moved? Anything to kill? Anything to double down on?

Day 90. Sit down properly. Three questions. What worked. What didn’t. What do we now believe that we didn’t believe ninety days ago. Write the next three bets. Repeat.

That’s it. No offsite. No Miro board. No facilitator in a beige cardigan asking how the brand makes you feel.

The boring rhythm is the strategy. Strategy isn’t the document, it’s the willingness to keep choosing.

Why this matters more for you than for a corporate

Here’s the thing nobody says out loud. AI fog is actually better news for small UK businesses than it is for big ones.

The big firms have spent twenty years optimising for predictability. Long contracts. Long planning cycles. Long approval chains. Their entire operating model assumes the fog clears. When it doesn’t, they freeze, and then they form another committee.

You don’t have any of that machinery. You can decide on Monday and ship on Wednesday. The same nimbleness that used to feel like a disadvantage when the world was stable is now the actual moat.

A SaaS competitor with thirty staff and a clean stack will beat a 300-person legacy player who can’t update their systems without a project manager and a six-week sprint plan. Not because the small one is smarter. Because the small one can change its mind.

At the end of the day, the question isn’t “what’s the right five-year answer”. The question is “what’s the cheapest way to learn what’s true in the next ninety days, and how fast can I act on it”.

That’s a question you can answer this afternoon.

The Practical Bit. The 90-Day Bet sheet

One side of A4. Stick it on the wall above your desk. Write it by hand, it sticks better.

Three sections.

The three bets. Three concrete things you’ll commit to over the next ninety days. One sentence each. Each one has a measurable outcome. Each one is small enough that if it fails, the business is fine.

The three Nots. Three things you are deliberately not doing this quarter. This is the bit owners skip. Strategy is what you say no to. Maybe it’s “no new website”, “no new hire”, “no new market”. Write them down so you have something to point at when the shiny thing tries to drag you off course.

The Day 90 decision. One question you’ll properly revisit on day 90. Not before. Things like “do we hire an AI ops person” or “do we sunset the legacy service line” or “do we double the marketing budget”.

That’s your strategy doc until 2027.

Review it every Friday for fifteen minutes. Kill what’s dead. Keep what’s working. Don’t add a fourth bet, three is the cap, your brain has limits and so does the business.

When the fog rolls in next time, and it will, you’ve already got the answer. You’re not planning for 2030. You’re planning for August. And in this weather, that’s the only honest move.

PS. If your accountant asks for a five-year forecast for the bank, give them one. Then put it back in the drawer where it belongs and get back to your 90-day sheet.

Most people read that and think, “right, we need better AI.”

They’ve got it backwards.

The thing is, the AI wasn’t the clever bit. The clever bit happened before anyone typed a prompt. It’s the step everyone skips because it’s boring, unglamorous, and doesn’t make a good LinkedIn post. And it’s the reason your last AI experiment quietly died in a forgotten browser tab.

Let’s be honest. You’ve probably tried this already. Someone on the team got excited about ChatGPT, fed it a contract, asked it to “summarise the key terms,” and got back something that looked impressive for about ninety seconds. Then you tried a second contract. Different format. Different output. Nothing you could actually use across a stack of fifty.

You concluded AI wasn’t ready. Or your data was too messy. Or your business was too bespoke.

None of those are true. You just skipped the boring step.

What Judge Group actually did

Here’s the bit the press release buried under a layer of corporate gloss.

Judge Group used Box Extract and Box AI Studio to run 49 specific compliance checks against every contract that came in. (Box) Forty-nine. Not “summarise this.” Not “find the risks.” Forty-nine named, defined, repeatable questions with expected answer formats.

That’s the whole game. They didn’t ask AI to be clever. They asked it to be a very fast, very tireless intern with a checklist.

Before any AI touched a document, someone sat down and wrote that checklist. Field name. Definition. Where it usually appears. What a good answer looks like. What a red flag looks like.

That document, the one nobody photographed for the case study, is what took six hours of senior reviewer time and squashed it into sixty minutes.

The AI is the cheap bit. The metadata template is the expensive bit. And by expensive, I mean one afternoon of clear thinking from someone who actually understands the work.

The press release buried the real lesson

Box’s own blog quotes the principle directly. “AI contract review only works when you structure unstructured data first.” (The AI Report via Box)

That sentence should be tattooed on every SME owner’s forearm before they buy another AI tool.

Structure the inputs. Then automate.

Not the other way round.

The reason this gets buried is obvious. Software companies sell software. They want you focused on their shiny extraction engine, not on the unsexy thinking work that makes the engine useful. So the headline is “Box AI cuts review time by 83 percent.” The truth is “smart humans defined 49 fields, then Box AI filled them in fast.”

Spare me the hype. The hype is a distraction.

Why “AI didn’t work for us” usually means something else

Here’s the thing nobody says out loud at the AI conferences.

When an SME tells me “we tried AI on our contracts and it was rubbish,” nine times out of ten what actually happened is this. They opened ChatGPT. They pasted in a contract. They asked an open question like “what should I worry about in this?” They got a generic answer. They tried a second document. The answer was structured differently. They couldn’t put the two side by side. They gave up.

That’s not AI failing. That’s a process failing.

You wouldn’t hire a paralegal and say “read this, tell me anything interesting.” You’d give them a checklist. Renewal date. Notice period. Liability cap. Auto-renewal clause. Payment terms. Penalty rates.

The checklist is the work. The reading is the easy part.

AI is the same. Give it the checklist and it’s a quiet, accurate machine. Give it vibes and it gives you vibes back.

The SME version, no Box licence required

You don’t need a Fortune 500 contract with Box. You need three things you already have.

A Google Sheet. Claude (or ChatGPT, fine, I’m not religious about it). A folder of documents you process every week.

Pick one document type. Supplier contracts. Quotes from subbies. Planning permissions. NDAs. Insurance certificates. Whichever one your team handles often enough that the boredom is real.

Open three real examples on your desk. Not the cleanest three. Three normal, slightly annoying ones.

Write down the 5 to 10 fields you always end up pulling out by hand. The bits you squint for. Renewal date. Counterparty name. Total value. Termination clause. Payment terms. Indemnity cap. Governing law.

That list is now a metadata template. Welcome to the boring step. You just did it.

Drop your three sample documents into Claude along with the list. Ask it to return the answers in a table, one row per document. Read the output critically. Where did it guess? Where did it get confused? Adjust the field definitions. Run it again.

By the end of the afternoon you’ll have an extraction routine that works. By Friday you’ll have run it across fifty documents in the time it used to take to do three.

Here’s what works. A tight checklist of named fields with clear definitions, fed to a capable model, with a human spot-checking the output for the first week.

Here’s what doesn’t. “AI, please be helpful with these contracts.”

Why this beats every shiny AI launch this year

Every fortnight there’s a new model, a new agent, a new framework, a new platform that claims to do your job for you out of the box.

None of them solve the actual bottleneck.

The bottleneck isn’t model intelligence. The models are already smarter than they need to be for 90 percent of SME work. The bottleneck is that nobody has written down what they actually want, in a format that’s repeatable, measurable, and boring.

Once you’ve done that, the choice of model becomes almost a footnote. Claude, GPT, Gemini, whatever. They’ll all do the job. The work that matters is the thinking you did before you opened the chat window.

That’s the bit no software vendor will sell you, because it’s not software. It’s about an hour of an experienced human’s attention. Yours, probably.

At the end of the day, the SMEs who win at AI over the next two years won’t be the ones with the biggest tooling budget. They’ll be the ones who sat down for ninety quiet minutes per workflow and wrote the checklist.

The Practical Bit. The Five-to-Ten Audit.

Block ninety minutes this week. Diary it. Don’t tell anyone.

Pick one document type your team processes every single week. Supplier contracts. Planning permissions. Customer quotes. Onboarding forms. NDAs. Whichever one bleeds the most hours.

Pull three real examples. Not perfect ones. Real ones.

List the 5 to 10 fields you always extract by hand. Name them. Define them in one sentence each. Note where they usually appear in the document.

That list is your metadata template.

Hand it to Claude with the three sample documents. Ask it to return a table, one row per document, one column per field. Check the output. Tighten the definitions where it stumbled. Run it again.

By Friday, you’ve got a working extraction agent. By next month, you’ve got hours back every week.

Total spend. Zero.

PS. If your first instinct reading this was “we’ll need to buy a tool first,” that’s exactly the trap Judge Group avoided. They built the checklist before they built the workflow. You can too, on a sheet of A4.

AI Leadership Minute: Stop Training, Start Showing

You’ve bought the AI tool. You’ve booked the training day. You’ve blocked out everyone’s calendar.

Two weeks later, nobody’s using it.

Here’s why:

Training teaches people how a tool works. It doesn’t teach them why they should care. And adults don’t adopt new tools because they sat through a webinar. They adopt them because they saw someone solve their specific problem in real time.

The Real Problem

Most AI training is generic. “Here’s how to write a prompt.” “Here are 10 use cases.”

Your team sits politely. Takes notes. Goes back to their desk. Opens Excel. Does things the old way.

It’s not because they’re resistant. It’s because nothing in that training connected to the thing they were struggling with at 3pm yesterday.

Generic training creates generic interest. Specific demos create immediate adoption.

The Show-Don’t-Train Method

1. Ask each team member: “What task ate most of your time last week?” Write down the answers.

2. Pick the three most common answers. These are your demo topics.

3. Book 15 minutes with the team. Not a training session. A live demo.

4. Show the AI doing their specific task. Use their actual data. Their actual words. Their actual problems.

5. Hand them the tool and say: “Try it on tomorrow’s version of this task. I’ll check in Friday.”

Why This Works

You’ve replaced theory with proof. Your team didn’t learn about AI. They saw it solve the thing that annoyed them on Tuesday.

The gap between “I understand how this works” and “I want to use this tomorrow” is bridged by relevance. Not curriculum.

Real Example

An accountancy practice in Bristol spent £2,000 on AI training for their team of 8. Adoption after one month: 2 people using it regularly.

They scrapped the training. Instead, the managing partner spent 15 minutes showing how AI could draft client emails from meeting notes. Using a real client. Real notes. Real output.

Adoption two weeks later: 7 out of 8. The holdout started using it the following week after watching a colleague save 30 minutes on a tax summary.

Same tool. No training. Just a relevant demo and peer pressure.

The Real Question

What’s the one task your team complains about most? Can you show them AI doing it in 15 minutes?

That’s not training. That’s proof. And proof sells better than any slide deck.

As promised, value in under two minutes.

Show the work,

Ben

PS - The £2,000 training budget that accountancy firm scrapped? They spent it on a team lunch instead. Better ROI, if I’m honest.

AI Leadership Minute: Write It Down First

Everyone wants to automate their business.

Nobody wants to document their business first.

And that’s why most AI projects fail before they start.

Here’s why:

You can’t automate what you haven’t defined. If your sales process lives in someone’s head, AI can’t touch it. If your onboarding relies on “ask Sarah, she knows,” you don’t have a system. You have a single point of failure.

The Real Problem

Most small businesses run on tribal knowledge. The founder knows the process. Maybe one or two staff do too. But it’s never written down.

Then someone buys an AI tool and tries to plug it in.

It’s like handing a sat-nav to someone who doesn’t know where they’re going. The technology works fine. The destination is missing.

I see this every month. Business owners spend £500 on an AI platform, then realise they can’t describe the process they want to automate in more than three sentences.

The Fix (30 Minutes, Zero Cost)

1. Pick your most repeated process. The one that happens daily or weekly.

2. Watch someone do it. Don’t help. Just watch and write every step.

3. Count the steps. If it’s over 15, it needs simplifying before you automate it.

4. Highlight the decision points. Where does a human need to think? Those stay human.

5. Everything else goes on the “automate this” list.

Why This Works

A written process does three things at once. It trains new staff without your time. It reveals waste you can’t see when you’re inside the work. And it gives AI something concrete to act on.

The checklist is the cheapest employee you’ll ever hire. It works every time, doesn’t forget steps, and never calls in sick.

Real Example

An estate agent in Leeds had a 23-step process for onboarding new landlords. Nobody had written it down. Three different staff did it three different ways.

They spent one afternoon documenting it. Cut it to 14 steps. Automated 8 of those with a simple workflow tool.

New landlord onboarding went from 5 days to 18 hours. No AI platform required. Just a checklist and some common sense.

The Real Question

What’s the one process in your business that only works because one specific person knows how to do it?

That’s your biggest risk. And your biggest automation opportunity.

As promised, value in under two minutes.

Document before you automate,

Ben

PS - If your best employee got hit by a bus tomorrow, how many processes would die with them? Morbid question. Important answer.

This doesn’t happen because AI is hard. It happens because nobody set a plan.

Here’s one. Ninety days. From nothing to a working, measurable AI implementation that pays for itself.

Each week has a job. Each month has a goal. At the end, you know exactly what you’ve built, how much it saves, and what to do next.

Print this. Stick it on the wall. Follow it.

Why 90 days specifically

Forbes and most credible AI consultants recommend a 90-day pilot window for a reason.

Shorter than that and you haven’t given the tool time to prove its value. Longer than that and the urgency evaporates. Somebody gets sick. Something else becomes a priority. The project drifts.

Ninety days is tight enough to stay focused and long enough to produce real results. It’s three months. It’s a quarter. It’s the natural rhythm of business planning.

The businesses that work to a 90-day plan ship working automation. The ones that don’t, don’t.

Month 1: Problem identification and supervised pilot

Week 1: Find the problem

Don’t start with a tool. Start with a problem.

List every task you or your team do at least three times a week. Don’t edit. Just list.

Now score each one on two dimensions:

• Time cost: How many hours a week across the team?

• Enjoyment: How much do people hate doing it?

The tasks that score high on both are your candidates. Pick one. Write it down. That’s the pilot target.

Week 2: Design the supervised pilot

Now design the test. Write down:

• The exact task the AI will attempt

• The tool you’ll use (your generalist AI or a specialist like Dext)

• The metric you’ll measure (time saved, accuracy, throughput)

• The baseline — how long does it take now?

Target: get a supervised pilot running by end of week two.

Week 3: Run the pilot

Every time the task comes up this week, do it twice. Once manually. Once with the AI. Log:

• Time taken (manual vs AI)

• Quality of output

• Corrections needed

You’ll generate real data. Not opinions. Numbers.

Week 4: Decide

Review the week’s logs. One of three things will be true:

• AI beat the manual process cleanly → scale it in month two

• AI matched the manual with editing → refine the prompt or setup, try again next month

• AI couldn’t do the task → pick a different task, start month one again

Whatever the outcome, you’ve learned. That’s the point.

By end of month one, you’ve proven one small thing works. One.

Month 2: Integration and scaling

Week 5: Connect the tools

If month one produced a working workflow in isolation, now you connect it to your existing systems.

This week:

• Wire the AI workflow into your CRM, email, or project tool

• Use Zapier or native integrations where possible

• Test every connection end-to-end

The goal: the workflow runs without you opening a separate app. It happens in the background.

Week 6: Name the champion and train the team

If you haven’t named an AI champion yet, do it now. Give them a four-hour-a-week remit (see my earlier newsletter for the full job description).

Run a short team training session. Fifteen minutes. Show them:

• What the workflow does

• How to check it’s working

• What to do if it breaks

• How to give feedback

Make this a habit, not a one-off.

Week 7: Build the second workflow

By now, the first workflow is solid. You know how it behaves. Trust is building.

Time to start the second.

Same process as month one — problem, pilot, scale. But shorter. You’ve built the muscle. Each new workflow takes less time than the first.

Week 8: Document everything

Take a day to write up what you’ve built. Short SOP. Include:

• What each workflow does

• How it’s connected

• Who owns it

• How to troubleshoot

• Current savings metric

One page per workflow. Stored in a shared location. This is the team brain.

By end of month two, you’ve got two live workflows, an owner, and documentation. You’re ahead of most SMEs.

Month 3: Measurement and iteration

Week 9: Lock the metrics

Pull together the data you’ve been logging.

• Hours saved per week (per workflow and total)

• Cost (tool subscriptions and integration)

• Team adoption (who uses what, how often)

• Error rate (where human correction was needed)

Lay this out on one page. This is your AI scorecard.

Week 10: Iterate based on data

Look at the scorecard. Where are the biggest gaps?

• If error rate is high: tune the prompts, add review steps

• If adoption is low: more training, simpler interfaces, better defaults

• If savings are lower than expected: either fix the workflow or park it

Spend the week making focused improvements. Don’t try to improve everything.

Week 11: Build the third workflow

Start the third automation. By now you’re doing this in parallel with your other work, not as a big project.

The first workflow took a month. The second took two weeks. The third should take one.

That’s how implementation accelerates. Not because AI gets better. Because you get better at shipping.

Week 12: The 90-day review

Pull everything together. Hold a simple review meeting with yourself, the champion, and anyone else involved.

Questions to answer:

1. What did we build? (the three workflows, in detail)

2. What does it save? (hours and pounds, total)

3. What did we learn? (surprises, good and bad)

4. What’s next? (the quarter ahead)

Document the answers. This becomes the case study you reference when someone asks, “Is AI really worth it for us?”

Spoiler: the answer is yes. Now you have proof.

The metric your finance director cares about

All through the 90 days, keep this simple calculation visible.

Monthly AI investment:

• Tool subscriptions: £X

• Champion’s time (4 hours/week × hourly rate): £Y

• Training and setup (amortised): £Z

• Total monthly cost: £(X+Y+Z)

Monthly return:

• Hours saved per week × 4 weeks × average hourly rate

• Revenue generated (from better-responded leads, faster proposals)

• Cost avoided (not hiring, not outsourcing, not missing opportunities)

• Total monthly value: £W

ROI: (W - (X+Y+Z)) / (X+Y+Z)

After 90 days, this ratio should be well over 3:1. Often 5-10:1 for well-built workflows.

If it isn’t, something’s wrong — most likely the workflows are too clever, the adoption is too low, or the measurement is too fuzzy. Fix whichever applies.

What 90 days looks like, realistically

Let me paint the picture.

Day 1: You list ten repetitive tasks. You pick lead follow-up. You decide to test Claude + Zapier.

Day 14: You’ve got a basic workflow running. Every new lead gets an AI-drafted reply that you review and send. It’s rough but working.

Day 30: You’ve logged 26 AI-drafted replies. You sent 22 with minor edits. You saved roughly 7 hours. You’re convinced.

Day 45: You’ve wired the workflow into your CRM. Replies happen automatically when leads come in. You just approve or tweak. Your champion has started building the second workflow — invoice processing.

Day 60: Invoice processing is live. Your accounting pile has disappeared. The champion has documented both workflows. The team has watched a 15-minute training video.

Day 75: Third workflow — meeting notes — is in pilot. Your CRM now automatically gets filled with summaries of every client meeting. Nothing gets forgotten.

Day 90: All three workflows running. Scorecard shows 11 hours saved per week. Total monthly cost: £180. Value generated: £1,600 a month. ROI: 9x.

You can now go back to the drawing board and pick the next three.

This isn’t fantasy. This is what a careful 90-day plan delivers in most SMEs.

What to avoid across the 90 days

Three common failure modes.

Scope creep. Week two, someone suggests adding a second workflow. Then a third. Next thing you know, you’ve started five and finished none. Stick to one per month. Finish each one before starting the next.

Tool hopping. You try Claude. You read that ChatGPT just launched a new feature. You switch. Halfway through, Gemini announces something shiny. You switch again. End result: you know three tools superficially, none of them deeply. Pick one at the start. Stick with it for the full 90 days.

Skipping the scorecard. The people I see fail hardest are the ones who “feel” AI is helping but never measure. The scorecard is the thing that protects your budget when someone senior asks “what does this actually do?”

The practical bit for this week

Print the 90-day plan. Put it on the wall. Start with day one.

• Today: list every repetitive task

• Tomorrow: pick the one with highest time cost and highest team resentment

• Wednesday: pick your tool and write down the metric

• Thursday: design the supervised pilot

• Friday: start running it

That’s week one. Follow the plan from there.

If you stall in week two, your first pilot is probably too ambitious. Pick something smaller. Repeat.

If you stall in month two, your champion doesn’t have enough time. Protect their four hours.

If you stall in month three, your measurement is fuzzy. Tighten the scorecard.

Everything else sorts itself out.

The bottom line

AI implementation isn’t complicated. It’s just structured.

One month to prove one thing works. One month to scale and document. One month to measure and build more.

Ninety days. Three workflows. Ten hours a week saved. Documented proof of ROI.

This is achievable for any UK SME with an owner willing to commit a few hours a week. No agency. No consultant. No expensive platform.

Most businesses won’t do it. They’ll talk about AI all year. They’ll sign up for tools and forget to use them. They’ll end 2026 in the same place they started.

You won’t. Because you’ve got a plan now. And plans that fit on one page, with weekly actions and a clear metric, tend to get done.

Start this week. Day one is listing ten repetitive tasks. That’s it.

In ninety days, you’ll have something most of your competitors will spend the next year trying to build.

There. I said it.

Not in every way. Not emotionally. Not morally. Not with the judgement earned from 30 years of getting things wrong, getting back up, and learning the hard way.

But raw processing power? Pattern spotting? Speed? Memory?

The ability to read, compare, draft, analyse, code, translate, plan, and keep going without a coffee?

It is not close.

AI wins.

And that is the bit most people are quietly wrestling with.

For years, intelligence was the human edge.

If you knew the answer, you had value. If you wrote the report, you had value. If you remembered the process, built the spreadsheet, searched the market, wrote the email, you had value.

Now a machine does most of that in seconds.

So people panic. Or they pretend it is rubbish. Or they use it like a slightly better Google and wonder what the fuss is about.

The honest answer is this.

AI is not the real advantage.

Knowing how to get the best out of AI is.

That is the new intelligence.

Not being smarter than the machine. That ship has sailed. The real skill is knowing how to direct it, question it, constrain it, challenge it, and aim it at something that matters.

Think of it like the best employee you have ever had. But one who turns up with no clue about your business, your clients, your standards, your tone, your politics, your risk, or what “good” looks like.

Brief it badly, you get rubbish.

Ask lazy questions, you get lazy answers.

Accept the first thing it says, you get the same beige output as everyone else.

And no one gives a fuck about beige.

This is where most businesses get AI wrong. They think the tool is the transformation.

It is not.

The transformation is the human using the tool well.

A good human with AI now does the work of a team. A poor human with AI now produces more rubbish, faster.

That is the uncomfortable bit.

AI does not remove the need for judgement. It exposes the lack of it.

If you do not know what good looks like, AI will not save you. If you cannot explain the outcome you want, AI will not guess it. If your business is a mess, AI will not tidy it.

It will just automate the mess.

Faster. Smarter. At scale.

Which sounds impressive until you realise you are making the wrong decisions at scale.

This is where the conversation needs to move.

Less “which AI tool should I use?” More “what problem are we solving?”

Less “can AI write my content?” More “what do we want to be known for?”

Less “can we automate this process?” More “should this process exist at all?”

That is the difference.

AI gives you intelligence. The human gives it direction.

The human brings context. The human spots when an answer is technically correct but commercially stupid. The human knows when something sounds clever but falls apart in the real world.

The human says, “No, that is not how our customers think.”

Or, “That might work for a SaaS company in San Francisco. It is useless for a 40-person business in Doncaster.”

That is not anti-AI.

That is the whole point of AI.

It should amplify good thinking, not replace it. It should help people punch above their weight. It should make the expert sharper, the business owner less buried, the team more capable, and the customer better served.

But only if someone intelligent steers it.

And by intelligent, I do not mean the person with the longest prompt or the fanciest workflow.

I mean someone who asks better questions. Someone who strips a problem back. Someone who tells the difference between useful and impressive.

Someone who understands the output is not the work.

The outcome is the work.

Most people miss that bit.

AI builds a 20-page strategy in 40 seconds. Brilliant.

Does it change a decision? Does it win a client? Does it save the team five hours a week? Does it cut mistakes? Does it make someone’s job easier? Does it help the business make or save money?

If not, who cares?

It is just clever noise.

The businesses that win with AI will not chase every shiny new tool. They will build human-led systems around it.

Clear inputs. Clear standards. Clear checks. Clear ownership. Clear outcomes.

AI does the heavy lifting. Humans do the thinking that matters.

That is where the magic is.

Not man versus machine. Not AI replacing everyone. Not another tired LinkedIn argument about whether it is “coming for your job”.

It is simpler than that.

AI is more intelligent than any human in a lot of ways.

But a human who knows how to use that intelligence well?

That is a different level.

That is the new advantage.

And most businesses have barely started.

The National Living Wage is rising again in April. Employer National Insurance thresholds are frozen. Employment costs are going up whether you like it or not.

At the same time, AI-driven search is eroding the performance of your Google ads and SEO.The traffic you used to get for free is drying up. The paid traffic is getting more expensive.

Costs are rising. Revenue channels are shrinking. It’s a tough time to be running a business.

But the SMEs that survive this won’t be the ones who cut their way to profitability. They’ll be the ones who adapt

.

The 2026 perfect storm.

Let’s be clear about what’s happening.

On the cost side: The National Living Wage increase means higher payroll. Frozen NI thresholds mean you’re paying more tax on the same wages. Energy costs remain volatile. Interest rates are still elevated. Everything that goes into running a business costs more than it did two years ago.

On the revenue side: AI is changing how people find things. When someone asks ChatGPT a question instead of Googling it, they don’t click your ad. They don’t visit your website. They get their answer and move on. Your carefully optimised landing page doesn’t even get seen.

The businesses that relied on Google for traffic are watching their numbers decline. The ones that relied on cheap labour are watching their margins shrink. And there’s no obvious quick fix for either problem.

The agility advantage.

Here’s the counterintuitive bit. In the AI era, small businesses actually have an advantage over large ones.

Big companies move slowly. They have procurement processes, approval chains, and internal politics. By the time they’ve decided to adopt a new tool, you’ve been using it for six months.

Small companies can experiment faster. You can try a new AI tool this afternoon if it looks promising. You can pivot your marketing approach in a week. You can make decisions without consulting a committee.

The squeeze is real. But it affects everyone. And the businesses that adapt fastest will come out ahead, regardless of their size.

Where tech can help (realistically).

I’m not going to pretend that technology solves everything. It doesn’t. But there are genuine opportunities to use it to ease the squeeze.

Communications. Services like Moneypenny can handle your calls and enquiries for a fraction of the cost of a full-time receptionist. You get professional coverage without the payroll overhead.

HR and admin. Tools like Ciphr or BrightHR can automate the tedious parts of people management. Payroll, leave tracking, compliance documentation. The stuff that used to require a dedicated person can now be handled by software.

Marketing. Instead of paying for Google ads that are getting less effective, invest in content and organic reach on platforms where AI hasn’t disrupted things yet. LinkedIn, YouTube, email lists. Owned channels that don’t depend on an algorithm.

Finance. AI-powered accounting tools can handle reconciliation, flag issues, and generate reports automatically. That’s hours saved every month.

The goal isn’t to replace people with tech. It’s to make the people you have more effective, and to avoid hiring for roles that technology can handle.

The outsourcing equation.

Leveraging third-party services and outsourced expertise is one of the smartest moves an SME can make right now.

You don’t need a full-time marketing director. You need a fractional one who works with you two days a month. You don’t need an in-house developer. You need a trusted agency you can call when you have a project.

The fixed cost of an employee, including the wage, the NI, the pension, the equipment, the management overhead, often makes less sense than the variable cost of an expert you pay only when you need them.

This isn’t about being cheap. It’s about being smart. The squeeze rewards businesses that can flex their cost base up and down with demand.

The Practical Bit

Audit your top three highest non-payroll costs this week. For each one, ask: “Could this be done more efficiently with technology or outsourcing?”

Common candidates:

- Reception and phone handling

- Bookkeeping and payroll

- IT support

- Marketing execution

- HR administration

You don’t have to change everything at once. But if you can reduce one of these costs by 30%, that’s margin you’ve just won back. And in a squeeze, margin is survival.

Ben

PS: The SMEs that come out of 2026 stronger won’t be the ones who hunkered down and hoped for the best. They’ll be the ones who used the pressure as a catalyst to get leaner, smarter, and more adaptable. The squeeze is real. But it’s also an opportunity to build a more resilient business. Don’t waste it.

AI Leadership Minute: The 15-Minute AI Audit

Most small business owners think AI adoption starts with buying a tool.

It doesn’t.

It starts with knowing where you’re bleeding time. And most of you have never actually looked.

Here’s why:

You’re too busy doing the work to see the work. The repetitive stuff becomes invisible. You stop noticing the 40 minutes you spend every morning copying data between spreadsheets because it’s “just what we do.”

The Real Problem

The average UK SME wastes 12-15 hours a week on tasks that could be handled by AI right now. Not in some future state. Today.

But nobody maps it. So the waste continues. Month after month. Year after year.

And when someone finally buys an AI tool, they pick the wrong one. Because they never identified the real bottleneck.

The 15-Minute Audit (Do This Today)

1. Grab a sheet of paper. Draw three columns: Task, Time, Hate Score.

2. Write down every task you or your team did yesterday. All of them.

3. Next to each, estimate the time it took in minutes.

4. Give each task a “hate score” from 1-10. How much does your team dread it?

5. Circle anything that scores above 7 AND takes more than 20 minutes.

6. Those circled tasks are your AI shortlist. Stop there.

Why This Works

You’ve just created a hit list based on real pain, not marketing hype. The tasks your team hates most are the ones they’ll happily hand to a machine. And the ones eating the most time give you the biggest return.

Pain plus time equals priority. Nothing else matters.

Real Example

A plumbing company in Birmingham ran this audit on a Tuesday morning. They found their office manager spent 2 hours a day chasing invoice payments by email. Hate score: 9.

They set up an automated payment reminder sequence that afternoon. Three weeks later, overdue invoices dropped 62%. The office manager now spends that time booking new jobs.

Same person. Same desk. Different output.

The Real Question

What’s the highest hate-score task in your business that you’ve been ignoring because “that’s just how it is”?

That’s your starting point. Not a webinar. Not a tool comparison. A piece of paper.

As promised, value in under two minutes.

Pen beats platform,

Ben

PS - The best AI strategy document I’ve ever seen was a Post-it note that said “stop doing the invoicing manually.” Sometimes simple wins.

I turned 50 this year and I’ve noticed something uncomfortable about my own head.

A lot of what I believe about the world wasn’t decided by me. It was decided for me. Drip-fed through a timeline, a news app, a YouTube sidebar, a group chat. By the time an opinion arrived in my brain it felt like mine. It wasn’t. It was the residue of a thousand small nudges from systems designed to keep me scrolling, not thinking.

That bothers me. It should bother you too.

The trap is not the content. It’s the delivery.

The problem isn’t that social media shows you rubbish. The problem is that it shows you your rubbish. Endlessly. In flattering light.

Every platform is optimised for one thing: engagement. Not truth. Not nuance. Not your long-term wellbeing. Engagement. The algorithm learns what makes you react, and then it feeds you more of that. Outrage works. Confirmation works. Certainty works. Doubt and nuance do not work, so you see less of them.

Your brain does the rest. Repetition feels like truth. Familiar ideas feel correct. Opposing views feel like attacks. Psychologists have names for all of this — confirmation bias, the illusory truth effect, availability heuristic — but you don’t need the jargon. You only need to notice the pattern. You are being trained, every day, by a system that does not care whether you are right.

Here’s a small test. Pick a country you have strong feelings about. China, say, or Russia, or America. Now ask yourself honestly: where did those feelings come from? Did you visit? Did you read the primary sources? Did you talk to people who live there? Or did you absorb a mood, over years, from headlines and clips and posts written to make you feel a particular way?

If it’s the second one, you don’t have a view. You have a reflex.

The honest bit

I’ve been guilty of all of it. I spent years consuming news like it was a vitamin. I had strong opinions about places I’d never been and people I’d never met. I mistook being well-informed for being well-fed. They are not the same thing.

The moment I realised I’d been outsourcing my thinking to strangers with business models, something shifted. Not to the other extreme. I’m not about to start shouting about mainstream media lies or fall down a conspiracy hole. That’s just the same trap with different wallpaper. Both tribes are fed. They just eat different meals.

What I want is something older and quieter. I want to think for myself again.

AI as the way out, not the way further in

This is where most people get the story backwards. They assume AI is part of the problem — another algorithm, another feed, another system making decisions for us. And it can be, if you use it passively.

Used well, AI is the first genuinely useful tool we’ve had for pushing back against all of this.

Here’s the difference. A social feed decides what you see. A search engine ranks what you asked for. Both are doing something to you. A good AI model, prompted properly, does something with you. It will argue with you. It will give you the strongest case against your own position. It will surface evidence you didn’t know to look for. It will admit when it doesn’t know. It has no ad inventory to protect and no tribe to please.

That last bit is the key. When I ask an AI to steelman a view I disagree with, it doesn’t get offended. It doesn’t try to win. It just does the work. That is a strange and valuable thing in 2026.

The catch is that AI will happily agree with you if you let it. Ask a leading question, get a leading answer. Most people use AI as a mirror and then complain it only shows them themselves. The fault is not in the tool.

How I actually use it

Five things. Nothing clever. All of them work.

One. I ask for the opposite. Before I accept any view I hold, I ask AI to give me the strongest possible case against it. Not a straw man. The real thing, argued well, by someone who believes it. If my position survives, it’s probably mine. If it doesn’t, I needed to know.

Two. I ask for the sources, not the summary. Summaries are where bias hides. I want to know who said what, when, and with what evidence. “Give me the five most cited studies on this, including the ones that disagree, and tell me who funded them.” That prompt alone has changed my mind about more things than a decade of news consumption.

Three. I ask it to be a sceptic. “Act as a hostile reviewer. Find every weak point in this argument.” You cannot do this well for your own ideas. Your brain is on your side. AI isn’t on anyone’s side, which is exactly what you need.

Four. I check the AI. Models get things wrong. They hallucinate. They have training biases. So I treat every answer as a starting point, not a verdict. I ask “what assumptions did you make?” and “where might this be wrong?” Then I go and look at the primary source myself when it matters.

Five. I decide. This is the one people forget. AI is not there to give me my opinions. It’s there to make sure the opinions I end up with are actually mine — tested, evidenced, and held deliberately. The final call is always human. That’s the whole point.

The quiet payoff

None of this makes me clever. It makes me slower, which turns out to be the same thing in a world optimised for speed.

I notice I post less. I argue less online. I’m less certain about things I used to be certain about, and more certain about a smaller number of things I’ve actually thought through. My feed is quieter because I’m not feeding it. I read primary sources I’d never have found. I change my mind in public sometimes, which used to feel embarrassing and now feels like the whole job.

The strange side effect is that I trust my own views more, not less. Because I know how they got there.

This is the position I want to stand on

I run an AI consultancy. I could tell you AI is going to transform your business, ten-x your output, free up your weekends. Plenty of people are already saying that, loudly, and some of it is even true.

But the thing I actually care about, the thing I’d want on my gravestone before any of the business stuff, is this: in an age where almost everything you see has been chosen for you by a machine that doesn’t have your interests at heart, the most radical thing you can do is think for yourself. And the best tool we have ever had for doing that is now sitting on your phone.

Use it properly and you get your mind back.

Use it lazily and you just have a more articulate feed.

The choice, for once, is actually yours.

She called AI a “tsunami hitting the labour market.” And her biggest concern wasn’t about senior executives or highly skilled specialists.

It was about the juniors.

“Tasks that are eliminated are usually what entry-level jobs do at present.”

Data entry. Basic research. Scheduling. Formatting reports. First-pass email responses. The boring, repetitive stuff that AI does brilliantly. The same stuff that every experienced professional in your business learned by doing when they were starting out.

If AI takes over the entry-level work, where do the next leaders come from?

The 60% number.

The IMF says 60% of jobs in advanced economies like the UK will be affected by AI.

Let’s be clear about what “affected” means. It doesn’t mean 60% of jobs disappear. It means 60% of jobs will change. The tasks within those roles will shift. Some tasks will be automated. Others will become more important.

But the jobs that are most at risk of being fully automated? They’re the entry-level ones. The ones that consist almost entirely of routine, repeatable tasks. And that creates a problem that nobody’s talking about.

The broken ladder.

Think about how you learned your trade.

You started at the bottom. You did the tedious work. You made mistakes on low-stakes tasks. You watched how senior people handled difficult situations. You gradually built judgment, instinct, and expertise through years of hands-on experience.

Now imagine someone joining your business in 2027. The tedious work is done by AI. There are no low-stakes tasks to practise on. The junior hire sits next to the AI and... does what, exactly?

The ladder that every professional has climbed for decades is losing its bottom rungs. And if you can’t get on the ladder, you never reach the top.

The medical residency model.

Medicine figured this out a long time ago. You don’t learn to be a surgeon by reading a textbook. You learn by standing in an operating theatre, watching, assisting, and gradually being trusted with more.

That’s the model I think businesses need to adopt.

Instead of using AI to eliminate junior roles, use it to supercharge them. Give your juniors AI as a tool, not as a replacement. Let them use AI to do the routine work in half the time, and then spend the other half learning the high-value skills they’ll need later.

A junior marketer shouldn’t be replaced by ChatGPT. They should be using ChatGPT to handle the first draft, and then learning from a senior marketer how to make it actually good. That’s apprenticeship for the AI age.

Your role as a mentor.

This is the bit that lands on you as a business owner.

If AI handles the “what” and the “how,” the only thing left to teach is the “why.” Why do we do it this way? Why does this matter to the customer? Why would I choose this approach over that one?

Those are questions of judgment. Strategy. Experience. Critical thinking. The stuff that takes years to develop and can’t be downloaded from a chatbot.

The most valuable thing you can do right now isn’t buying another AI tool. It’s teaching the people around you how to think. How to make decisions when the data is ambiguous. How to read a room. How to solve problems that don’t have a template.

That’s the skill set that AI can’t replace. And someone needs to teach it.

The Practical Bit

Review the tasks you give to your most junior team member. For each one, ask two questions.

First: “Does this teach a skill, or is it just donkey work?” If it’s donkey work, automate it.

Second: “What should they be learning instead?” Replace the automated task with something that builds judgment. Let them sit in on client calls. Give them a small project with real decisions. Ask them to present their own analysis.

The entry-level job isn’t dead. But it needs redesigning. And the businesses that do it first will have better people than everyone else in five years.

Ben

PS: If you’re a young person reading this, don’t panic. The skills that matter most, judgment, empathy, communication, and creative thinking, aren’t going away. They’re becoming more valuable. Learn those alongside the AI tools, and you’ll be ahead of 90% of your peers.

That’s from Jodie Cook in Forbes this week. And when I read it, I didn’t argue. I just felt a bit sick. Because she’s right.

I know where my time goes. Sort of. I know the big things. But the small things? The fifteen minutes here, the twenty minutes there? The “quick” email that turned into an hour of back-and-forth? That’s where the time disappears. And it adds up to roughly 15 hours a week of work that doesn’t move the needle.

AI can give you those hours back. Not hypothetically. This week

.

The 80/20 time audit.

You think you know where your time goes. You probably don’t.

Most business owners have a rough mental model: “I spend most of my time on strategy and client work.” But when you actually track it, the picture is different. A huge chunk goes to admin. Scheduling. Invoice chasing. Formatting documents. Searching for files. Rewriting the same email for the fifth time this month.

None of that is growth work. All of it can be automated or drastically reduced with the right tools.

The first step isn’t buying a tool. It’s seeing the problem clearly.

Your first automation win.

Don’t try to automate everything at once. That’s how people burn out on AI before they even start.

Pick one thing. The single most repetitive, soul-crushing task in your week. The one where you think “why am I still doing this manually?”

Here are the usual candidates:

Email sorting and responses. If you answer the same types of emails every week, AI can draft responses for you. You review and send. What used to take an hour becomes ten minutes.

Scheduling. If you’re still going back and forth with “Does Tuesday work? What about 2pm?” just stop. Calendly, Cal.com, or even ChatGPT can handle scheduling entirely.

Invoicing. If you’re manually creating invoices, chasing payments, and reconciling accounts, tools like Xero with AI add-ons can automate 90% of that process.

Content repurposing. Wrote a blog post? AI can turn it into five LinkedIn posts, three email snippets, and a video script in minutes. Not great content, but a solid first draft you can refine.

Pick one. Automate it. Measure the time saved.

The admin energy drain.

This is the bit people miss. Admin doesn’t just cost you time. It costs you energy.

You sit down at 9am with the intention of doing strategic work. But first, you check email. Then you realise you need to chase an invoice. Then someone asks you to reschedule a meeting. Then you need to update a spreadsheet. By 11am, you’ve done nothing of value and you’re mentally exhausted.

Admin is a cognitive drain. It fragments your attention. It keeps you in reactive mode instead of creative mode. Even if you only save 30 minutes by automating your invoicing, the mental energy you get back is worth far more than 30 minutes.

Protect your recovered hours.

Here’s the trap. You automate 15 hours of admin. You feel great. Then you fill those 15 hours with more admin. Different admin, but still admin. And you’re right back where you started.

“AI gives you leverage without the overhead, drama, or management complexity.” But leverage is only useful if you point it at something worthwhile.

The recovered hours should go to growth work. Client conversations. Strategic thinking. Building relationships. Creating something new. The stuff that actually moves your business forward.

Block those hours in your calendar. Protect them like you’d protect a meeting with your biggest client. Because that’s exactly what they are.

The Practical Bit

For one day this week, keep a simple log. Every time you switch tasks, write down what you just did and how long it took. No fancy tool needed. A piece of paper works fine.

At the end of the day, mark each task as either “Growth” (talking to clients, strategy, creative work) or “Admin” (everything else).

Calculate the percentage.

Prepare for a shock.

Ben

PS: When I first did this exercise, my split was roughly 30% growth, 70% admin. I was spending most of my week on work that didn’t matter. Now it’s closer to 60/40 on a good week. AI didn’t fix that overnight. But it gave me the leverage to start shifting it. One boring task at a time.

“Stop pretending AI automation is marketing.”

They’re right.

There’s a growing wave of businesses that have automated everything, their emails, their social posts, their ad copy, their customer service. And their brand now sounds like every other brand. Flat. Generic. Forgettable. The content reads fine. It just doesn’t feel like anything.

I call it AI Slop. And it’s everywhere.

The rise of AI Slop.

You’ve seen it. You’ve probably scrolled past dozens of examples today without even noticing. LinkedIn posts that feel slightly off. Blog posts that answer the question but leave you feeling nothing. Emails that are technically correct but completely soulless.

The irony is painful. Businesses adopted AI to stand out. And by using it the same way as everyone else, they’ve all blended in.

AI is phenomenal at optimisation and efficiency. It can write a hundred email subject lines in seconds. It can A/B test headlines while you sleep. It can analyse customer data faster than any human.

But it can’t tell you why your business exists. It can’t feel the frustration of your customer. It can’t make a strategic bet based on gut instinct and 20 years of hard-won experience.

Where to draw the line.

I think about it like this. There are two types of work in any business.

Tasks of optimisation. These are repeatable, measurable, process-driven. A/B testing headlines. Scheduling social posts. Segmenting email lists. Reformatting content for different platforms. Give these to AI. All day long. That’s what it’s built for.

Tasks of creation. These are strategic, emotional, human. Coming up with the core campaign idea. Deciding your brand positioning. Writing the story that makes someone feel something. Understanding what your customer is really afraid of. Keep these for your best people.

The businesses getting the best results right now aren’t the ones using the most AI. They’re the ones letting AI handle optimisation while keeping strategy human. It’s not about less AI. It’s about AI in the right places.

The value of empathy in a world of automated responses.

Here’s something AI genuinely cannot do. It cannot sit across from a client who’s worried about losing their business and say “I’ve been there. Here’s what I did.” It can simulate empathy. It can write empathetic-sounding sentences. But it doesn’t know what it feels like.

And your customers can tell the difference. Maybe not consciously. But they feel it. The businesses that’ll win over the next few years are the ones where the humans show up for the moments that matter. The strategy calls. The difficult conversations. The creative leaps that come from truly understanding someone’s problem.

AI handles the how. Humans own the why and the what.

Building a team where AI accelerates, not replaces.

The sentiment on r/Entrepreneur is shifting towards “unsexy, physical products” and real-world execution because those require something AI can’t replicate. Judgment. Relationships. Physical presence. Experience.

Your team structure should reflect that. Free your people from the boring, repetitive, process-driven work by automating it. Then redirect that time towards the high-value, human-only work. Strategy. Creativity. Customer relationships.

Don’t replace your best people with AI. Give them AI so they can do what they’re actually good at.

The Practical Bit

Look at your marketing plan for the next month. For each activity, ask one question.

Is this a task of optimisation or a task of creation?

A/B testing headlines? Optimisation. Give it to AI. Coming up with the campaign concept? Creation. Keep it human. Writing 50 social post variations? Optimisation. Deciding what story to tell? Creation.

Draw the line. Stick to it.

Your competitive advantage was never efficiency. It was always judgment.

Ben

PS: I use AI every single day. It probably saves me 3-4 hours of work daily. But the strategy, the voice, the decisions about what to say and who to say it to? That’s mine. 10% human input, 80% AI execution, 10% human refinement. That’s the ratio.

It’s about finding the most boring, soul-crushing bottleneck in your current operations and killing it with simple automation. That’s it. That’s the whole strategy.

No transformation. No disruption. No futuristic vision. Just find the thing that wastes the most time and make it stop

.

Why UK businesses are right to be cautious.

I’m going to say something that might surprise you. The fact that only 31% of UK small businesses are using AI isn’t entirely a bad thing.

It means we’re not blindly jumping on every bandwagon. British businesses tend to be pragmatic. We want to see proof before we commit. We want to know the ROI before we spend the money. That’s sensible.

The problem isn’t caution. The problem is when caution turns into paralysis. When “let me think about it” becomes “let me think about it for another year.” When the perceived cost of inaction feels like zero, even though it’s compounding every week.

The hesitation isn’t protecting you. It’s costing you.

How to find your boring bottleneck.

Every business has one. Usually more than one. It’s the process that makes people sigh when they have to do it. The task that eats two hours but produces ten minutes of actual value. The thing that’s been “fine” for years but everyone secretly hates.

Here are the usual suspects.

Invoice reconciliation. Someone in your team is probably spending hours every month matching invoices to bank statements, chasing payments, and updating spreadsheets. AI-powered accounting tools can do this in minutes. Literally minutes.

Customer triage. The same three questions come in every day. “What are your opening hours?” “How much does X cost?” “Can I book an appointment?” An AI chatbot handles these instantly, 24 hours a day, without complaining.

Data entry. If someone on your team is manually typing information from one system into another, that’s a bottleneck. Automation tools like Zapier, Make, or n8n can connect your systems and move data between them without a human touching it.

Report generation. Pulling numbers from multiple sources, formatting them into a spreadsheet, and emailing it to the team. AI can do this on a schedule, automatically, with zero human effort.

None of these are exciting. None of them will make headlines. But each one saves real hours every week. And those hours add up fast.

The “Scan, Pilot, Scale” framework.

This is the no-nonsense approach I recommend to every SME I work with.

Scan. Spend one hour (just one) walking through your weekly operations. Write down every task that’s repetitive, manual, or time-consuming. Don’t judge them yet. Just list them.

Pilot. Pick the worst one. The one that wastes the most time or causes the most frustration. Find one off-the-shelf tool that claims to fix it. Sign up for the free trial. Give it two weeks. That’s your pilot.

Scale. Did it work? Did it save time? Did the team actually use it? If yes, roll it out properly. If no, move to the next item on your list. No drama. No sunk cost fallacy. Just try the next one.

The whole point is to start small, prove value quickly, and build confidence through results. Not through strategy documents. Not through AI transformation workshops. Through actual, measurable improvement.

The Practical Bit

Walk into your office tomorrow morning. Ask your team one question.

“What is the one repetitive task you do every week that makes you want to bang your head against the desk?”

Write down whatever they say. That’s your boring bottleneck. That’s where the real value of AI lives for your business. Not in the hype. Not in the headlines. In the boring, practical, head-banging stuff that nobody talks about.

Find it. Fix it. Move on to the next one.

That’s how AI actually transforms a business. One boring problem at a time.

Ben

PS: A UK CEO recently put it perfectly: focus on “boring but high-impact” bottlenecks. If your first AI project saves your team 5 hours a week, that’s 260 hours a year. That’s over six working weeks. Try buying that back any other way.