Skip to content
Jamie Gray AI systems you can explain Book an AI audit
← All services
Service 02 · Fix it

AI Automation Build

One working system, built to a fixed scope: enquiry funnels, AI-written replies, and links between Gmail, Google Sheets and the tools you already use. Delivered with a guide so you can run it.

At a glance
Start here if
Someone on your team repeats the same task every day.
You receive
A live system and a handover guide.
Price
[PRICE TBC]
Time
[TIMELINE TBC]
Where
Remote
You're in the right place if…

Three signs a build will pay off.

Your team answers the same enquiries, bookings and follow-ups by hand, every day.
Leads arrive by email, forms and messages, and some get lost on the way.
A spreadsheet is doing the job of a system, and one person understands it.
What you get

A system that runs, and the records to prove how.

01
A working system, fixed scope
Agreed in writing before I start. Changes are quoted separately, so there are no surprises.
02
Your tools, connected
Gmail, Google Sheets and the apps you use, linked with tools such as Make.com. [CONFIRM: tool list]
03
AI-written replies in your tone
Drafted from your own examples, with an option for a person to approve before sending.
04
A record of what it did
A log of what the system sent and decided, so you can explain it later.
05
Tested on your real cases
I run your own examples through it before going live and show you the results.
06
A handover guide
Plain-language instructions so your team can operate it without me.
Examples

What a build can look like.

Coaching business
An assessment funnel, personalised checkout and daily AI check-ins, linked to Gmail and Google Sheets. This is the kind of build I have running today.
Clinic admin
Appointment reminders and enquiry sorting. Admin only, never clinical decisions, and patients are told when they're talking to AI.
Tech startup
Inbound requests sorted into a shared sheet, with draft replies for the team to approve.
The coaching build is real. The clinic and startup scenarios are illustrative, not client results.
How it works

Four steps from idea to handover.

1
Agree the scope
What it does, what it doesn't, and what done looks like.
2
Build in a test copy
Nothing touches your live customers yet.
3
Test with real cases
You review the results and I fix what's off.
4
Go live and hand over
Accounts in your name, plus the guide.
What this isn't

Honest boundaries.

Not open-ended. Scope is fixed, and extra changes are quoted before I do them.
Not for clinical or high-stakes decisions about people. Admin tasks only.
Not legal advice. Where customers deal with AI-written messages, I recommend telling them.
Questions

Common questions.

Who owns the system?
You do. Accounts are set up in your name.
What if something breaks later?
The handover guide covers common fixes. For anything else, see Handover & Support.
Do I need an audit first?
Not always. If you already know the task, we can scope the build directly.
Can you build for healthcare?
Admin tasks only, never clinical decisions. [CONFIRM: local partner for Arabic-speaking clinics]
← 01 · AI Audit All services 03 · Policy & Documentation Pack →

Have a repeat task in mind? Tell me what it is.

Discuss a build