What manual data entry really costs you
The sum to do with your own company's numbers, the items almost everyone forgets, and a way to tell whether automating that work makes sense or not
Read the guideGuides written for the person who decides, not for the person who codes, with the things I'd usually explain to you on the phone
You can read them just to understand how things work, without writing to us

You can do the sum on your own, and sometimes the answer is that it isn't worth it, that happens too

The sum to do with your own company's numbers, the items almost everyone forgets, and a way to tell whether automating that work makes sense or not
Read the guide
You don't automate everything at once, you start with one, and choosing it well is half the result
Read the guide
It's a division, you don't need a consultant to do it, you need to put the right numbers in
Read the guide
Do the sums before you post a job ad, look at what the repetitive work you are about to hand to someone really costs you, how much of it can be automated, and the cases where a person is exactly what you need
Read the guide
You are paying for a person's hours, not a finished product, and seeing that changes the way you buy it
Read the guide
They are two ways of splitting the risk, and it pays to know which way it falls before you sign
Read the guide
The ready-made program costs less and you have it tomorrow, the custom one does exactly what you do, and the choice isn't obvious
Read the guide
Writing it correctly was ten seconds, putting it right is another story altogether
Read the guide
You need a number, not a feeling, and to get it you don't have to put a stopwatch in anybody's hand
Read the guide
In almost every office two or three processes take the big slice of the time, the rest is noise
Read the guide
There are jobs where an automation is money thrown away, and we tell you before instead of after
Read the guide
A method for working out which steps are eating your hours, which ones can be taken out of the way, and how much extra work you can carry with the people you already have
Read the guideAPI, RPA, OCR, EDI, acronyms with simple things underneath

If your vendor told you an API is needed and you nodded without understanding, this page is for you
Read the guide
It's an acronym that goes round in presentations, underneath there's something simple
Read the guide
It isn't that the program is stupid, it's that a crooked scan is crooked for it too
Read the guide
If a customer mentioned EDI to you and you pretended to know what it was, here's what it is
Read the guide
One follows rules you decided, the other tries to work things out, and what your business software needs above all is the first
Read the guide
Almost never, and whoever puts it everywhere is probably selling you the word of the moment
Read the guide
They look the same on screen, for anything that has to read them automatically they are two different worlds
Read the guide
The totals are easy, it's the lines in the middle that give you the headache
Read the guide
The data is already in there written cleanly, if somebody is still retyping it something is wrong
Read the guide
There are two ways of making the programs you have in the company work together, here's what changes between them, when one is better and when the other is, and the questions to ask about your process before you decide
Read the guide
Same supplier, same file, and every time something has shifted
Read the guideThe right question isn't whether it can get something wrong, it's what happens when it doesn't understand

The right question isn't whether it can get something wrong, it's what happens when it doesn't understand
Read the guide
It gets them wrong in a different way, and that's the thing that really counts
Read the guide
There are jobs an automation can close on its own, others where it's better for it to stop and ask a person to confirm, and the criteria for deciding which of the two your case is
Read the guide
The two roads change the cost, the reliability and who has to keep the computer switched on
Read the guide
Yes, and it's one of the reasons it's worth it, but not for every job
Read the guide
It stops halfway, and the real question is what it finds when it starts again
Read the guide
It's a question you have to ask, and the answer belongs in the contract, not left as a spoken promise
Read the guide
It's one of the first questions people ask, and it's right to ask it, the answer belongs in writing in the contract
Read the guideIf you recognize your own work in one of these, it's a good place to start

It's the most repeated job there is in the back office, and it's the one where the checks count for most
Read the guide
Everyone sends them the way they like, some a PDF, some an Excel file, some write it in the body of the email
Read the guide
How reading an invoice or a delivery note (DDT) in PDF really works, which data can be pulled out, which checks you need so that wrong numbers don't end up on file, and where the method stops working
Read the guide
You start from the file, put the checks in before saving and let an automated system fill in the screens, even if your business software offers no direct integration at all
Read the guide
You log in, search, download, rename, save in the right folder, twenty times in a row
Read the guide
Logins, forms to fill in, documents to upload and receipts to download, which of these steps can be handed over to an automation, how it works underneath and when it isn't worth trying
Read the guide
The business software says one thing, the spreadsheet says another, and every month somebody spends half a day working out which one is right
Read the guide
That's where the margins go, quietly, one line at a time
Read the guide
The entries are always the same ones, only the figures and the dates change
Read the guide
Nobody did it on purpose, it happened over ten years, and now the reports don't add up
Read the guide
The same data, three screens, and on the third somebody gets a digit of the VAT number wrong
Read the guide
One for production, one for accounting, and a person in the middle acting as the bridge
Read the guide
Then somebody, when there's time, books them in one by one, and meanwhile the stock in the system is wrong
Read the guide
An Excel file turns up laid out his own way, and somebody has to get it in without getting a single price wrong
Read the guide
Orders, payment reminders, questions, attachments, and somebody sorting them by hand from first thing in the morning
Read the guide
There's a rule, everybody knows it, and nobody follows it when things get busy
Read the guide
The due dates are there, so is the list, all that's missing is the time to look at it
Read the guide
And you write ten of them to sell one, so nine are work nobody pays for
Read the guide
Same steps, same copy and paste, same spreadsheet, every week for three years
Read the guide
Which of the practice's jobs can be handed to an automated system, which are better kept by hand, and how to tell in two minutes which of the two groups a process you run every week belongs to
Read the guideOld, closed, with no integrations, doesn't mean lost

How automating a program you already use works, which jobs can be taken off people's hands, which are better left with them, and how to do the sums yourself to see whether it adds up
Read the guide
If your business software exposes no data and talks to nothing, there's still a road, letting a system use it and click in your place, how it works, when it's worth it and where it breaks
Read the guide
It works, the company runs on it, and every time you ask to connect it they tell you it can't be done
Read the guide
Sometimes he is, and we say so too, even though we make a living from the opposite
Read the guide
Which updates break an automation and which don't, how it notices by itself that something doesn't add up, and what it takes to get it back on its feet quickly
Read the guide
It happens, and it's expected, the question is who puts a hand to it and who pays
Read the guide
He may well be right, and he may well be talking about his own job, not yours
Read the guide
They were written by someone clever who isn't here any more, and nobody knows where to start
Read the guideIncluding the awkward questions, which are the ones worth asking before you sign

Less than you think, and nothing technical, but that little has to really be there
Read the guide
Three minutes of screen are worth more than ten emails, and you need nothing special for it
Read the guide
Marisa knows how, but when you try to have the rules explained twenty exceptions come out
Read the guide
You do, always, and that isn't a courtesy, it's the only way it works
Read the guide
It depends, but not on weeks of code, it depends on how quickly the odd case shows up
Read the guide
You don't flip a switch and walk away, you start slowly with the brake within reach
Read the guide
The day it's ready isn't the end, it's day one, and anyone who sells it to you as finished is misleading you
Read the guide
It's a serious worry, it has to be faced before and not after, because if the office pulls the other way nothing gets off the ground
Read the guide
And when they go they take away everything they knew about the process, which was written down nowhere
Read the guide
The work doesn't grow slowly, it all arrives together in five days, and it's always the same five
Read the guide
Good, that's not a problem, they're two different trades that meet
Read the guide
It's the right question to ask before you sign, not after, and it goes for anyone, not just for us
Read the guide
It has real advantages and real risks, and we set out both of them, then you decide
Read the guideDescribe the process or send a short screen recording and we'll tell you what can be automated