01 · Where this fits
Where this fits
The same approach fits wherever a judgement gets made repeatedly, against evidence that already exists somewhere in your business.
That is the test. Not an industry, not a department, not a size of company. If your people make the same kind of call over and over, and the information they need to make it is already sitting in your records, this applies.
Three kinds of work where it does. Then one of them, in full.
Preparing a quote or an estimate
The information is almost always there already: what similar jobs cost, what was quoted last time, which discounts are allowed and who can approve them, which suppliers are current.
What it usually looks like is a person rebuilding that picture from scratch, or from memory, every time. What it can look like instead is the comparable work pulled together, the numbers drafted, and the basis for each of them shown, so the person pricing it is checking a case rather than assembling one.
The price is still theirs to set.
The exception that always escalates to the same person
Every business has one. The awkward case that only Sarah knows how to handle, so it waits until Sarah is free.
The approach here is not to replace Sarah's judgement. It is to write down what her judgement actually consists of, then have the case prepared the same way every time it arises: the relevant history, the applicable rules, what makes this one unusual, and what the options are. Whoever picks it up starts from a prepared case rather than a cold one.
The decision still goes to a person, and where the case genuinely needs Sarah, it reaches her already worked up.
A compliance or verification check
The documents that must be present, the rules that must hold, the things that must be true before something proceeds.
Checks like these fail quietly. They get done properly when someone is careful and has time, and skimmed when they are not. The approach applies well because the requirements are already written down somewhere: the system checks against your actual rules, flags what does not hold up, and shows what it looked at.
What it will not do is decide that something is acceptable anyway. That is a person's call, and it is meant to be.
FIG. 01 · One method, applied three times
the shared spine02 · One of them, in full
One of them, in full
Talk is cheap and AI demos are usually theatre. This one is deliberately unglamorous: the same difficult task, done twice.
The example here is a customer complaint email. It is one of the three kinds of work above, taken end to end so you can see the whole thing rather than a description of it.
03 · The task
The task
A complaint email from an unhappy customer. The kind that needs judgement: an apology that doesn't admit the wrong thing, a policy applied correctly, history taken into account, and a tone that doesn't make it worse. The kind of email a good member of staff spends half an hour on and a tired one gets wrong.
04 · Watch the difference
Round one: a generic AI tool. Round two: done properly.
FIG. 02 · The same difficult task, done twice
demonstration, not client workSame email, same few minutes. One answer is a guess in good English. The other is your business answering, faster.
05 · Round two, in full
What "done properly" actually checks
- It checks first. The customer's history, the relevant policy, the business's own rules about tone and what can be offered.
- It shows its working. The draft arrives with what was checked and why it says what it says, visible.
- It knows what it doesn't know. Where the records don't answer something, it says so and asks, instead of inventing a confident answer.
- It stops. The draft waits for a person. Someone in the business reviews it, sees the evidence, changes what they want and approves it. Nothing was ever going out on its own.
06 · What you're actually looking at
What you're actually looking at
This is a demonstration, built to show the approach. It isn't a client's system and I don't claim it is. It is built the same way as the systems I run in a real business every working day: records in, rules applied, evidence shown, person in charge. What changes for your business is the workflow, the records and the rules. The discipline is the constant.
The part that matters for you
The point of the first conversation isn't to book a project. It's to work out which of your workflows would benefit from this treatment, and then show you, on your kind of problem, what round two looks like for you.