I've spent the last while building software for a sheet metal fabrication shop, a health and safety consultancy, a hockey gear platform, and I've studied plenty of others closely. Businesses that could not be more different. Different customers, different products, different worlds.
They all had the exact same problem.
The moment a customer has to stop and wait on you
Here is the pattern, and once you see it you cannot unsee it.
Somewhere in the middle of doing business with a customer, there is a moment where they have to stop and wait on one of your people. Usually it is a price. Sometimes it is an approval, a feasibility check, a choice they can't make alone, or an answer only your expert can give. Whatever it is, it depends on a human sitting down and working it out, and until that human is free, the customer is stuck.
That moment shows up in three places. Once you know to look for all three, you find them everywhere.
Before the sale
This is the one people notice first. A customer is ready to buy and has to wait on you before they can.
At the fabrication shop, a customer would send over their part drawings and then wait. A day. Two days. Sometimes a week, while someone reviewed the files, checked them against what the shop could actually do, and worked out a price. Meanwhile the machines sat mostly idle. The constraint on the business was never production capacity. It was the wait at the front of the sale.
At the consultancy, the first real step was a hazard assessment that only a credentialed expert could perform. Every lead had to get in line behind that expert's time. At the hockey platform, a customer faced a wall of options with no way to know which one was right for them without help. Same shape. A ready buyer, stuck waiting on a person.
During the sale
Sometimes the customer has already decided. They want it. Now they are stuck turning that "yes" into an actual order, and that still runs through you.
This is the business where the thing being bought has too many variables to just add to a cart. The customer knows what they want in their head, but getting to a real, valid, priced order means someone on your side has to configure it, check it, and confirm it. The buyer is committed and still waiting, not to decide, but to finish deciding.
During and after the work
This is the one I almost never see people account for, and it might be the most expensive.
Think about taking your car to a mechanic. You hand over the keys and then you are in the dark. You don't know what they found, what it will cost, or what is happening, until someone calls you. And when they find something new mid-job, everything stops while they try to reach you for approval. That back-and-forth is slow for you and awkward for them, because now it feels like an upsell over the phone.
A shop I know solved this. They built a tool that shows the customer exactly what was found, with photos and a running timeline, and lets the customer approve the extra work themselves, right there, no phone tag. The customer is never in the dark and never feels cornered. And here is the part that matters for the business: they sell more work, because approving a repair you can see for yourself is easy, while approving one described to you over the phone is not.
The customer already bought. The friction is not in front of the sale at all. It is in the middle of the work. And it is the same pattern: the customer stuck waiting on a person for something they could handle themselves.
Why the wait costs more than it looks like
The obvious cost is the deals you lose. A customer who is ready and has to wait will sometimes go with whoever answers first. You never see those. They do not show up in your numbers because they were never customers. They just quietly went somewhere else.
But there is a second cost that is easy to miss, and it is bigger.
The fabrication shop could handle far more work than it was getting. The people were there. The machines were there. The overhead was already paid for. The only thing standing between the shop and more revenue was how fast a customer could get an answer. Every job it could have taken but did not is not just a lost sale. It is idle capacity that the business is paying for either way.
The during-work version has its own second cost. The mechanic who can't reach a customer for approval doesn't just lose time. They lose the extra work entirely, because a customer who can't be reached is a customer who doesn't say yes. The repair that would have been approved in one tap over a photo becomes a repair that never happens.
That is the part that reframes the whole thing. The bottleneck is rarely that the business cannot do the work. It is that the work keeps getting stuck waiting on a person.
The step is usually rules, not judgment
Here is the part that surprised me the first time and now I expect it every time.
When you actually break down that manual step, most of it is not real expertise. It is rules. The fabricator was not making a creative judgment call on every quote. They were applying the same constraints and the same pricing logic they always apply, by hand, one job at a time. The consultant's assessment followed a defined structure. The hockey recommendation came down to matching a few inputs to the right option. Even the mechanic's approval is just showing the customer what was found and letting them say yes.
And if a step is rules, it can run without you.
That is the whole idea. You take the thing your customer currently has to wait on a person for, and you hand it back to them as a tool they use themselves. They upload, they answer a few questions, they see the work, they approve it, and they get what they need in seconds instead of days. The expert stops being the bottleneck. The customer stays in control. The capacity you were already paying for finally gets used.
Not every business has this
I want to be honest about the limits, because the pattern is real but it is not universal.
Sometimes the manual step genuinely is expertise, not rules, and it cannot be written down. Sometimes there is no waiting step anywhere, before, during, or after. Sometimes a business is already at capacity, in which case the answer is to raise prices, not build software. The pattern only holds when there is a repeatable, rules-based step that a customer is stuck waiting on.
But when it does hold, it holds hard. And I keep finding it in places I would never have grouped together.
If you have read this far, you probably already have a guess about where this lives in your own business. That moment where customers wait on you, whether it is before they buy, while they are buying, or while you are doing the work. If you want to find it exactly, and get an honest read on whether a tool would actually help, that is the thing I built the rest of this site to do.
