Policy first. Then the automation.
Your people are already putting client documents into ChatGPT, Claude or Gemini, and nothing in writing says what may go in or who answers when a customer asks. So the rules get written down first: a plain-English policy and a register of every AI tool in use. Then the hours come back.
Book the free assessmentYou keep the AI Use Register whether or not you hire us.
What is already happening on a Tuesday afternoon
Someone in the office is behind, and a document needs reading. They paste it into a chatbot because it is faster than doing it by hand. Nobody told them not to. There is no rule to break, because there is no rule.
Nobody is being careless. The tools arrived and the paperwork did not. The exposure is your client's data, your staff member's judgment, and your name on the contract with the customer who finds out.
Then the hours
The counting exercise still matters. It just stopped being the first thing we ask. When you want a number: how many hours a week go into work the system should have done. Four boxes, two minutes, and a report you keep.
Your week, counted
How often does each of these happen, and how long does one cost?
Time that only exists because of the system
Nothing to install, and nothing leaves your machine until you send it.
Why we ask you to count instead of guessing
A wage multiplied by an assumed number of hours is a guess dressed as a calculation, and every owner can feel it. Counting is different: how many invoices a week, how long one takes. Those you know. The arithmetic is printed under the answer so you can check it against your own week — and if your count is half of ours, the number halves with it.
It also tells us where to start. The biggest row on that list is usually where we begin, and it is often not the thing anybody expected — us included.
How it works
Four kinds of work that exist only because of the system
Not the work you sell. Not the picking, the packing, the driving or the machine running. This is the overhead wrapped around it — and every hour of it is recoverable if a system can do the step and a person can approve it.
Rework after a mistake
A transposed digit, a wrong part, a figure keyed into the wrong field. Someone finds it, someone fixes it, and the job gets done twice. The second time is pure loss.
The numbers typed off paper
Hard-copy invoice numbers, quantities, dates, a total that never got carried over. A person reading a page and typing it into a system, and the mistakes that follow from it.
The evidence hunt
Where is the spec, the ticket, the approval, the signed sheet? Time spent assembling the documentation to answer a go/no-go that a system could have answered in a glance.
Where did it get to?
A call to the shop floor, an email to the customer, a text to the driver. Nobody can see the status, so somebody has to ask — several times, to several people.
If the work does not happen inside a system, we leave it out. That is on purpose. None of this touches your labour, your crew or your product. It is the computer work around it that comes off your people.
Where the hours go instead
That figure is capacity you are already paying for. Once the system does the keying and the digging, the time goes to work that needs a person in it.
More gets finished
The quotes that waited until Thursday, the follow-up calls nobody had time for, the service work at the bottom of the list. Same people, same hours, more of the work that earns.
Without a hire
The next slice of volume lands on admin hours already on your payroll, instead of a new salary. A full-time hire at $30 an hour loaded is about $62,400 a year.
The rework stops
The row for corrections is the one that changes fastest. The job gets done once, the credit note never gets written, and the customer never finds out there was a problem.
To be plain: nobody loses a job over this. The hours go back into the business, and that is the only version of this that works in a company your size.
What we would actually do about it
Find the one thing
For the owner who knows something is broken but not where. We sit down, find the biggest time leak, and fix one thing so you can see it work.
Build it and hand it over
We find it, build the tool, train your team on it, and make sure you own it — no dependency on us to keep it running.
Keep it working
As the business changes, the tools change with it. We add, refine and retrain as new work shows up.
Under ESC hd
ESC hd, LLC is the firm: it signs the agreement, stays responsible for the work and holds the relationship afterwards. The work itself comes from the practice side: one for now, a second only when there is a reason for one. You do not have to start with a build.
designedconcepts.ai a DBA of ESC hd, LLC
Training and enablement. If your team already works in Copilot, Gemini, ChatGPT or Claude, you do not need a build or an assessment to get help — the training is the whole engagement, and it starts from the tools you already pay for.
Behind a build, it is the same practice: it trains the team that will run the fix, and tells you plainly when to leave something alone. It is also who runs the assessment on this page.
Training on the tools you already use →The assessment
The assessment is free. How the policy work runs →
About ESC hd
ESC hd is a small firm in Mesa, Arizona, built on more than twenty-five years managing technology and financial-institution programs — the kind of work where a policy, an audit trail and a signature were not optional. The policy practice is new and deliberately small: the same person writes the document, trains the people who follow it, and answers the phone when it needs changing.
We have not published a wall of client logos, because the businesses we work with did not sign up to be a case study — and we would rather show you the arithmetic than someone else's results. The numbers on this page are your own, counted from what you tell us, with the working printed next to them so you can check it.
We do not replace what already works. If your system does its job, we leave it alone and take the manual work off the people around it.