AI consultancy North West England, AI implementation & bespoke systems.

Why "North West" is a real market, not a geo tag

The North West mid-market has a distinct operational shape. It's not London-style venture-backed scale-ups burning capital for growth, and it's not micro-business in the way the Welsh marches or Cumbria sometimes is. It's founder-led businesses with skilled teams, real customers, and a structural problem common to the region: scaling without losing the operating discipline that got them there.

The capital base is different. Investment timelines are longer. Headcount decisions weigh more heavily because each hire is a meaningful percentage of total payroll. SaaS-sprawl bites harder because there are fewer in-house engineers to glue tools together. The founder-bottleneck tax compounds because the founder is usually the operator, there's no professional CEO layer to absorb decisions.

That shape rewards bespoke AI in ways the London playbook misses. The build doesn't need to scale to ten million users, it needs to give the operator their week back.

What I build for North West operators

Every build is bespoke and starts from a discovery call, but the patterns that recur across the North West are predictable:

• Bespoke CRMs shaped around how the team actually sells, not how a SaaS vendor thinks selling should work. (See the Renew Energies case study, a NW solar installer's full bespoke CRM ecosystem.)
• Trade business websites engineered as conversion flows, with local-SEO targeting across the postcodes that actually matter. (See the Lyttle's Tiling case study, Lancashire-based tiling business.)
• Compliance platforms for regulated industries where data sensitivity rules out SaaS AI. (See the Thermova case study, UK EPC compliance platform.)
• Hospitality and direct-booking builds for operators escaping OTA commission. (See the Stay by the Sea case study, Blackpool seafront holiday let.)
• Voice agents and missed-call recovery for businesses where leads queue up after 5pm and competitors pick them off. (See the WheelsAI case study, UK used-car dealer platform.)

Local working pattern

Most of the actual engineering happens remotely, the build is code, not face-to-face contact. The face-to-face moments that matter are the discovery call, the scoping session, and (where it helps) on-site time during the early stages of a build to see the operation in real conditions. I'm based in the North West myself; on-site visits across Manchester, Liverpool, Blackpool, Preston, and the surrounding Lancashire/Cheshire area are practical.

Cities and towns I work in

• Manchester: fintech, media, professional services, manufacturing
• Liverpool: port logistics, healthcare, knowledge economy
• Blackpool: hospitality, trades, holiday-let economy
• Preston, Lancaster, Bolton, Warrington, Wigan, St Helens, Salford, Stockport, Macclesfield, Crewe, Chester

Next step

The discovery call is the same across the region: 45–60 minutes, technical conversation, costed bottleneck map at the end. The build / no-build call is honest, if bespoke AI isn't the right answer for your operation, I'll tell you.