Why a clear process beats a clever one

A company buys a sales system. It comes with automations, lead scoring, a pipeline with eleven stages and a dashboard for each of them. Six months later the sales team is back to a shared spreadsheet and a WhatsApp group, and the system holds a few hundred contacts nobody has opened since spring.

The software is rarely what failed. It was set up to run a process the team had never agreed on, so each person used it a little differently. Soon the numbers stopped matching what people knew to be true, and once nobody trusted the numbers, there was no reason left to keep typing into it.

Write down what already happens

Before anything is bought or built, write down how work moves through the business today. People tend to describe the process they wish they had, so it helps to walk through the last three jobs that came in, one step at a time.

A lead arrives by phone, through the website or as a message on Instagram. Somebody replies, or nobody does. A quote goes out as a PDF from someone's laptop. There is a follow-up if the salesperson remembers. The customer says yes on the phone, the job is handed over in a chat, and later someone builds the invoice by retyping the quote.

Put a name next to each step and note where the information lives at that moment. The list is usually shorter than people expect, and it shows where work falls through: the week between a quote and the follow-up, the job that starts before anyone has written down what was sold, the invoice put together from memory.

Fewer stages than you think

Most small businesses need five or six stages in a pipeline. New enquiry, quote sent, follow-up due, won, delivered and invoiced covers a surprising number of them.

A useful stage describes something that has happened. "Quote sent" is true or false, and anyone can check it. "Warm" and "interested" mean something different to every person who picks them, and a pipeline full of them tells the owner nothing on a Monday morning.

When everyone uses the same short list in the same way, the numbers become believable. You can see how many quotes went out this month and how many turned into work, without first asking anyone to update a sheet.

Automate what is already clear

Once the process is written down and people follow it, automation starts to pay for itself. A reminder goes to the salesperson when a quote has had no answer for five days, and the invoice is drafted from the accepted quote so nobody retypes a price.

The first rule of any technology used in a business is that automation applied to an efficient operation will magnify the efficiency. The second is that automation applied to an inefficient operation will magnify the inefficiency.

Bill Gates, The Road Ahead (1995)

The second half is the one that hurts. A reminder that fires at a stage half the team skips produces noise faster than any person could, and within a week everyone has learned to ignore it.

Checklists work for experts too

Some of the clearest evidence for plain written steps comes from operating theatres. Eight hospitals around the world started using the World Health Organization's surgical safety checklist, a list of 19 items read out at set moments during an operation.

Deaths after surgery fell from 1.5 percent of patients to 0.8 percent, and complications from 11 percent to 7 percent. The study compared the same hospitals before and after, so it shows an association rather than proof, but the drop was large. The operations themselves were the same. What changed was that the teams went through the same short list, in the same order, every time.

A sales process runs on the same mechanism. When the steps are clear, people stop relying on memory, and the business stops depending on whoever happens to remember.

Where to start

Spend an afternoon with the people who do the work and write the list: every step from first contact to paid invoice, who does it, and where the information sits. Then cross out any step nobody can explain. What is left is your process. Put that into a system first, and decide what to automate after.

It feels slower than buying the tool and working the rest out later, but it decides whether anyone is still using the tool six months from now.