Executive summary
A useful automation audit starts by locating repeated work, channel chaos, missing ownership, slow follow-up, and unclear approval paths. These 20 questions help Saudi SMEs pick the right first AI workflow before buying tools or building agents.
Most Saudi SMEs do not need to start with an AI strategy workshop. They need to find the repeated work that keeps leaking time every week.
That is what an automation audit is for.
The goal is not to automate everything. The goal is to find the first workflow where AI can reduce chasing, speed up response, improve consistency, or protect the founder's attention.
These are the 20 questions I ask first.
1. Where does work enter the business?
List the real channels:
- WhatsApp.
- Calls.
- Instagram DMs.
- Email.
- Website forms.
- Walk-ins.
- CRM.
- Spreadsheets.
The channel map usually reveals the first automation opportunity.
2. Which channel creates the most lost opportunities?
Not all channels matter equally. Find the one where leads, support requests, or approvals get buried.
3. What does the founder still chase manually?
If the founder has to ask "where are we on this?" every day, there is likely an automation opportunity.
4. What repeats every week?
Repeated work is the easiest to automate safely.
Look for reporting, follow-up, summaries, intake, routing, reconciliation, reminders, and status checks.
5. What gets copied from one place to another?
Copy-paste work is usually a sign that systems are not connected.
6. Which request types need the same first response?
If the team answers the same question repeatedly, AI can draft or suggest responses from approved templates.
7. What information is usually missing?
Good automation often starts by asking for missing information before a human gets involved.
8. Who owns each request type?
If ownership is unclear, automation will only move confusion faster.
9. Which approvals slow the business down?
Map who approves discounts, refunds, purchases, content, offers, hiring steps, and customer exceptions.
10. What should never be automated without review?
Write this down early. It protects trust.
11. What data is sensitive?
Customer data, health information, payments, employee records, and private documents need tighter handling.
12. Where does Arabic tone matter?
Customer-facing automation needs Arabic that fits the relationship. Internal summaries can be more direct.
13. Where does WhatsApp need structure?
If WhatsApp is where work happens, automation should organize it, not pretend it does not exist.
14. Which metric proves the workflow improved?
Pick one:
- Response time.
- Manual hours saved.
- Missed follow-ups.
- Error rate.
- Time to approval.
- No-show rate.
- Lead conversion step.
15. What can AI draft but not send?
Drafting is often the safest first automation layer.
16. What can AI summarize for managers?
Daily or weekly summaries can remove a lot of status chasing.
17. What alerts are actually useful?
Do not automate noise. Only alert when action is needed.
18. What system should remain the source of truth?
CRM, ERP, spreadsheet, email, or database. Decide where the structured record belongs.
19. What would make the team resist this?
Fear of monitoring, extra work, unclear authority, bad Arabic, or a tool that exposes old messes. Address this before launch.
20. What is the smallest useful pilot?
Choose one workflow, one owner, one metric, and one week of real usage.
How to score the answers
For each workflow candidate, score 1-5:
- Frequency.
- Time cost.
- Revenue impact.
- Risk reduction.
- Data availability.
- Ease of human review.
Start with the workflow that scores high on value and is easy to review.
What a good first automation looks like
A strong first project usually has these traits:
- It repeats weekly.
- The inputs are available.
- The decision boundary is clear.
- Human approval is simple.
- Arabic/WhatsApp context is understood.
- The result can be measured within 14 days.
That is enough to start.
The mistake to avoid
Do not start with the biggest, most sensitive, most political workflow.
Start with the workflow that proves the system can help without threatening the team. Trust compounds from there.
Download the checklist
Use the working version here: Saudi SME Automation Audit Checklist. It turns the questions into a scorecard you can use before requesting a build.