In most small businesses there is one person who has to say yes to things, and most of what reaches them is not really a decision.
The job today
A request arrives that needs approval. A discount a rep wants to give. A credit a customer is asking for. A return outside the window. A purchase over somebody's limit. Whether a repair is warranty or billable. Terms for a new account.
It goes to the owner, or the one manager who is allowed to decide, usually as a message that does not contain enough information to decide with. So the first thing that happens is a round trip: what did we quote them, what have they bought before, do they pay on time, what did we do the last time this came up.
Then a decision gets made, and it is made well, because the person deciding knows the business. And then the same shape of request arrives on Thursday and the round trip happens again.
Two costs come out of this. The obvious one is that things sit — a rep waiting on a discount answer for two days has a customer cooling off, and a purchase waiting on approval is a job not starting.
The less obvious one is inconsistency. The same request gets a different answer depending on who was asked, how busy they were, and what mood the week was in. Nobody intends this. It is what happens when the rule lives in a person rather than on paper, and it shows up as customers who have learned that asking twice works.
What the agent does
It gathers everything first. Customer history, payment record, what was quoted, what the margin is on this job, what happened the last three times something like this was asked. The context that used to be a round trip is assembled before anyone is asked anything.
Then it applies your policy to the routine cases. Inside the rule, it approves and records why. Outside the rule, it declines or escalates according to what you decided should happen. The routine majority resolves in seconds instead of days.
For the ones that genuinely need judgment, it does not decide. It hands the person a decision that is ready to be made: here is what is being asked, here is the context, here is what our policy says, here is what we did in similar situations, here is what it costs either way. A recommendation, and the reasoning behind it, and a person who says yes or no in ten seconds because the work has already been done.
Everything it decides, it logs — what was asked, what rule applied, what happened. Which means that for the first time you can look at a quarter of decisions and see the pattern: which customers ask most, which reps discount hardest, which rule is being escalated so often that it is not really a rule.
What changes
Routine decisions stop taking days. The rep gets an answer in the customer's driveway. The purchase order goes out the same morning.
Answers become consistent. The same request gets the same answer on Thursday as on Monday, from anybody, which changes how customers and staff behave toward the process within about a month.
The owner sees only the real calls. Their attention goes to the ten decisions a month that genuinely need them, instead of being spread across a hundred that did not.
And the decisions become visible. The log is frequently the most useful output — most owners have never been able to see how many exceptions their business grants, or to whom.
What it connects to
Your policy, written down. This is the honest part: in most businesses the actual rule is not written anywhere, and the version in the handbook is not the one being applied. Writing down what you really do — including the exceptions you always grant and why — is the substance of the project. It usually takes a couple of conversations, and it is worth doing whether or not anything gets built afterward.
The systems holding the facts — customer history, order and job records, accounting, margin. It can only apply a rule to information it can reach.
A clear escalation path. Who decides what, at what threshold, and who covers when they are away. An agent that escalates into a void has simply relocated the bottleneck.
And an audit trail you can actually review. Every decision, the rule that produced it, and the reasoning. Both because you will want to look at the pattern, and because the first time it gets a call wrong you will need to see exactly why it decided what it decided.