It is taking the steps that need no judgement out of people's hands: checking entries, chasing what's missing, raising problems and drafting the routine replies. 110 Analytics builds it on the systems a business already runs, with every automation keeping a ledger of each run and the time it gave back, while people keep every decision.
Where the hours go
In a growing business, the work around the systems tends to sound like this.
- Every Friday someone goes through the overdue invoices and writes the reminders one by one.
- Orders go in late or half filled in, and the gaps surface at month end.
- A supplier's bank details changed, and it was spotted by chance before the payment run.
- The same figures are copied from three systems into a spreadsheet before every meeting.
- Whose job is it to reply to customer reviews?
- How many hours does the routine take each week, and could anyone say?
Why the routine costs more than it looks
None of these steps needs judgement, and each one takes a few minutes. Together they add up, spread across people who were hired for something else.
They are also where mistakes creep in. A reminder goes to a customer who paid yesterday, a half-filled order is invoiced at the wrong price, a changed bank detail goes unnoticed until the money has left.
And because the work is spread thin, it is rarely measured. So it costs twice: in the hours spent, and in the decisions that wait for them.
What gets automated
The steps between your systems that need no judgement. Each one is set up with your team and logged as it runs.
Checking
Each night's new entries are tested against the rules agreed with your team: a missing customer code, an order with no delivery address, a possible duplicate invoice. Problems are flagged the next morning, not at month end.
Chasing
When an invoice passes its due date, a reminder is drafted in the right tone for that customer and held until the credit controller approves it. Missing details are asked for from the person who owns them.
Watching
Rules raise the flag, not luck: an order stuck at one stage, a margin under plan, a supplier's bank details changed before a payment run. Each arrives with the next step beside it.
Drafting
Reorder proposals when stock runs low, replies to customer reviews and other routine answers, drafted on a trigger and queued for a person to approve.
Reporting
The figures load overnight, and the monthly pack builds itself and lands in inboxes. Reporting automation covers this part in detail.
Where AI fits in automation
Most of the steps above start from rules agreed with your team: an invoice is overdue, a field is empty, a figure crosses a line.
AI works alongside them: it checks every entry against those rules, drafts where a fixed template would read badly and answers questions from your own data, not the internet. That is AI on your own data, put to work on the routine.
Whatever AI drafts, a person approves before it goes out.
Both run on the same foundation as the 110 Command Centre: the systems you already run, connected into one warehouse in your own cloud account, with each number defined once.
The same week, by hand and automated
The work is the same. What changes is who does it, and when it is noticed.
| By hand | Automated | |
|---|---|---|
| Overdue invoices | Chased when someone has the time, one email at a time | A reminder drafted when the invoice passes its due date, approved by the credit controller |
| Entries that went in wrong | Found at month end, if at all | Flagged the next morning to the person who entered them |
| Supplier bank details | Checked if someone happens to notice | Raised by a rule before the payment run |
| Low stock | Spotted on the shelf | A reorder proposal drafted for approval |
| The monthly pack | Exported, pasted and assembled by hand | Built overnight and delivered on its own |
| Time spent | Unknown, because nobody counts it | Logged for each automation, so the saving is counted |
A wholesaler's Friday, before and after
A Maltese wholesaler sells to trade customers on account, buys from suppliers abroad, and keeps its accounts, orders and stock in separate systems with a spreadsheet or two in between. The credit controller also puts together the monthly pack.
- Friday afternoons go on writing reminders for overdue accounts, one by one.
- Orders missing a delivery address or a price are found when the invoice comes back.
- A change to a supplier's bank details is checked only if someone happens to notice it.
- The monthly pack takes the first days of every month.
- Reminders are drafted as each invoice passes its due date, in the right tone for each customer, and the credit controller approves them in one sitting.
- Orders missing a field are flagged the next morning to whoever entered them.
- Any change to a supplier's bank details is raised before the payment run, with the next step beside it.
- The pack builds overnight once the month's figures are in, and lands in inboxes on its own.
The credit controller still decides who gets chased and how firmly. The ledger shows the time each automation gave back, so the saving is counted, not estimated.
What we agree with your team before anything runs
The rules
What counts as overdue, which fields every order needs, which changes need a second look.
Who owns what
Each flag and each draft goes to a named person, so nothing waits on whoever happens to notice.
What waits for a person
Anything that goes out to a customer or supplier waits for someone to approve it.
From first call to the first automation
- Strategy callThirty minutes with Glen, free of charge. Bring the job that eats the most hours and a list of the systems you run, and you will hear plainly what to connect first.
- Data auditAbout three hours with Glen and the people who do the work. Every source and every step done by hand is mapped, and a quote closes the audit.
- BuildAccess to each agreed system, read-only wherever possible, loads every night, and your team signs off the rules. The first live screen is due three to four weeks after you accept the quote.
- Fractional data teamFrom the second month a senior team runs the loads and the checks, adds a new system when it arrives, and takes on the next job worth automating.
What stays with your people
- Decisions. The system flags and drafts; people decide.
- Anything that goes out to a customer or supplier without a person approving it first.
- Work that needs judgement. If a step needs weighing up, it stays with the person paid to weigh it.
- The systems you run. We read them; we do not ask you to change them, and they are never written to.
- Moving entries from one system into another. Connecting your systems to each other stays with whoever supports them.
Glen Sultana founded 110 Analytics after a career built where the numbers move daily. Our people have run analytics for tier-one companies, S&P 500 firms and high-growth technology businesses. Glen is the person on the first call, and he runs every data audit himself.
- Built in your environment, under your account
- Every connection approved by you first
- Based in Malta
Straight answers
Do we need new systems to automate?
No. The automation runs on the systems you already have, connected into one warehouse. We read them; we do not ask you to change them.
Will anything go to our customers without us seeing it?
No. Reminders, replies and proposals are drafted and queued for a person to approve. The system flags and drafts; people decide.
How is this different from reporting automation?
Our reporting automation takes the monthly pack out of people's hands: loaded overnight, agreed once, delivered on its own. Business automation goes wider, to the checking, chasing and drafting around your systems. Both run on the same foundation.
What is AI automation?
Automation with an AI step in it. Rules handle the predictable steps; AI drafts where a fixed template would read badly, checks what goes in and answers questions from your own figures.
How do we know it is saving time?
Each automation keeps a ledger of every run: the trigger, the action and the time it gave back, so the saving is counted, not estimated.
Where should we start?
With the step that takes the most hours and needs the least judgement. The strategy call is where we find it, and the data audit maps the rest.
What does it cost?
What it costs depends on what you need, and that is one of the things the strategy call settles. Our price follows the data audit, as a quote.
Terms on this page
- Business process automation
- Taking the repeatable steps of a process, such as checking, chasing and reporting, out of people's hands, with rules and AI doing them on a schedule or a trigger.
- AI automation
- Automation with an AI step in it, such as drafting a reminder in the right tone for each customer, where a fixed template would read badly.
- Trigger
- The event that starts an automation: an invoice passing its due date, a field left empty, a figure crossing a line.
- Ledger
- The record each automation keeps of what triggered it, what it did and the time it gave back.