Business process improvement: one real process, and exactly where the lead dies

Business process improvement starts with one process, not a big map. An honest teardown: where the inquiry dies, what to connect, and what not to automate.

Illustration: the path of an inquiry through a business, breaking and going dark at one point

I searched for business process improvement to see what a business owner actually gets. I got process maps, acronyms, and advice to define success metrics. All true, and nearly useless on a Monday morning. Nobody shows the wiring itself: where exactly, on which line, the business loses the inquiry.

So instead of another map, let us take apart one process. Not a specific client's process, I do not tell stories about real people. This is the typical route I see again and again, in completely different businesses, and it almost always breaks in the same places.

The process, line by line

Someone interested sees you, through an ad or a recommendation. Now count the stops: they fill in a form on the site, or send a WhatsApp message, or call. The form lands in an inbox. The WhatsApp lands on a personal phone. The call, if you did not pick up, lands nowhere.

Someone is supposed to get back to them. In practice, whoever saw it first gets back, and who saw it first depends on which app happened to be open at that moment. After the callback, the details are written down somewhere: a notebook, a spreadsheet, a head. Then a meeting goes into a calendar, a quote is issued in different software, and the invoice comes from a third system.

Now ask yourself one question. If I asked you right now how many inquiries came in this month and how many are still waiting for an answer, how long would it take you to reply? If the answer is "I would have to check in a few places", you have found the process that needs attention. Not all of them. That one.

The four points where it breaks

The entrance is split. Three channels, three inboxes. There is no single list of who got in touch. I wrote about this separately in unifying inbound channels, because it is almost always the first point.

No owner and no clock. An inquiry has no name attached and no target time. As long as "someone will handle it", under load someone will not. That is not negligence, it is structure.

The manual handoff between tools. Every time a person retypes something that already exists somewhere else, two versions of the truth are born. I went through the real price of that in duplicate work between systems.

No status. New, contacted, quote sent, closed. Without those four words there is no way to know what is stuck, so things get stuck quietly.

Notice that none of the four is a people problem. All four are wiring problems.

What to connect, and in what order

The order matters more than the tools, so this is the order I work in:

  1. Unify the entrance. Every inquiry, from every channel, lands in one list. That alone changes the day.
  2. Add an owner and a time. Every inquiry gets a name and a clock. Now you can see what is late.
  3. Kill the double typing. Details entered once flow onward, to the meeting and the quote, without anyone copying them.
  4. Only now add automatic reminders. Not before, because automation on top of a broken process simply reproduces the break faster.

Step four is the one everyone wants to start with. It is the most common mistake I see, and I wrote about it in where to start with your first automation.

What it saves, without invented numbers

I am not going to give you percentages. I do not know how much it will save you, and anyone quoting a number without knowing your business is selling you a feeling. What I can tell you is what changes in character: you stop searching. The question "what happened with Tuesday's inquiry" gets an answer on one screen instead of across three apps. And that, in practice, is what gives you your head back.

And what is not worth automating

This is the part you will not find from someone selling automation.

Do not automate a process that happens once a month. The time you spend building and maintaining it exceeds the time you save. Do not automate a decision that needs judgement, unusual pricing or a sensitive client, for example. Do not automate the first conversation with a person, people recognise an automated reply, and at that stage it costs you trust. And do not automate a process you are still changing every week, let it settle first.

The rule I work by is simple. Good automation removes typing and reminders. It is not supposed to remove judgement.

If you want to do this yourself, start with the cheapest exercise there is: take your last five inquiries and sketch on paper where each one travelled, and where it waited. The bottleneck will jump out at you. And if you want me to look at it with you, the short questionnaire maps it in a few minutes, or you can just see what I actually build.

Tips & content, once a week, no noise

What's new on the blog + a short automation tip, straight to your inbox.

By subscribing you agree to receive content by email from Digital Efficiency · One-click unsubscribe in every email · Privacy policy

Want to know what your business's system needs? The smart questionnaire maps it in a minute. Then I get back to you personally with a report.

Start the questionnaire →

Or start on your own: there are free tools you can run right now, with no form and no email.