Home / Field guides / AI & Automation
Field guide · AI & AutomationThe Automation Field Guide what to decide before you build
A working document for owners and operators in the GCC. Written to be useful on its own, including to the reader who decides to do all of this without us.
Written to be used.
Some readers will finish this guide, look at their own operation, and decide to build the whole thing themselves. That is a good outcome. A great deal of automation work is genuinely within reach of a capable owner with a free afternoon and a little patience, and we would rather you knew exactly which parts those are than paid anyone to do them on your behalf.
So this is written the way we would brief a new member of our own team. It sets out what the work involves, where it tends to go wrong, and the order we would do it in. The sequence at the end is the real one. Nothing is held back to make the engagement look harder than it is.
You can generate the work. You cannot delegate the outcome.
What you can genuinely do yourself.
- Map your own process, properly
- Automate the obvious plumbing
- Clean your own records
- Drafts you still edit yourself
- A build you could unpick quickly
- First builds away from invoices
- Anything quoting a price
- Data leaving your tenancy
- Systems only one person understands
If your workflows are internal, the cost of a mistake is an apology rather than a refund, and one person can hold the entire picture in their head, then build it yourself. In that situation you do not need us at all, and a retainer would be an expensive way to buy something you could maintain in an afternoon.
Where the general answer stops being useful.
Not because it is wrong. Because it is general, and this is a contested problem against named competitors who were handed the same advice.
“Build me a workflow that sends new website leads to WhatsApp and creates a record in our CRM.”
Correct, complete, and it will work the first time you run it.
What the decision requiresThe build is the small part. The decisions are what happens on the day the CRM returns a success code and writes nothing, whether two enquiries from the same person an hour apart become one record or two, and what the system does when a messaging template is rejected mid-campaign - because a rejected template does not raise an error, it simply drains the queue in silence. Owners tend to discover this when a quiet month turns out to have been a broken one. Design the failure path before the happy path; the happy path takes an afternoon.
“Write me a prompt so our AI agent can answer customer questions about pricing and availability.”
It is a good prompt. Better, honestly, than most that arrive with us.
What the decision requiresPricing is not a prompt problem. It is a question of where the number lives and how stale it is permitted to be: an agent reading a document written in March will quote March's price in perfect grammar and total confidence, and the customer will reasonably hold you to it. The decision is whether the agent may state a price at all, or may only confirm what an authoritative system returns at that moment, and what it says when that system is unreachable. In practice the agents that survive contact with real customers are the ones with no independent knowledge of anything that changes.
“What is the best AI tool for automating our marketing and sales operations?”
Fair, current, and more impartial than most vendor comparisons.
What the decision requiresThe tool matters less than where the automation runs and whose account owns it. Workflows built inside one person's personal connector account, or on a founder's API key, quietly become unmovable: the credentials belong to an individual, the audit trail is thin, and the business cannot answer a straight question about which sub-processor holds its customer data. In this region that question arrives sooner than people expect - a bank, a clinic or a government-adjacent client will ask where data is processed, and the answer has to exist before the automation does. Choose on ownership, exportability and data residency. The feature comparison is out of date by the next quarter anyway.
What a year of doing it alone usually looks like.
- No heartbeat check on the workflowEnquiries collect in a queue nobody opensWeeks of lost enquiries, found by a customer
- Nobody decided which record winsTeam trusts neither and returns to emailRebuilding trust in the records, not the wiring
- Nothing defined the edge of its authorityIt confirms delivery windows and implies discountsA narrower job, not a better prompt
- Built on records nobody cleaned firstOne customer messaged three times, reporting splits themCleaning the records anyway, errors now spread wider
- Built by someone who then leftCredentials sit in a departed inboxEvery small change now looks like a rebuild
If you run it yourself, run it in this order.
- Start hereWrite down the process as performedSteps that only correct earlier steps should be removed, not automated
- Before choosing toolsSettle the records underneathMost later arguments trace back to which system is authoritative
- ThenChoose a low-consequence first processThe first build is to learn how your data behaves
- During the buildDesign the failure path firstThe characteristic failure is silence, so every workflow needs a heartbeat
- Before going liveDecide what may leave unreadPrices, commitments and published output need a name against them
- From then onReview what ran and failedAn automation nobody reviews is a liability accruing quietly
No one can guarantee AI answers — we improve the signals that earn them.
Six workstreams, drawn as one machine.
Automation fails in a particular way: it works perfectly on the day it is demonstrated.
What the PDF adds to this.
- —The six workstreams in full — what each one actually contains, not just what it is called.
- —One line item opened into twelve decisions — the part that decides the result.
- —The shape of a mandate — scope, cadence and what the work honestly asks of you.
- —The written argument behind every diagram on this page, in full.
Run it yourself.
Or hand it to someone whose name is on the result.
The tasks became cheap; who answers for the number at the end of the quarter did not change. We will tell you honestly if you are not a fit.
Request a Growth Audit