Skip to content

The approach

Business process first. Technology second.

I start by understanding how the work moves through the business — where it slows down, gets repeated or gets lost. Then I decide whether technology can actually improve it.

A desk mid-work: a printed process diagram, a job checklist on a clipboard, a monthly schedule, and an open notebook with a workflow sketched out by hand.

How I think about the work

Start with where the work gets stuck.

An enquiry waits in an inbox. A quote is never followed up. The same information gets copied between three systems. Those are the problems worth finding before deciding what to build.

  1. 01

    Understand

  2. 02

    Find the friction

  3. 03

    Build the smallest useful system

  4. 04

    Test it in real work

What I bring to the work

01Business process

Understand the work before changing it.

Find where work waits, repeats, or depends on someone remembering.

02Software engineering

Build systems that hold up outside the demo.

Real data, errors, integrations and edge cases are the whole job.

03AI & machine learning

Use AI where judgement is actually useful.

Understanding, classifying and responding — not AI inserted into every step.

04Business analysis

Make it work operationally.

The system has to fit the people, tools and process around it.

Tell me what is breaking.

Describe what keeps slowing the work down. I'll help work out whether there is a sensible system worth building.