Skip to content
01Business Automation

The four minutes a person spends being glue.

A document arrives. Six systems need to agree about it. Somebody opens five tabs and retypes the same twelve fields, and by now that is simply the job. This is the work of replacing that person-as-glue with a pipeline that runs in about four seconds and escalates only the cases it is not sure about.

FIVE WAYS AN ORDER ARRIVESPO by email41%EDI drop22%Portal order18%SFTP file12%Phoned in7%WHAT THE RUN WILL NOT DECIDEevery 10012 stop for a personTHE SAME ORDER, BOTH WAYS, TO ONE SCALEby hand4 min 20 sthe run4.34 ssixty times shorter, and nobody typedFIVE WAYS AN ORDER ARRIVESPO by email41%EDI drop22%Portal order18%SFTP file12%Phoned in7%WHAT THE RUN WILL NOT DECIDE12 of every 100 stop for a personBOTH WAYS, ONE SCALEby hand4m 20sthe run4.34 ssixty times shorter, and nobody typed

A finished run leaves the order in your ERP, the confirmation sent and the ship date on it. The twelve it will not decide arrive with a person, with the reason attached.

What the work is

Six things, and what each one actually gets you.

01

Workflow automation

The run itself: what happens when a document lands, in what order, and what the system does when a step fails rather than when it succeeds.

02

CRM integration

Your customer records stop being retyped between sales, support and accounts. One write, everywhere, with the history of who changed what.

03

AI where it earns its place

Reading an unstructured document, matching a fuzzy SKU, drafting a reply. Every one of them behind a confidence threshold you can move.

04

Custom API connectors

The system with no API is the reason most of these projects stall. We build the connector, including the unglamorous ones that scrape a portal on a schedule.

05

Reporting that maintains itself

The weekly spreadsheet somebody rebuilds every Monday becomes a dashboard that is already correct on Monday.

06

Process mapping first

Before any of the above. We time the work as it is actually done, not as the process document says it is done.

What it costs and how it runs

$8,000 to $14,000 to build, and you own it.

Build$8,000 to $14,000 for a first workflow, fixed price
Running$180 to $400 a month, metered, on your own cloud account
Us, after$0. No retainer, no licence, nothing phones home
Not includedLicences for software you do not already own. We will say so before you buy
Week 0

We time it

Two weeks of shadowing before a price exists. This is where the 212 orders a week and the 4 minutes 20 came from, and where a third of the people who ask decide they do not need us yet.

Weeks 1 to 3

It runs beside you, writing nothing

Every disagreement between the system and the person is logged and reviewed together. We do not go live until agreement clears 95%.

Week 4

Live, with the flag in your hand

One switch reverts everything to manual. Your team is shown where it is on day one, before they are shown anything else.

Questions about this one

The ones that decide it.

What if the system we need to reach has no API?
That is the normal case and it is why this is a build rather than a subscription. We have connected to portals by scraping them on a schedule, to accounting packages through their file drops, and to one ERP through a printer queue. If it can be reached at all, we will tell you how in the mapping week, and if it cannot we will tell you that instead.
How do we know it is not quietly getting things wrong?
Every run keeps the raw input and the decision it made. The weekly report shows agreement against the sample a person still checks, and alerts if it drops. The threshold that decides when the system hands over is a slider, not a constant we chose for you.
This is more than we expected. Where does it all go?
You are buying the thing itself rather than renting access to it, and the difference shows up in year two. A subscription rents you somebody else's idea of your process, and repricing it is theirs to do. What you get here is a mapped process, a pipeline that follows it, and the whole thing running in your own cloud account with nothing phoning home. If your volume is a few documents a week, say so in the mapping week and we will tell you the arithmetic does not work yet.
What happens when our process changes?
The map from week zero is a document you own, and the pipeline follows it. Small changes are configuration. A genuinely new step is a small piece of work, quoted the same way. Nothing here is compiled into a black box.

Start with the week where we just watch.

$1,500, five days, a written map of where your hours go and a fixed price for fixing it. Credited in full if you go ahead. It is free to ask, and nobody calls you until you do.