Workflow automation and AI agents, built on systems you own

A business at reststays at rest.

Manual work does not decay on its own. Someone re-types the invoice. Someone chases the approval. Someone copies the row into the sheet. It happens every week, indefinitely, until an external force acts on it.

We are that force. We map how work actually moves through your business — not how the process document says it moves — and then build the systems that carry it without a person in the loop.

at rest EXTERNAL FORCE we build it, once in motion, unattended, indefinitely
Fig. 1 Friction holds a process still. Applying force costs you once; the motion afterwards is free. Our work is deciding which processes are worth the push.

The way in

A friction audit, free, and the written map is yours whether or not you hire us.

The first build

It ships inside the window we agree at sign-off, or you are not invoiced for it.

If we stay on

The first month of any retainer is refundable, and you can end it any month after.

What we automate

The work nobody should still be doing by hand

These are the processes we are asked for most often. Each is built on your own systems, under your own accounts, and runs without anybody watching it.

Invoices and bills

Invoices arrive by email, get read automatically, are checked against the purchase order, and post themselves into your accounting system. A person only ever sees the ones that do not match.

Replaces re-keying and line-by-line PO matching

Leads and enquiries

Enquiries from your website, WhatsApp and inbox land in one place, get qualified against your own criteria, and reach the right salesperson while the lead is still warm rather than the next morning.

Replaces manual triage, scoring and chasing

Reports and dashboards

Numbers pulled from your systems, assembled into the report you actually read, and delivered to the right people every Monday morning — without anyone spending Sunday night building it.

Replaces the weekly spreadsheet ritual

Customer support

Incoming messages are read, categorised and routed. Routine questions come back with a drafted reply ready to send. Anything unusual goes straight to a person with the history already attached.

Replaces inbox sorting and copy-paste answers

Social media posting

A content calendar that publishes itself. Captions drafted in your voice, images attached, posts going out on schedule to every channel — with a review step so nothing reaches the public without a human saying yes.

Replaces posting the same thing five times

Client onboarding

A client signs, and everything downstream happens on its own — folders created, accounts provisioned, welcome sequence sent, first meeting booked, the internal team told. Nothing depends on somebody remembering the checklist.

Replaces the checklist people keep forgetting

Not on this list? Most of what we build is not. If somebody on your team runs the same sequence of steps more than a few times a week, it is worth a conversation.

What actually changes

Automation removes the waiting, not the people

Below is one accounts-payable process drawn twice. The steps barely change. What disappears is the hand-off between them, which is where nearly all the delay lives.

BY HAND Invoice arrivesemail inbox Re-key into ERPa person, every time Check against POa person, every time Chase approvalthen it sits, waiting File and notifya person, every time Four hand-offs. The invoice waits at every one of them. AUTOMATED Invoice arrivestrigger fires Extract and postautomatic Match to POautomatic Approveone click, on a phone File and notifyautomatic One decision left. The heavy outline is the only step that still needs human judgement.
Fig. 2 The example is accounts payable, but the shape holds everywhere: the steps survive, the queues between them do not.

How we work

Three kinds of force

Automate

The repetitive sequence a person runs today, rebuilt so it runs itself and tells you when it cannot. Workflow automation on n8n, self-hosted on your own infrastructure, with AI agents where judgement is needed and human approval where it genuinely belongs.

Integrate

Most automation fails at the seams between tools. We connect your CRM, accounting, helpdesk and databases properly, and write custom API work where no off-the-shelf connector exists. Unglamorous, and it decides whether the rest holds.

Operate

An automation nobody watches becomes a liability the first time a provider changes something. We monitor every live workflow, fix what breaks, and hand the whole thing over with documentation whenever you want to take it in-house.

How an engagement runs

How working together actually goes

Four phases, in order, because each depends on the one before it. You can stop after any of them and keep what has been built.

Friction audit

Free, and yours to keep

We sit with the people who do the work and follow one process end to end. You get a written map of where the time goes, what is automatable and what is not — whether or not you go on to hire us.

First workflow

Small, fast, provable

We pick the single highest-value process and ship it. One workflow, in production, doing real work. Small enough to approve without a committee, concrete enough that you can judge us on it before committing to anything larger.

System build

Scoped after the audit

Once the first proves out, we build the connected set — the workflows around it, the integrations they depend on, the monitoring that tells you when something breaks. Delivered in working increments rather than one big reveal at the end.

Handover or retainer

Entirely your call

Two honest options. Take it in-house with documentation and training, and we walk away. Or keep us on to run, monitor and extend it. We will tell you which one we think fits your situation, including when the answer is that you do not need us.

Where the risk sits

On us, not on you

We are asking you to trust a supplier with a process your business depends on. These are the terms that make that a reasonable thing to do.

It ships, or it is free

Your first workflow goes live inside the window we agree at sign-off, or you are not invoiced for it.

Month one refundable

On any retainer the first month is fully refundable. If it is not working, say so and it is returned, without an argument.

You own all of it

Workflows run on your infrastructure, under your accounts. No lock-in, no proprietary layer of ours in the middle, and a full export whenever you ask.

Evidence

Evidence, once there is evidence

These spaces are empty deliberately. Anonymous case studies and unattributed testimonials are the easiest things in the world to write, which is precisely why they prove nothing. Each gets filled with a client who agreed to be named.

Case study one

Named client, named process

What the process was, what changed, how long it took — and a contact willing to take a reference call.

Case study two

Named client, named process

A second engagement, ideally in a different industry, showing the approach is not a one-off.

Reference

Attributed testimonial

Full name, role, company, and a link that resolves to a real person. Nothing anonymous.

Questions

Questions people actually ask

What do you build on?

Primarily n8n, self-hosted on infrastructure you own, with custom code where the platform runs out. We will use Make where a client already has it. And we will tell you honestly when a problem does not need automation at all — sometimes the right answer is deleting a step rather than automating it.

Where does our data go?

Onto your servers, under your accounts, by default. Self-hosting is the whole reason we standardised on n8n rather than a hosted platform. Where a workflow calls an AI model, that specific call goes to a provider you choose, and we will tell you exactly what is in it before we build it.

What happens if it breaks after you leave?

Every build ships with documentation and a handover session. If you are on a retainer, monitoring is ours and you hear about failures from us first. If you took the handover and something breaks later, you can bring us back for a fixed-fee repair without negotiating a new contract.

How is this different from just hiring someone?

A full-time automation engineer is a serious annual commitment made before you know whether the work exists to justify it. Start with one workflow, see what it returns, and scale the arrangement from there. If the volume grows to the point where hiring outright is cheaper, we will say so.

Do you work with small teams?

Yes, and they are often the best fit. A five-person company where two people lose a day a week to manual work has a clearer and faster return than a large organisation where the same fix needs six approvals to proceed.

Start with the cheapest possible commitment.

One process, one conversation, a written map you keep either way. If there is nothing worth automating, we will tell you that too — a faster conversation, and a better outcome than being sold something you did not need.