Automation & Workflows

Not every process needs an agent. Most of the work in a business process is moving data from one place to another, checking it and telling someone when something happens. I build that automation for the processes no off-the-shelf tool covers: deterministic where it can be, with an AI step only where it needs judgement.

Where automation ends and agentic AI begins

The two overlap, and most projects use some of each. The difference is who decides the next step.

In an automated workflow, the steps are fixed: when this happens, do that. A model might classify an email or extract a field along the way, but the workflow decides what happens next. That makes it predictable, cheap to run and easy to audit, and it is the right design for most repetitive work.

In an agentic system, the model chooses which tools to call and in what order. That handles open-ended tasks a fixed workflow can't, at the cost of more testing and oversight. I start with the simplest design that does the job, and add an agent only where the task needs one.

Where an AI step runs on every record, such as routing tickets or tagging documents, a trained classifier is often cheaper and more consistent than calling a general model each time.

Engagement

Working with me on an automation

Deterministic automation for the processes no off-the-shelf tool covers, with an AI step (or a small trained model) only where a decision needs judgement.

Who it's for

  • Teams copying data between systems by hand
  • Processes that run on spreadsheets and reminders
  • Operations that need a report or an alert nobody currently produces
  • Teams with fragile automations that break silently

What you get

  • Working workflows, pipelines, dashboards or alerts
  • Error handling, retries and monitoring
  • Documentation your team can maintain from
  • Hosting on your infrastructure or n8n
  • All code and configuration, yours

What I need from you

  • A walk-through of the process as it runs today
  • Access to the systems involved
  • Who should be told when something fails
  • A process owner

How it runs

Typically 2–6 weeks for a single process.

  1. Week 1

    Map the process

    Steps, systems, data and failure points.

  2. Week 1–2

    Design

    What runs where, what triggers it, where people review.

  3. Weeks 2–5

    Build and test

    Build against real data and edge cases.

  4. Weeks 4–6

    Run and hand over

    Monitored rollout and handover.

From $8,000

Single workflows and data pipelines start around $8,000. Larger automation programmes are quoted on scope after a short call.