What we automate
Here is the manual work we remove most often, grouped by the kind of job it is. You do not need all of it. Most businesses recognise two or three and start there.
Usually the biggest single block of manual work, and the one where mistakes cost the most.
Statement in one window, invoices in the other, down the list by eye. A payment arrives under a spouse's name or a company you do not recognise and takes twenty minutes to place.
Import the statement and payments match themselves. Duplicates never post twice. The few that are genuinely unclear are flagged, and those are the only ones you touch.
A customer calls to ask their balance. You say you will check and ring back, then spend ten minutes rebuilding the number from a spreadsheet and hoping it is right.
You open their record while they are still on the phone. Every payment and charge posted itself, so the balance was already correct before they called.
The follow-up depends on someone remembering. Busy weeks it does not happen, and the invoice quietly ages another thirty days.
Reminders go out on schedule and log themselves against the record. Each account shows where it sits and what happens next, so escalation is a process rather than a judgement call.
Anyone on terms gets checked manually each month, and whether a charge is waived depends on who happens to look at it that week.
The schedule tracks itself. Charges stay off while they keep to it and come back automatically if they do not. The same rule for everybody, every time.
The quiet tax: entering the same information more than once, and then hunting for it later.
One workbook for contacts, another for jobs, a third someone keeps for billing, plus whatever the software you bought will not hold. They drift apart and nobody is sure which is right.
Entered once and shared everywhere it is needed. Change an address in one place and it is correct in all of them, with no workbook to reconcile.
Answering one question means the inbox, the shared drive, the accounting system, and asking whoever took the call. When they leave, half of it goes with them.
One record per customer and vendor with every invoice, document, note and conversation in the order it happened, and it stays put when people move on.
Payment notifications, supplier invoices and customer requests pile up until someone sorts them, and occasionally the same one gets actioned twice.
Each message is read on arrival, matched to the right record and filed. Duplicates are caught before they reach anyone.
The phone goes all week with "what do I owe?", "did you get my payment?" and "can you resend that invoice?" Each one costs somebody ten minutes and their concentration.
A customer portal. Each one gets a private link to their own balance, payment history, invoices and documents, on their phone, with no password to forget. The calls that still come through are the ones worth your time.
An example
The balance, how it got there, what has been sent, and what was said. Every line on it posted itself.
Figures are set in a monospaced face with aligned digits so columns scan cleanly and a wrong number looks wrong. Small thing, noticed every day.
Illustration, not a customer screenshot. Built in the same interface we ship, with invented names and figures.
Anything you currently build from a template, one at a time, by copying figures across.
An evening of copy and paste to get thirty statements out, and one goes out carrying last month's figures because a cell did not update.
Invoices, statements, quotes and letters generated from live data in one pass. All correct, all in the same format, every time.
Attach, address, send, repeat. A week later nobody can say for certain what went to whom, or whether it arrived at all.
Sent on generation and logged against the record, so there is never a question about what went out or when.
If a job needs doing on a particular day and depends on somebody remembering, it is a candidate.
The first of the month arrives and someone has to raise thirty invoices and apply last month's charges. Some months nobody does, and the revenue never appears.
It already ran overnight. Same day, same rules, every month, whether or not anyone noticed the date.
The day before the meeting disappears into pulling numbers out of four places and pasting them into a report.
The close runs overnight on schedule. The report is already current when you open it.
A request lands in someone's inbox and surfaces three weeks later when the customer chases it, by which point the deadline has gone.
It queues, routes to whoever approves it, and counts down against its deadline where nobody can miss it.
Renewals, service intervals and check-ins live in a calendar somebody has to actually open, or in one person's memory.
They fire on their own and record that they went. Nothing depends on a person being at their desk that day.
Included underneath
That is the whole first conversation. Thirty minutes, no obligation, and a straight answer about what is worth automating first and what is not worth touching.