AI consultancy for UK mid-market operators.

What "UK mid-market" actually means

Most AI marketing is aimed at one of two audiences. At the top, FTSE-listed businesses with internal AI teams, eight-figure transformation budgets, and a board paper deadline. At the bottom, the micro-business sole trader buying a £20/month chat tool. Almost everything in between — the £1m–£20m UK businesses doing real work for real customers — gets ignored.

The shape of a mid-market operation is specific. The founder is usually still in the operation, not above it. Headcount is small enough that every hire is a meaningful percentage of payroll. The software stack is a SaaS patchwork that grew organically and now glues itself together with spreadsheets. Decisions tend to wait on the founder because the founder is the operator.

That shape rewards a different kind of AI build. Not a transformation programme. Not a chat widget. A bespoke system that takes one specific bottleneck and dissolves it — so the founder gets their week back and the team scales without breaking.

What I build for UK operators

Every build is bespoke and starts from a discovery call, but the recurring patterns across UK mid-market clients are predictable:

• Bespoke CRMs shaped around how the team actually sells — not how a SaaS vendor thinks selling should work. (See Renew Energies — a full CRM ecosystem and AI-agent stack for a UK solar installer.)
• Vertical platforms for regulated industries where SaaS AI can't go. (See Thermova — bespoke EPC compliance platform with bulk register matching and RdSAP 10 workflow.)
• Inbound automation — voice and SMS agents that answer leads 24/7 inside 60 seconds. (See WheelsAI — used-car dealer platform with sub-minute lead response.)
• Operator-facing apps that replace clipboard, spreadsheet, and email chains with a single bespoke surface. (See TS Plastering — Telegram-to-website pipeline that publishes a case study in 90 seconds.)
• Custom AI systems for bottlenecks that don't fit a category — large-scale document classification, pattern detection across years of internal data, bespoke decisioning workflows.

How working with me actually goes

The mechanism is the same regardless of where you are in the UK:

1. Discovery call (45–60 minutes, free). Technical conversation. We map your operation and identify the three biggest bottlenecks.
2. Costed bottleneck map. You leave with a one-page document naming each bottleneck, sizing it in hours and £/month, and recommending the right next step — process, hire, SaaS, or bespoke build.
3. Build (if a build is the right answer). Discovery → design → build → deploy. Typical timeline 4–12 weeks depending on scope.

The discovery deliverable is the same whether AIMindShift ends up building anything or not. If a process change or off-the-shelf SaaS is the right answer for one of your bottlenecks, that's the recommendation. I'd rather not build than build the wrong thing.

Where I work

Most of the actual engineering happens remotely — the build is code. The face-to-face moments that matter are the discovery scoping session and (where it helps) on-site time during the early stages to see the operation in real conditions. I'm based in the North West myself; UK-wide delivery is the default.

Regional service-area pages with sector context, local references, and on-site working pattern:

• North West England — Manchester, Liverpool, Blackpool, the M6/M62 corridor
• Manchester — fintech, media, professional services, manufacturing
• Liverpool — port logistics, healthcare, knowledge economy
• Blackpool & Fylde Coast — hospitality, trades, holiday-let economy
• Outside the North West: full UK coverage; on-site visits arranged by train or short stay where it adds value

Before you book

Two reading lists that prepare you for a productive discovery call:

• Three operational bottlenecks — the framework I'll be running against your operation.
• Bespoke AI vs SaaS AI — the decision framework with cost ranges and the four criteria.
• Bespoke AI build cost UK — honest 2026 cost ranges by build type.
• How to evaluate an AI consultant — what to ask before you commission anything (including me).

Next step

The discovery call is the same whether you're in Manchester, Macclesfield, or Margate: 45–60 minutes, technical conversation, costed bottleneck map at the end. The build / no-build recommendation is honest — if bespoke AI isn't the right answer for your operation, I'll tell you.