The Disciplines Plate III Intelligent Automation

Intelligent
Automation.

For the jobs you do every week and wish you didn't.

Workflows and custom code that connect the tools you already use and pass the work between them, so nobody has to copy it across by hand. For small businesses across Suffolk and Cambridgeshire.

Return to the workshop

Think about how much time your team spends copying data between systems, sending the same emails over and over, putting reports together by hand and chasing information across four different places nobody remembers signing up to.

Work like that is slow, it is easy to get wrong and nobody enjoys doing it. I build automations that take it over, so that the people you pay can spend their time on the parts that really need a person.

I build on self-hosted automation tools, so your workflows run on infrastructure you control and cost nothing per run, no matter how often they fire. Those tools are good up to the point where a job outgrows them, which happens sooner than the demos suggest, and when it does I switch to custom code in Python or Node.js.

§ What I automate

  1. I.

    Data sync & integration

    A new customer in the CRM gets added to the email platform, and a new order updates the inventory and notifies fulfilment, so nobody has to type the same record into two systems and then wonder which one is right.

  2. II.

    Email & notification workflows

    Emails that go out when something happens, such as onboarding, order confirmations, follow-ups and internal alerts, each one addressed to the person it is meant for. It works with Gmail, Outlook or any mail system that has an API.

  3. III.

    Document generation

    Quotes, invoices, contracts and reports generated from templates against your live data, so a quote that used to take twenty minutes to put together takes about twenty seconds.

  4. IV.

    Automated reporting

    Daily, weekly or monthly reports pulled together from several sources and sent to the people who need them, instead of somebody spending their Friday afternoons rebuilding the same spreadsheet.

  5. V.

    Scheduling & booking

    Booking flows that sync with Google Calendar, Outlook or Radicale, and send the reminders, confirmation texts and rescheduling links without anyone touching them.

  6. VI.

    Alerts & monitoring

    For things like stock running low, a complaint that needs escalating or a website that has gone down, you set the rules once and you are told when one of them trips, at any hour.

§ The process

  1. Step 1

    Process mapping

    I write down how the job is done now, step by step: what starts it, what information it needs and where that comes from. Usually this turns up steps that nobody realised they were doing.

  2. Step 2

    Workflow design

    I design the automated version, including what should happen when something goes wrong, and before anything is built you get a diagram that shows exactly how it will work.

  3. Step 3

    Build & test

    I build it, either as a workflow or as custom code depending on the job, and test it against your own data. When something fails it sends an alert, so nothing breaks without somebody knowing about it.

  4. Step 4

    Deploy & monitor

    It goes onto your infrastructure, or I host it for you. At the beginning I keep a close eye on it, and you get written notes on what it does, plus training for any step that still needs a person.

  5. Step 5

    Refine & expand

    Once it has been running for a while I ask how it is going and adjust it, and quite often the first automation shows which one is worth doing next.

§

Questions, answered

Before you
have to ask

Will this stop working when something changes?

Sometimes, yes, because automations break when a system they depend on changes. Mine are monitored and send an alert when they fail, so you hear about it before a customer does.

Is there a per-run fee?

No. The automations run on infrastructure you control, so you pay for the build and for the hosting and nothing for each time one runs. Platforms that bill per run charge you the most exactly when the automation is doing its job.

What will it cost?

The prices on this page are starting points, so that you can tell in a minute whether you are in the right range. I then quote each job once we have talked it through, because the price depends on the shape of the job, and at this point nobody knows that yet. The first half hour is free, and usually it settles whether this is a small piece of work or a large one before any money is discussed.

Who owns the code when it is finished?

You do, outright, including the source. I hand it over with the runbooks you need to keep it running, and there is no licence to renew and no seat to pay for. When I say commissions, not subscriptions, I mean it literally.

What happens if you are unavailable?

I build everything so that somebody else could pick it up: common technologies, readable code, written runbooks and nothing proprietary. It is a fair question to ask of a one-person business, and the answer lies in how the work is built.

Do you work outside Suffolk and Cambridgeshire?

Yes. With local work you get the option of having me in the room, which is worth more than it sounds for the first conversation and for the handover, and for most clients everything after that is done remotely anyway.