Automate the process, not the mess
Approvals live in WhatsApp, records live in Excel, and reconciling the two is somebody's whole job.
What you get
- The current process timed end to end, including the waiting
- Steps removed before steps are automated
- Approvals and audit trails inside the system, not in chat threads
- The hours saved, measured against the baseline we recorded first
The approval is a voice note and the record is a photograph of a signature
A purchase is approved in a WhatsApp group. The buyer types the order into the system from a photograph of a signed sheet. The stores keeper writes the delivery on a pad and somebody enters it two days later. On Thursday a person whose job title says something else spends the day reconciling a spreadsheet against the system, finds four differences, and resolves them by deciding which one looks more likely.
Every one of those steps was invented by a competent person working around a system that did not fit. Together they mean there is no audit trail, no cycle time anybody can quote, and no way to find out that a request has been sitting with one manager for nine days.
When the person who does the Thursday reconciliation resigns, the company discovers how much of its process was living in one head.
Fix the process before you automate it
We time the current process end to end first, including the waiting. That distinction is the whole job. In most approval chains the work takes minutes and the elapsed time is days, and nearly all of the difference is a document sitting in an inbox or a decision waiting for somebody who is travelling. Automating the minutes and leaving the days is the usual outcome of an automation project, and nobody in the business can feel the improvement.
Then steps get removed. Three signatures on a purchase below a threshold nobody has revisited in eight years is not a control, it is a habit. Automating it makes the habit permanent and gives it an audit trail.
Expect a meaningful share of what we find to be deleted rather than automated. That work is cheaper than building anything, it pays back fastest, and it is the part of the engagement that reduces our own scope.
Business process automation belongs inside the systems you already pay for
Before recommending a new tool we look at what your existing software can already do. Approval rules, escalation, scheduled actions, portal access for a customer or a subcontractor, document generation and notifications are standard features in most ERPs, and they are switched off in most installations because nobody was asked to configure them.
Where a connector between two systems is genuinely needed, we will use one. What we will not do is add a fourth product to join up three you are not using properly. That arrangement works until the person who built the automations leaves, and then nobody can explain why an invoice is being emailed twice.
Approvals and audit trails end up on the document they belong to, with a name and a timestamp. That is a compliance improvement as much as an efficiency one, and it is usually the part your auditor notices first.
Where this pays back, and where it does not
Volume and repetition. A process that runs hundreds of times a month, crosses three departments and produces a document somebody else has to check: requisition to purchase order, delivery to invoice, timesheet to payroll, customer onboarding, supplier invoice matching, subcontractor payment applications. Operations across the UAE and the GCC where the same work is done in two languages and both versions have to reconcile.
It does not pay back on a process that runs four times a month and takes twenty minutes. The build will outlive the saving and you will have added something to maintain. Do that one by hand and spend the money on the process that runs four hundred times.
It also does not work in a company unwilling to change how a decision gets made. If the general manager intends to keep approving everything personally by phone, no workflow will hold — the exception gets re-entered afterwards and the system ends up describing a process that does not happen.
How it is priced and how the saving is proved
The baseline is recorded before anything is built: how long the process takes today, how many people touch it, how many corrections it generates in a month. Without that number the saving after go-live is a claim. With it, it is a comparison, and it is yours to check rather than ours to assert.
Cost is determined by how many processes are in scope, how many systems each one crosses, whether the process is agreed before we start, and whether approvals and documents have to stand up to an audit or a tax authority. A fixed scope at a fixed price, per process, after a short diagnosis that says which ones are worth doing and in what order.
That order matters more than the tooling. Most companies have two or three processes that account for the bulk of the manual effort, and a long tail that should be left exactly as it is.
How the engagement runs
- 01
Diagnose
Two weeks inside your operation. We map how the work is actually done, where two systems disagree, and what each gap costs you in a month.
- 02
Architect
A target design tied to operating decisions: which system holds which truth, who owns it, and what has to be true before go-live.
- 03
Implement
Delivery in phases you can stop after. We train your team to run it, because a system that only we can operate is a system you do not own.
- 04
Govern
The part everyone skips. Ownership, review cadence and metrics, so the system does not quietly decay back into chaos.
Questions
What people ask before they start this work
How is process automation priced?
Per process, as a fixed scope at a fixed price, after a short diagnosis that establishes which processes are worth automating and in what order. The drivers are how many systems each process crosses, whether the process is agreed before work starts, and whether the approvals have to hold up to an audit. The diagnosis often removes processes from the scope, which lowers the price.
How long does it take to see a change?
The measurement of the current process takes days, not months, and it is usually the point at which people start removing steps on their own. Build time then depends on how many systems a process touches and whether the decisions behind it are settled. We deliver one process at a time so the first one is in real use while the second is still being scoped.
Who maintains the automations afterwards?
Your team, and it is set up so that is possible. Where the automation lives inside your ERP as configured approval rules and actions, the people who administer the system can change a threshold or an approver without calling us. Anything written as code is documented and handed over. If every change to an approval limit requires a consultant, the automation has replaced one bottleneck with another.
Will this mean we need fewer people?
Sometimes, and we will not pretend otherwise. More often the same people stop spending Thursdays reconciling and start doing work that was being deferred. Where a role genuinely shrinks, it is better to know before the build than after, and we say so during the diagnosis so you can plan it rather than discover it. Automation sold on headcount cuts alone usually under-delivers on both.
We do not want to replace our ERP. Can you still help?
That is the usual case, and it is the cheaper one. Most of what we switch on already exists in the system you own and was never configured. Replacing an ERP to get an approval workflow is the most expensive way to buy one. If the diagnosis finds your existing system can carry the process, the recommendation will be to configure it rather than to change it.
Do you use tools like Zapier, Make or Power Automate?
Where they genuinely fit, yes. The preference is to keep the logic inside the system that owns the record, because an approval that lives in a third-party tool is invisible to anyone auditing the document. External automation tools are a reasonable choice for connecting systems that will never be merged, and a poor one for holding a control that a regulator or an auditor may ask about.
Can we keep approving things on WhatsApp?
You can keep the notification there. What cannot stay there is the record. Sending an alert to a manager's phone is fine, and often the only way a busy approver responds the same day. The approval itself has to land on the document, with a name, a timestamp and the version that was approved, or you are back to reconstructing a decision from a chat history two years later.
Process Automation
Start with a diagnosis
Tell us the symptom in one line. We will come back with what we would look at first and what it would take.
Monday to Friday, 9:00 AM – 6:00 PM (GST)
Prefer we call you?
Leave your WhatsApp number and we will reach out.