To automate the process is to make a whole chain of work run without someone chasing each step. Not one job, like typing a new client in by hand. The whole run: a signed proposal becoming a paid invoice, an email becoming an open matter, a brief becoming something you would publish.
We already wrote about one repeated job. That Field Note is how to automate a repetitive task. This one is the longer thing that job sits inside. If you only fix the copy-paste, someone still chases the rest.
A task is one step, a process is the chain
Someone types a new client into the system. That is a task. The process is everything around it. The signed proposal arrives. The client goes on the books. A folder appears in the drive. The first invoice goes out. The first meeting gets booked. The person who will do the work is told.
If you only stop the typing, the invoice still sits in a mailbox. The folder still waits for someone to make it. The first meeting still lives in a WhatsApp that nobody filed. You have made one step faster. The chain still needs a person to remember the next one.
Here is a simple test. If finishing one job is what starts the next one, you are looking at a process, not a task. Filing a signed letter can be a task. Opening a matter, the file a law firm starts for a new client, is a process, because filing is only one step in the chain.
In a firm of five to fifty, the same person often holds the whole chain in their head. They did the typing. They are also the one who notices the invoice has not gone, because nobody else owns the run. The hours you feel are theirs.
Write the whole chain on one page
Get the person who actually holds the chain to talk through a real week. Not a tidy diagram. Last Tuesday. Start at the first thing that arrived, and stop at the last result a client or a partner would recognise as done. Put that on one page, including the messages and the extra sheet that never made it into the official tool.
The WhatsApp they send when a field is blank belongs on that page. So does the mailbox they check for an invoice PDF. So does the side spreadsheet that holds the real status.
If two people run the same chain two different ways, write both. The page will show you which steps exist only because someone remembered, and which ones actually have to happen. Do not write the tidy version. Write the one that ran last Tuesday. That is the process you have.
Say when it starts and when it is finished
Two lines on that same page.
It starts when... It is finished when...
A process that starts when "we have a new client" has no start. Point at the thing that arrived: the signed PDF in the mailbox, the completed form, the email that says yes. A process that finishes when "they are onboarded" has no finish. Point at facts you could check on a Wednesday: they are on the books, the first invoice is out or paid, the person doing the work has been told.
Most teams try to automate the process by picking a tool first. The tool does not know those two lines. The person who ran the chain last Tuesday does.
If the start and the finish are vague, the chain will either fire too often or never quite finish. Specific enough to check is enough.
Automate the ordinary cases
Through a whole chain, ordinary means each step looks like last month. The proposal matches the template. The fee is the usual one. The folder looks like the last client's folder. That run can move without a person in the middle of every step.
The odd ones go to a named person, in a list they already watch, with enough to finish the job: what arrived, which step skipped, and why. A message that only says "failed" puts them back in the same hunt.
Do not try to cover every special arrangement on day one. A referral with a custom fee. A client who pays from two companies. A matter that is urgent and incomplete. Name those, send them to a person, and leave them until the ordinary cases show you which ones actually come up.
If being wrong is expensive, the person stays on that step. Put a name on it, not a shared inbox. When the chain skips, that person should see why.
The person is not a failure of the setup. They are the part that should stay human. Judgement, odd fees, a client who is not a fit: those are not bugs. They are the job.
Make sure you can see it working
You should be able to answer, without hunting, whether this client's chain finished. If you have to open three tools to find out, you cannot see it working. Put one place the team already looks, and let it show the runs that finished and the ones that stopped.
A chain that fails quietly is not finished. The invoice that never left the mailbox, the folder that never got made, the follow-up that sat in WhatsApp: those are the cases a rule cannot see. Build the check in the same pass as the ordinary cases. When it ran, how many it handled, how many it sent to a person, and a way to pick those up.
If nobody would notice it going quiet, the check is in the wrong place. Put it where the work already lives.
What to do this week
You do not need a new platform. You need one chain that already hurts, written on one page, with a start, a finish, the ordinary cases marked, a name on the rest, and a way to see it working.
Pick the chain. New client to paid invoice is a good one because you can see when it is done. A matter opening is another. A brief becoming something you would publish is a third.
Write the page. Include last Tuesday's mess. Circle the ordinary cases. Write a name next to the odd cases. Then stop. The next decision is not which tool. It is whether the ordinary cases are actually ordinary enough to trust.
That is how you automate the process. If the page is still a mess, do not connect anything yet. Cheaper to find that on paper than inside a chain that copies the confusion, only faster.
