Chaos in HR and sales: a process audit and automation
When everything rests on people rather than on a process, one person's holiday gets planned like a military operation and a new hire takes months to get going. Below are five signs there is no process, and the order of work — describe first, automate second, with no exceptions.
When everything rests on people rather than on a process, one person's holiday gets planned like a military operation and a new hire takes months to get going. Below are five signs there is no process, and the order of work — describe first, automate second, with no exceptions.
---
Somebody left and the process stopped
The sign that makes this diagnosis in a minute: one employee leaving paralyses an area of the business.
They knew how it was done. Knew who to call, where the files were, what to say in a difficult case. None of it is written down, because "everybody knows anyway". Everybody knows while they are there.
Then come the derivatives of the same thing. A new hire takes three months to get going and pesters everybody else throughout. The same task gets done differently by different people. Nobody can say how long it should take. Asked who is responsible, people answer "well, we all are".
The company works and grows meanwhile. It is just that every new person adds chaos rather than output.
Why written procedures usually do not help
The root cause: they get written as a document rather than as a tool.
The classic scenario: somebody was hired, spent six months writing procedures, produced a two-hundred-page volume, and it went into a folder. Nobody opened it once, because finding anything in there takes longer than asking a colleague.
The misconception: "we need to document everything". No. You need to document what repeats and what is expensive when it goes wrong. The rest is wasted time on both sides.
A second misconception: "procedures exist to control people". No. A procedure exists so somebody can do the work without asking, and so the result does not depend on who is doing it. The moment it is perceived as supervision, it gets sabotaged.
And a systemic layer. A procedure not embedded in the tools goes out of date within a quarter. A written order of actions that is never prompted at the moment of work survives exactly until the first change.
How the pipeline works
Step 1. A map of the processes
Not "how it should be" but how it actually is. Assembled from interviews: what do you do, where does the task come from, who do you hand it to, where do you usually get stuck.
The main finding usually comes at this step. Processes nobody asked for turn up, along with duplication between departments and points where a task hangs with no owner.
Step 2. Priority by the cost of chaos
Documenting every process is pointless. The ones selected satisfy at least two conditions: they repeat often, a mistake is expensive, the knowledge sits with one person.
The last is the most important criterion. A process one person knows is not a process, it is a risk.
Step 3. Getting the knowledge out of heads
The most labour-intensive stage, and the one that used not to work.
An assistant conducts a structured interview with the person holding the knowledge: what do you do, in what order, what goes wrong, how do you handle exceptions. The person does not have to sit down and write — they have to answer questions, and that they can do.
What comes out is a draft procedure the holder checks and corrects. That is many times faster than "please write down how you work".
Step 4. A procedure people actually use
Format matters more than content. A working procedure is short, answers a specific question in ten seconds, describes the exceptions and says who to go to when a case is not covered.
The sign of a non-working one: it cannot be read in the time the task takes.
Step 5. Automating what needs no human
Once formalised, part of the described processes turns out to be mechanical: move data, send a notification, compile a report, remind about a deadline. That goes to automation.
The order is fundamental: describe first, automate second. Automated chaos is chaos that has become harder to fix.
Step 6. Assistants as prompts at the moment of work
A procedure in a folder dies. A procedure built into an assistant you can ask at the moment of the task lives.
An employee asks "what do I do if a client wants to move the deadline" and gets an answer from your procedure rather than from general notions. A new person gets going in days rather than months.
Step 7. Ownership
The final step, without which the previous six fall apart: every process has one owner. Not "the department" but a person responsible for the description matching reality.
How to tell it is time
Five signs. Three is enough.
A new hire takes more than a month to get going. That is a direct cost: the salary is paid, the output is low and colleagues get pulled away to explain.
The same task gets done differently by different people. The client gets different service depending on who answered.
A key person's holiday has to be planned like a military operation. A sign that there is no process, there is a person.
There is no answer to "how long should this take". Which means you can neither plan nor notice things getting worse.
The same mistakes keep recurring. They get discussed verbally and the discussion settles nowhere.
If you recognised three of the five, the company is growing faster than its processes, and the gap will widen on its own.
What the business gets
- A map of the processes as they are — with duplication and gaps
- A priority: what gets formalised first and why
- Procedures for the key processes in a format people use
- Automation of the mechanical part
- Prompt assistants answering from your procedures
- An ownership chart: whose process is whose
- An update procedure: who refreshes it and when
On resistance, separately
This is the project's main risk and it is not technical.
People resist having their work described for an understandable reason: being irreplaceable feels like protection. While only I know how this is done, I will not be dismissed.
One thing works: showing that a procedure takes routine off a person rather than making them redundant. Whoever stops being asked about trifles gains time for more interesting work. Whoever goes on holiday and comes back to a functioning operation rather than a backlog feels the difference quickly.
What must not be done: promising redundancies. One mention and you get sabotage at every step where you need people to be honest.
What does not need documenting
Half the failed procedure projects are attempts to document everything.
You do not document what happens once a year. It is cheaper to work it out each time than to keep the document current.
You do not document the creative part. The order of work on a design or a piece of copy formalises up to a point; beyond that begins taste, and a procedure does harm there.
You do not document what is about to change. A process being rebuilt every quarter is too early to write down.
And you do not document for the sake of completeness. A procedure exists so somebody can do the work without you. If the task is one nobody can do without you anyway, documenting it is work for the drawer.
What it costs
The cost is calculated from the volume: how many processes get formalised, how many people are involved, whether automation and assistants built on your procedures are needed.
An honest caveat: the fee here is stated by our methodology from the scope of work rather than taken from market statistics — I have not measured what comparable work fetches on average.
What to compare it against. The cost of three months bringing every new hire up to speed, and the cost of one departed holder of knowledge.
What is needed for this
AI assistants — more than 140 across 14 categories, including HR, sales and analytics. Interviews, extracting knowledge, drafting procedures. Chat access comes with Basic.
Automation templates — the mechanical part of the processes. The Plus plan; advanced ones Full.
Your own assistants built on your procedures — Creator+. Those are what turn a document into a living prompt.
Registration is free and opens three days of Basic access — enough to run one interview and get a draft procedure for one process.
Do one thing today: write down the processes exactly one person in the company knows. The list is usually shorter than it feels and more frightening than expected. That is where you start.
---
What gets automated once the processes are described
The procedures are written — now the question is what to put on autopilot first.
CRM integration — by its own description the most in-demand service in this category. It creates leads, assigns tags, notifies the team, opens deals. An integrator's fee is from $1 200.
Make + JSON + Google Sheets — processes data structures and updates spreadsheets in real time. Management dashboards for small businesses get built from this: the manager sees the figures without pulling people away.
Call transcription into the CRM — transcribes a conversation and attaches it as text to the deal. It closes a standard hole: the conversation happened and the record is empty.
Staff synchronisation — a list of employees that updates itself. A small thing, but it is exactly why procedures drift from reality within two months.
The order worth keeping. First the process is described, then automated — a rule with no exceptions. A ready solution saves weeks of building but does not remove the first step: automated chaos remains chaos.
The Legacy library — the Make and Full plans.
---
What to read next
[A company knowledge base as a service](/en/blog/company-knowledge-base) — what gets done with the knowledge collected.
[Three automations people buy](/en/blog/three-automations-that-sell) — what gets automated first.
[AI for business owners](/en/blog/ai-for-business-owner) — three levels of adoption and the order between them.
[AI for HR](/en/blog/ai-for-hr) — if the problem comes down to hiring.
[n8n and Make automation templates](/en/blog/n8n-automation-templates-guide) — the full guide to automations.