Walk through an owner's day in a trading house in Karachi or a distributor in Sharjah and much of it is moving the same information from one place to another. An order read off WhatsApp and typed in. A ledger scanned for who to chase. A sales figure collected each evening. None of it is skilled work, and all of it goes wrong when the person doing it is busy. Our plan for automating a company covers the order to do things in. This guide is the list: the seven jobs, what replaces each one, and what to watch.
Rule or AI: the two kinds of automation
A rule is a fixed instruction inside your ERP or CRM: when an invoice is thirty days old, send a reminder; when stock falls below the reorder level, add the item to a purchase list. Rules are cheap, predictable and never need checking. AI reading takes something unstructured, a photo of a bill or a message that says "wahi pichle wala, do carton zyada", and turns it into fields a system can use. It is useful, and it is sometimes wrong, so a person approves what it produces. The test for which one you need is whether the input is already structured. If it is a form, a record or a number, a rule will do. If it is a document or free text, you need reading.
The seven jobs
| Job | By hand today | What automates it | The catch |
|---|---|---|---|
| Retyping orders from WhatsApp | A salesman reads the chat and types the order into the system or a register | AI reading turns the message into a draft order; or a salesman app or ordering link so the order arrives structured in the first place | Free text is messy; "the same as last time" still needs a person to confirm |
| Chasing payments | The accountant scans the ledger and phones or messages each party | An ERP rule: ageing report plus a reminder on WhatsApp or SMS at set days | Reminders annoy good customers if receipts are entered late and the ledger is wrong |
| Daily sales report to the owner | Someone compiles it from the POS or register each evening | An ERP rule: a scheduled report sent to the owner's phone at closing time | Only true if every sale is entered; a report from half the data misleads |
| Stock reorder list | The storekeeper walks the godown and writes down what looks low | An ERP rule: a reorder level per item and godown, and a suggested purchase order | Levels must be set and revised; seasonal items need a different level each season |
| Salary calculation | Attendance register, Excel and a calculator at month end | A payroll module: attendance becomes a salary sheet with advances and deductions | The rules for late marks, overtime and advances must be written down first |
| Invoice data entry | A supplier bill is retyped line by line | AI reading creates a draft bill matched to the purchase order | Handwritten bills, stamps and new suppliers need a person; every draft is approved |
| Lead follow-up | Enquiries in a notebook or a chat, followed up when remembered | A CRM rule: every lead has an owner, a next action and a reminder | Only works if every enquiry is entered, so the CRM must sit where the chats are |
The two that need AI
Orders written in a chat and supplier invoices arriving as documents are the only two in the list that start unstructured. For orders there is a cheaper route first: give the customer or the salesman a way to send the order as an order, through an app or a link, and the reading problem disappears. Where the customer will only ever send a WhatsApp message, reading it into a draft is the next best thing. For invoices, our guide to AI document processing explains how the reading, matching and approval work, and where photos and handwriting let it down.
The five that only need a rule
Payment reminders, the daily report, the reorder list, salary and lead follow-up are all rules on records that an ERP or a CRM already holds. No reading, no guessing, nothing to approve. They are also the five that most businesses have been sold "AI" for when a report schedule would have done. Siratim, a bottled water company, keeps its customers, orders and deliveries in one system; any report or reminder built on top reads those same records rather than anything clever.
The catch that runs through all seven
Every row in the table has the same condition hidden in it: the records must be complete. A reminder rule on a ledger with late receipts chases people who have paid. A reorder list from a godown whose issues are not entered orders stock you already hold. A sales report from a POS that skips cash sales tells the owner a comfortable lie. Automation does not fix a process that people are not following; it makes the gaps faster and more confident. So before any of the seven, the question is whether every order, receipt, issue and enquiry is entered, by the person who did it, on the day.
Which to do first
Not the one that sounds most modern. The one that is typed twice today, by two people, with the two copies disagreeing at month end. For a distributor that is usually the order from the salesman; for a trader it is the supplier bill; for a services firm it is the lead that nobody followed up. Pick that one, make its records complete, add the rule or the reading, and leave the other six alone until it has settled. If you would like to walk through your own list, book a demo and we will mark each job as rule, reading or not worth it yet.
Questions people ask
Which business processes should I automate first?
The one that is entered twice today, by two different people, with the copies disagreeing at month end. For most trading businesses that is the order or the supplier bill. Make its records complete first, then automate it, then move to the next.
Do I need AI to automate these jobs?
For five of the seven, no: payment reminders, reports, reorder lists, salary and lead follow-up are rules inside an ERP or CRM. AI reading is only needed where the input is a document or a free-text message, such as a WhatsApp order or a supplier invoice.
Can WhatsApp orders be entered automatically?
Partly. AI reading can turn a clear message into a draft order for a person to confirm. The better route is to give the customer or the salesman an app or a link so the order arrives as an order, and the reading problem never exists.
Can payment reminders go out on their own?
Yes, as a rule in the ERP: an invoice past an agreed number of days triggers a WhatsApp or SMS reminder. It only works if receipts are entered promptly, otherwise the system reminds customers who have already paid.
What stops automation from working?
Incomplete records. If sales, receipts, stock issues or enquiries are not entered on the day, every rule and every report built on them is wrong. Fix the entry habit before adding automation on top.
