What admin should a growing business stop doing by hand?

Stop retyping anything that already arrived in a structured form. The same name, the same address, the same figures, copied from an email into a spreadsheet, a CRM and an invoice. That is the admin automation pays for. Judgement stays with a person.

Automate is the third part of the job, after Attract has produced the enquiry and Convert has made sure a person owns it. If those two are leaky, automating the typing just files the leak more neatly.

The work that should go first

Look for steps a careful person could describe without saying "it depends". They tend to be the same few, in businesses that have never called them a process:

• Copying an enquiry into another system. The form already collected it. A person should not be the integration.
• Saving attachments by hand. Invoices, application forms, photos from a job. They arrive by email and get dragged into a folder with a name nobody else would guess.
• Chasing a status. "Did they approve it?", "Has the quote gone?", "Did anyone reply to this one?" A reminder with a rule beats a memory.
• Sending the same update twice. The customer, the engineer and the accounts person each get a version of the same facts, typed out again.
• Creating the same documents from scratch. Proposals, contracts, onboarding packs, where most of the page is identical and six fields change.

These are ordinary. That is why they survive. None of them looks big enough to deserve a project, and together they are a day a week.

A simple test

For a task you are tempted to automate, ask:

1. How often? Weekly is enough to matter. Once a quarter is probably not.
2. Is the input already digital? An email, a form, a file. If the input is a conversation that has not been written down, automate the filing of the outcome, not the conversation.
3. Can you write the rule? "If the amount is under this, file it and notify Sam. If it is over, ask Sam first." If the honest answer is "Sam just knows", you do not have a rule yet. Write the rule before you buy the tool.
4. What happens on the exception? The automation should stop and show a person the odd one, with the reason. It should not guess.

If it fails the rule test, it is still someone's job. Making a flowchart of a fuzzy job does not make it automatable. It makes a diagram of the confusion.

What to leave with people

Leave anything where the value is the decision: whether to take the work, how to price the awkward case, what to say to an unhappy customer, whether the photo from site is good enough to invoice against.

Also leave the first version of a process you do not understand yet. Automating a mess gives you a faster mess and a supplier to blame. Run it by hand until the steps are boring. Boring is the signal.

The longer definition of what counts as a process, and where tools like Power Automate fit, is in what business process automation actually is. The service is process automation, scoped around one process at a time rather than a transformation programme.

Where this sits after Attract and Convert

Attract decides whether strangers can find you and raise a hand. Convert decides whether that hand gets a reply from a named person, with a record. Automate decides whether the admin around that work is still being done as craft.

Do them in that order when the leak is commercial. There is no point removing the retyping if the enquiry never arrives, or arrives and sits unseen. Once the enquiry is owned, the copying, filing and chasing are the right things to take off people's desks.