A clinic I work with takes a deposit when someone books, and collects the rest after the appointment. The rest was not coming in. Clients paid the deposit, came in, went home, and never received a way to pay the balance. From the outside that looks exactly like a broken business process — something wired up wrong, quietly failing every week.
Three separate attempts went into fixing it. All three were looking for the break.
There was nothing broken. There was nothing there.
The fourth look did something the first three had not. Instead of hunting for the fault, it listed every automation on the account and read what each one was actually for.
Fifteen in total. Thirteen were switched on and running: booking confirmations, reminders before the session, follow-ups after it, a recall months later.
Not one of them had anything to do with an invoice or a balance.
The payment link was never late. It was never sent, because the thing that sends it had never been built. The only trace of an earlier attempt was an unfinished draft sitting unpublished in the account from a week before.
Is your business process broken, or was it never built?
These two feel identical from where the customer stands. Nothing arrives either way. But they cost completely different amounts to find.
- A broken step leaves evidence — something ran, something failed, something is half-done.
- A missing step leaves nothing at all, and nothing is exactly what a search for a fault turns up.
Here is the trap. A search for a broken step that finds nothing feels like a search that has not gone deep enough yet. So you go deeper. That is how the same question gets asked three times.
The assumption that stopped anyone building it
There was a reason nobody had built it, and the reason was wrong.
The belief was that sending a bill after the session would charge the client twice — that the booking already created one, so adding another would double up. Sensible, cautious, and it stopped the work dead for weeks.
A look at the actual payment records settled it in minutes. No bill is ever created at booking. There was nothing to duplicate. The very action everyone had avoided was the mechanism the whole thing needed.
An assumption that stops work deserves the same scrutiny as a claim that starts it. Nobody ever audits the reasons they did not do something.
Three questions before you fix a broken business process
Ask these in order. The first one is nearly free and it is the one that gets skipped.
1. Does the step exist at all?
Not "is it working" — does it exist. Open the list of everything your system does and read the names. If the job you are chasing is not in that list, you do not have a repair job. You have a build job.
2. Who or what actually performs it?
A person, a piece of software, or nobody. "The system does it" is not an answer until you can point at the thing. Plenty of steps live only in somebody's memory, which means they happen when that person is in the room and not otherwise.
3. What proves it ran?
If a step leaves no receipt, you will never know it stopped. The clinic's missing payment link left no trace of failure, which is precisely why it went unnoticed for so long.
What this looks like in your business
The pattern is not about clinics or software. It shows up wherever money or follow-up depends on a step nobody has looked at directly.
- The quote that "goes out automatically" after a site visit.
- The review request "we always send" after a job is finished.
- The reminder for the second half of a payment.
- The follow-up on a lead that went quiet.
Pick one. Do not ask whether it is working. Ask someone to show you the thing that does it. If nobody can point at it, you have just found a week of your own time that you were about to spend looking for a fault.
The cheapest fix in business is the one where you discover there was never anything to fix — only something to build.