The client called on a Monday. His name was Ruiz, or something like that. He had a warehouse in the Molina industrial estate and needed a ventilation system. He explained it over the phone in three minutes. He was a concrete man. The kind who says what he wants, asks how much it costs and, if the number fits, says yes.
Alberto, the sales rep, wrote it down. On a post-it note, because his phone was charging and the CRM was taking too long to open. He wrote "Ruiz — ventilation — Molina warehouse — urgent". He underlined "urgent" twice.
After lunch, Alberto passed the information to Jorge, the technician. He sent him an email with the subject "Warehouse ventilation quote" and in the body he put what he remembered from the conversation. Three minutes of information that, passing through Alberto's memory and keyboard, had become five lines.
Jorge read the email on Wednesday. Not because he was slow. Because on Tuesday he was at an installation in Lorca and on Wednesday morning he had two maintenance checks. He read it at three in the afternoon, after eating a sandwich in his van. He replied with a question: "Square meters of the warehouse?". Alberto didn't know. He called Ruiz. Ruiz didn't pick up. He left a message. Ruiz called back on Thursday mid-morning. Three hundred and forty square meters. Alberto forwarded it to Jorge.
Jorge did the math on Friday. He typed it up the following Monday. He sent it to Alberto. Alberto formatted it with the company template—which was in a shared Word document that sometimes lost its formatting—and sent it to Ruiz on Tuesday afternoon.
Nine days.
Ruiz didn't reply. Alberto called him on Wednesday. Ruiz said he had already hired another company. That they had sent him the quote in two days. No reproaches. No anger. With the polite tone of someone reporting something that can no longer be fixed.
Alberto hung up. He looked at the post-it note, which was still stuck to his computer screen. "Urgent" was still underlined twice.
The gap between people
What happened with Ruiz wasn't Alberto's fault. Nor Jorge's. Nor the admin's who formatted quotes when Alberto wasn't there. Everyone did their job. Did it well. Did it within the timeframes their other tasks allowed. The problem wasn't the people. It was the empty space between them.
The email waiting in an inbox. The call not returned until the next day. The missing data point that forces a round trip consuming three days. The template that has to be opened, filled out, reviewed, and sent manually.
Every step was reasonable. The sum was unacceptable. But since nobody saw the sum—everyone only saw their own step—nobody perceived it as a problem. It was simply how things worked.
Until a client hired someone else.
The nine days that could have been two
An automated system doesn't make Alberto faster or Jorge less busy. What it does is eliminate the gaps.
The client calls. Alberto enters the data into a form that takes one minute. The system notifies Jorge immediately, not by email but with a notification that doesn't get lost among newsletters and supplier invoices. Jorge sees he needs the square meters. The system asks the client directly, by text or email, without Alberto having to play middleman. The data arrives. Jorge calculates. The quote is generated automatically with the correct template, updated prices, and company formatting. It gets sent.
Two days. Sometimes less.
It isn't magic. It isn't artificial intelligence. It is that someone sat down to look at how information flows—or doesn't flow—between the people in the company, and built a road where before there was open field.
What the gap costs
Alberto lost Ruiz. Estimated billing: four thousand euros. Not a tragedy. It's one ventilation installation. But if Alberto loses one Ruiz a month—and he does, even if he doesn't always find out—that's forty-eight thousand euros a year. Forty-eight thousand euros lost not because the work is done poorly, but because it's done slowly.
And there is the other cost, the one that doesn't appear on any spreadsheet: reputation. Ruiz didn't complain. He didn't leave a negative review. He simply hired someone else and moved on with his life. If anyone ever asks him, he will say Alberto's company took too long. He won't say they were bad. He'll say they were slow. Which, deep down, is worse.
What Alberto said later
The manager called a meeting. He wanted to understand what had happened with Ruiz. Alberto explained the process. Step by step. The manager took notes. When he finished, he looked at the whiteboard.
"Nine days?"
Alberto nodded.
"And every step was necessary?"
"Every step, yes. What was extra was the wait between steps."
The manager stared at the whiteboard for a moment. Then he erased the arrows between the steps and left just the steps. Five loose rectangles. No arrows.
"This is what we do," he said. "And this"—he drew the arrows again, but this time in a straight line, without the zigzags of email and waiting—"is what we should do."
It wasn't a very good drawing. But the idea was clear.
Alberto took the post-it off his screen. He threw it in the trash. Not because it had stopped being urgent, but because "urgent" should never depend on a post-it note.
How many "Ruiz" does your company lose a year without knowing?
If you notice that internal processes get stuck between departments or that response times are too long, the solution is almost never to ask your team to work faster. It is to eliminate the waiting.
Let's talk about your processes