AI Proposes, You Approve: How Back-Office Agents Should Work

Most trade owners I talk to don't have a software problem. They have an owner-as-switchboard problem.

A customer asks a question by email. A homeowner wants to move Thursday. An estimate needs a follow-up. A sub needs a window. All of it runs through you, or through the one person in your office who's also answering the phone.

That's not hustle. That's unpaid office work eating your billable hours.

Why another app didn't fix it

For years, the answer was another login. A scheduling tool. A CRM for contractors. A dashboard.

Then the crew stayed in group texts, you stayed on the phone, and the tool only knew what somebody remembered to type in. A dashboard shows you the work. It doesn't do any of it.

What an agent actually does

An agent is different. It takes one defined slice of the office work and moves it forward until a person needs to decide.

Here's the pattern I build every agent around:

1. Something comes in. A customer request, a schedule change, a quote with no reply.
2. The agent prepares the next step. It pulls the job details and drafts the reply or the update.
3. It checks the rules. What it's allowed to touch, and what it isn't.
4. A person approves. You or your office manager reads it and says yes, edits it, or says no.
5. The approved action happens. The reply goes out. The calendar updates.
6. There's a record. You can see what came in, what was proposed, and who approved it.

AI proposes. People approve. That's the whole idea.

What I'd automate first

• Estimate follow-ups that die in the inbox
• Confirmation checks, like "are we still on for Thursday?"
• Status chasing that shouldn't need you
• Sorting incoming requests so the right person gets the decision, not the whole thread

What I won't automate

• Price or scope changes without a person
• Refunds, promises, or anything that commits your money
• Anything that could leave a crew or a customer stranded with no one to call
• Pretending to be you. The agent helps you. It doesn't fake being the owner.

Trade businesses don't have spare trust. One bad message sent in your name and that customer is gone. So the agent starts with boring, repeat work, and it earns more only after you've watched it do the job well.

Why it starts small

The first agent should have one narrow job. One inbox, one type of request, one person who owns it. It gets more responsibility only after you've reviewed its work and decided it's ready. That's slower than flipping on every feature at once. It's also how you avoid a mess you have to clean up later.

What approval looks like day to day

It shouldn't be a chore. A good setup puts the drafts in one place, with the job details right next to each one. You read, tap approve or fix it, and move on. A few minutes in the morning and a few at the end of the day. If approving takes longer than doing the work yourself, the setup is wrong and needs to change.

Where Dreki fits

Dreki Solutions is a veteran-owned AI and agentic software company in Michigan. I build agents for customer response, intake and scheduling, and the handoffs between office and field. Each one works with the tools you already use where it can, so you don't start over.

Next step

Pick the one office job you'd hand off tomorrow if you could. Then book a 30-minute call, call (517) 215-7573, or email brett@dreki-solutions.com. We'll map that one job and decide what stays with you.