Approvals first: hand work to AI without losing control

01The worry is reasonable

When owners hesitate about AI, it's rarely the technology itself that worries them. It's a message going to the wrong customer, a quote with the wrong price, or someone's details ending up somewhere they shouldn't.

Those are reasonable worries. They're also the reason most small businesses never get past experimenting. The answer isn't to trust the software more. It's to set things up so that trust is earned step by step, on evidence you can see.

02Write three lists: alone, ask first, never

Before an agent does anything, decide what it's allowed to do. We write it down in three lists, as part of your Business Map.

Alongside the lists, write down how you talk to customers and the things you never say or promise. That's what keeps drafts sounding like you rather than like software.

03Every action is logged

A log is what turns "I think it's working" into "I can see it's working". Every action an agent takes is recorded: what triggered it, what it did, what it was waiting for, and who approved it.

23:47:02  enquiry.received   web form · "Kitchen refit, 3-bed semi"
23:47:04  map.checked        service ✓  area ✓  price list ✓
23:47:19  reply.drafted      3 questions · 2 survey slots
23:47:19  approval.needed    customer-facing → owner
07:12:40  approved           owner · 1 tap
07:12:41  reply.sent         follow-up set for Friday

Each week you get a summary of the log: jobs done, hours saved and corrections made. Each month it feeds a short report on what the agents did and what that was worth to the business.

04Corrections are training

While approvals are on, you'll sometimes edit a draft before it goes out, or reject one entirely. That isn't a failure. It's the most useful information the system gets.

Every edit and rejection is noted against the agent and remembered. If you always soften the opening line, or never mention a particular product, the agent learns that. Over the first few weeks the number of corrections should fall, and the log shows you whether it has.

Every time you edit a draft, your second brain gets a little more like you.

05Reading the weekly log in five minutes

The weekly summary is short by design. Read it with four questions in mind:

1. What did it do on its own, and was any of it surprising?
2. What did it ask me about, and could any of those have been handled alone?
3. What did I correct, and is the same correction coming up more than once?
4. Did anything unusual happen: a complaint, a price question, an unhappy customer?

A correction that keeps coming back usually means the Map needs updating, not that you need to keep editing. Unusual events are exactly where you want a person looking, which is why they're flagged rather than handled quietly.

06Loosen it slowly, on evidence

Approvals don't have to stay fully on forever, but they come off one job at a time, and only when the record supports it.

1. Day 14: go live with approvals on.Anything customer-facing or money-related waits for a tap from you.
2. Every month: review the log together.Look at corrections, mistakes caught and time saved.
3. Clean record: routine jobs run on their own.Low-risk work, like confirming a booking, can go out without a tap. You decide which jobs qualify.
4. Money and regulated work keep asking.They stay on approval until there's a long, clean record and you're comfortable changing it.

Trust can also go the other way. If you change your prices, launch a new service, take on new staff or see a run of complaints, switch approvals back on for the jobs affected until the record is clean again. It's a setting, not a promise.

Customer data gets the same care. Personal data is only processed by AI models approved for it, and your Map records which of your tools hold personal data, so nothing is left to guesswork.

07What good looks like after three months

Three months in, a healthy setup looks something like this. Routine replies and booking confirmations go out without you. Anything with a price still asks, and takes a tap from your phone. You read the Monday briefing with a coffee, glance at the weekly log in five minutes, and spend the time you got back on the work only you can do.

None of that needs a leap of faith. It needs approvals on from day one, a log you can read, and someone reviewing it with you every month. That's how every Cogent setup starts.

If you'd like to see how it would work for your business, book the free discovery call. We'll find your top three time-wasters and show you exactly where the approvals would sit.