I’m Andrew Bembridge — Head of Digital Infrastructure, builder, and operator. I write here about leveraging AI across every surface a real business actually runs on.

Most AI writing covers one surface: the API, the model, the agent. I cover the seven I have to make pay rent in the same week — the e-commerce store, the mobile app, the CRM, the Zap graph, the WordPress site, the autonomous engineering harness, and the cross-surface glue that holds it all together.

This blog is the working notebook from that seat.

The surfaces I work across

Agentic harness. I’m building an autonomous orchestration platform — engineering workflows that plan, execute, and review without me babysitting every step. What does “autonomous” actually look like when it’s running your overnight queue? I have opinions, and most of them were earned the hard way.

E-commerce. Where AI earns revenue in a merch stack — product copy, support, recommendations, fraud, ops automation — versus where it’s just a demo with a checkout button bolted on.

Mobile (iOS / Android). On-device vs API, AI features that don’t tank battery or get rejected at App Store review, the realistic UX patterns for shipping AI in a binary you can’t hot-fix.

CRMs. Where LLMs belong (enrichment, summarization, routing) and where they break things (anything that writes back to the source of truth without a human gate).

Zapier, Make, n8n. The new low-code: AI nodes inside glue. When a fourteen-step Zap with a GPT step beats writing a service. When it absolutely doesn’t.

WordPress. Yes, still WordPress. It’s quietly one of the best AI-augmented stacks in 2026, and most engineers are too embarrassed to notice. I’ll explain.

The cross-surface view. What transfers between surfaces. What doesn’t. The generalist’s AI playbook, written by a generalist who’s tired of the specialist takes.

How I write here

First person. Opinionated. Specific tools, named platforms, real failures. No “five trends to watch” posts. No hedged thought-leadership. If I haven’t actually run the thing, I don’t write about it.

Two registers:

  • Essays — where I commit to a take. Roughly monthly.
  • Lab notes — shorter, rougher write-ups of things I shipped or broke this week.

loopcycle

loopcycle is the orchestration platform I’m building — a node-based system where every workflow is visible, composable, executable, and testable. Think n8n, but purpose-built for AI-native orchestration. Most of what I learn about agentic systems comes from building it.

Work with me

I take on a small number of consulting engagements each year — usually with teams who want help wiring AI into surfaces they already own (commerce, CRM, support, content), or who are trying to get autonomous engineering past the demo stage. If that’s you, get in touch.

Connect