Business Automation Consultant, Kuwait

Automating for a group, not a single company

When each company in a group automates on its own, the result is a patchwork: one company has an approval workflow in its ERP, another uses a spreadsheet with email reminders, a third has nothing. Group finance then spends its time translating between them.

I start at group level. With the heads of finance, procurement, HR and property or sales operations, I list the routines that every company performs and compare how each company does them. Routines that are frequent, rule-based and broadly similar across companies become group candidates. Those that are unique to one company are assessed separately.

For each candidate, a group rule sheet is written: trigger, conditions, actions, exceptions and owner. Where a company has a real reason to differ, for example a contracting company whose purchase approvals depend on project budgets, the variation is written into the same sheet rather than becoming a separate build. One company is chosen as the pilot. Once the workflow runs well there, it is extended to the others with only their variations configured.

Two conditions come before any build. The process must be agreed, and the approval levels behind it must be written down. If neither exists, automation would only encode today's habits, so the Kuwait process consulting work comes first. The same applies when companies in the group use different systems: the workflow design must suit each one, or wait until they share a platform.

Approvals that respect the owners' time

Owners in Kuwaiti groups are often the final approvers for a wide range of requests. Automating approvals naively, by sending every request to their phone, can make things worse: the owner receives a constant stream of notifications and the important ones are lost among routine ones.

A better design uses the group's approval matrix as rules. Requests within a manager's agreed limit are routed to that manager and approved without reaching the owner. Requests above it, or outside budget, or involving a new supplier, are escalated. For the owner, those escalations can arrive as a short daily digest with the essential facts for each request, rather than as individual messages through the day. Urgent items can be marked as such by the group finance head, who acts as a filter.

The workflow also records every approval, delegation and rejection, which gives owners something they often lack: a clear view of what was approved in their name and by whom. When an owner is traveling, a named delegate can be set for a defined period, and the digest continues to inform the owner without requiring action.

These rules are written with the owners, not for them. Some owners prefer to see more; others want only the exceptions. Both are valid, and the configuration follows their decision. Mobile approval apps can support this, as described on the Zoho Creator in Kuwait page, but the rules come before the app.

A group close tracker and the monthly reporting pack

Group reporting in Kuwait often depends on a single person in group finance collecting files from every company, checking them, copying figures into a consolidation workbook and chasing whoever is late. Automation can take most of the collecting and chasing off that person's desk.

A close tracker lists the month-end tasks for each company: sales and purchase cut-off, bank reconciliations, stock adjustments, intercompany confirmations and the trial balance submission. Company accountants mark tasks as done. Reminders go out automatically as deadlines approach, and the group finance head sees at a glance which companies are complete and which are behind.

Once a company's figures are submitted, automated checks run before they enter the group pack:

• the trial balance balances and matches the prior closing position;
• intercompany balances agree with the counterparty company's figures, with differences listed;
• mandatory accounts and cost centers are not blank;
• amounts carry the dinar's full precision, so totals do not drift.

The pack is then assembled from the checked figures into a standard format for the owners, with commentary added by finance. Where the companies already share an ERP, much of this comes from the system directly; where they do not, a low-code workflow collects standard files. Either way, the review of the numbers, and the decisions based on them, stay with people. The management dashboards page covers the reporting side in more depth.

Rent, checks and renewals in property and trading companies

Many Kuwaiti groups include a property company and one or more trading companies, and both handle checks. Tenants may pay rent by check, sometimes several at the start of a lease. Business customers of trading companies may pay with post-dated checks. Tracking them by hand in a register is common and error-prone.

Once checks are recorded when received, a scheduled workflow can list those due for deposit each week, create a deposit task for the responsible accountant, and open a follow-up task when a check is returned. For property companies, the same approach supports rent and installment notices before due dates, lease expiry reminders to the leasing team, and a renewal task assigned in good time. The Arabic and English wording of tenant and customer messages is approved by your own leasing and credit staff.

Renewals of a different kind run across the whole group. Company licenses, authorized signatory documents, employee residencies and work permits all expire on their own schedules. A renewal alert workflow reads expiry dates from one record per company and employee and notifies the group PRO desk in advance, identifying which company and which person each alert concerns. It does not submit anything; it makes sure nothing is forgotten.

No money moves automatically in any of these workflows. Deposits, refunds and decisions on returned checks remain with finance and, where needed, your lawyer. The automation only makes the next action visible and assigned.

AI with review, data care, limits and roles

AI can help busy managers in a group by summarizing long Arabic or English letters, contracts and email threads into short English notes, sorting a shared inbox, or drafting routine replies. Each output is checked by a person against the original before anyone acts on it, and Arabic source documents are reviewed by your own staff. The engagement runs in English.

Data needs care. Kuwait has data protection rules, and some sectors carry their own requirements. For every AI step I prepare a short data note: the document types involved, the outside service that would read them, the region where it runs. The group's legal counsel signs that note off, or rejects it, before the step is switched on. Employee identity documents, salary details and family members' personal information are kept out of AI steps.

Some decisions should not be automated at all: approving payments above delegated limits, decisions about family shareholders or board matters, credit decisions for major customers, and the final wording of letters to ministries or authorities.

On roles, I choose the automations with the group, write the rule sheets, and build the workflows inside the ERP or CRM, or in tools such as Zoho Flow, Deluge, Odoo automated actions, n8n, Make or Zapier. Bespoke code is written by the group's developers or partner and tested by me before launch. Each workflow has an owner in each company, a runbook and a failure alert. Results are judged in plain terms, such as owners receiving fewer routine requests and the group pack arriving on time. Delivery is remote; visits need a separate arrangement. See the Kuwait overview.