By the problem, not the technology

Name the thing that eats the week.

These are the recurring problems we see most in businesses of 50 to 500 people. Each page says what it costs you today, how it gets removed, and what a person still does. The full working sits underneath for the person who will own it.

Something else? Name it in the free check and we will cost it.

What handing over a job means

Handing a job to software means one recurring piece of work stops being something a person has to remember to do. The software watches for the condition that starts the job, runs it end to end, and returns only what it could not settle. Nothing else about the company has to change for that to work.

That is different from the automation most businesses already own. A workflow runs a path somebody drew in advance, and either follows it or breaks when the input does not match. This reads the input, decides which path it belongs on, and is expected to say when it does not know. The useful consequence is not speed. It is that the awkward cases stop falling on the floor and start arriving in one place with a reason attached.

It is a position rather than a purchase. A category list slowly stops matching the words customers use. A supplier changes a document layout. A sending address loses its reputation. A limit that was right at last year's volume is wrong at this year's. Every job here has a maintenance surface of that kind, and one handed to software nobody operates ends up worse than the manual version it replaced, because the manual version at least complained.

What makes a job suitable

Four tests. A job that fails one of them is usually not ready rather than unsuitable, and the difference matters, because the two have different fixes.

There has to be a starting condition you can observe. An invoice past its due date, a form submission, a ticket sitting unassigned, a file arriving in a shared inbox: in each of those a system changed state, and that change is the entire starting condition. Work that begins because an experienced person noticed something has nothing to watch, and the first task there is finding out what they noticed.

The judgement has to survive being written down. Software cannot infer which customers you want, which code a transaction belongs under, or which of your queues a request should sit in. It applies the version you wrote down, identically on the first record and the ten thousandth, and that consistency is most of the benefit. What you are really buying is the written version, and the software is only the machinery underneath it.

There has to be a check that is not another guess. An invoice states a total that either equals the sum of its own lines or does not. A chase can be tested against a ledger that will eventually disagree with it. A lead score can be compared, months later, against which of those leads became customers. A ticket routed to the wrong queue comes back.

You have to be able to name the conditions under which it stops and asks a person. A dispute rather than a query. Arithmetic that will not reconcile. A submission naming an account somebody already owns. The most important behaviour any of these has is the one where it does nothing and hands back, and it is the part most proposals leave out.

Where the boundary sits

The boundary is not difficulty. It is consequence. Every one of these jobs divides into a half that prepares a decision and a half that announces one, and the two halves carry completely different risk. Reading a ticket and labelling it is reversible; answering the customer is not. Pulling fields off an invoice is reversible; posting it and paying it is not.

So the sequence that works is to hand over the inside half first. It costs less, it fails where somebody can see it, and it leaves behind a record of past decisions that anything attempted on the outside half will need as its starting evidence.

Some things stay on the far side of that boundary permanently. Anything that begins a statutory clock. Anything that creates or waives a legal position. Anything that moves money to a party whose identity has not been confirmed. Anything where the person on the other end is deciding about the whole relationship rather than about this one transaction. In each of those the correct output is a flag and a named owner, and the correct action is none. Which businesses this reaches furthest in is a question the industry fit reports answer.

The one ask on this page

Ninety seconds now. Thirty minutes if it is worth it.

Take the check, see your score with no email asked for, and decide whether the thirty-minute review is worth your time. If you already know the process, skip the check and tell us.