Your Business Has a Speed Limit

A friend of mine runs a services shop that did just under four million last year. Good operator. Smart guy. Works like a mule.

He called me a few weeks back doing the thing everybody does, which is complaining about time. Not enough hours. Team’s maxed. He’s thinking about hiring two more people he can’t really afford yet because the work is backing up and clients are getting twitchy.

I asked him one question.

“From the second a client signs, how long until they get the first real thing they paid for?”

Long pause. He didn’t know. Guessed two weeks, maybe.

So we went and looked. Pulled thirty of his most recent projects and timestamped them. Signed date. First deliverable date. Simple.

Eleven days, on average.

Then we did the part that actually mattered. We asked how many of those eleven days involved an actual human being doing actual work on that project.

Two.

Nine days of nothing. Nine days where the thing sat in somebody’s inbox, or waited on a kickoff call that got scheduled a week out, or sat in a folder because the person who does step three was finishing step three on four other projects.

He didn’t have a capacity problem. He had a nine day problem. And he was about to spend a hundred and sixty grand on two hires to solve it.

Here’s the thing almost nobody looks at, and it’s the single biggest lever most operators have sitting untouched.

There are two clocks running in your business.

The first one is touch time. That’s the actual labor. Somebody sitting down and doing the thing. This is the clock you obsess over. It’s the one your team reports on, the one your project software tracks, the one you think about when you think about productivity.

The second clock is elapsed time. Wall clock. Calendar days from the moment something starts to the moment it’s done and in the customer’s hands.

In most businesses I’ve looked at, touch time is somewhere between ten and twenty five percent of elapsed time. Which means the overwhelming majority of your delivery timeline is your work sitting perfectly still, waiting for something.

Read that again, because it changes what you do on Monday morning.

This is why hiring feels like it never fixes anything. You add a person, they add touch time capacity, and the queue keeps growing because the queue was never about capacity. It was about how long things sit between the moments somebody touches them.

Speed is not effort. Speed is the absence of waiting. Those are completely different problems with completely different solutions, and if you solve for the wrong one you will spend a fortune and feel like you’re going backward.

Let me put money on it, because that’s the part that gets attention.

Cutting your cycle time in half does four things at once, and this is the part operators tend to miss.

You collect faster. If you invoice on delivery or milestone, and delivery moves from six weeks to three, your cash conversion cycle halves. That’s working capital you didn’t have to borrow or earn. For a lot of businesses that’s the difference between comfortable and constantly checking the bank balance on Thursday.

You reduce churn at the riskiest moment. The gap between “I bought” and “I got something” is where buyer’s remorse lives. Every day in that gap is a day for the client to wonder if they made a mistake. Shorten the gap and you kill the doubt before it forms.

You learn faster. Every completed cycle is a data point. Half the cycle time means twice the loops, twice the feedback, twice the improvement. Compounding works on iterations, not on calendar time. A business that runs thirty cycles a year gets better twice as fast as one running fifteen, even if both have been open the same number of years.

You win deals on it. Nobody sells against speed. Your competitor is pitching quality and price. You show up and say we start Tuesday and you’ll have something in your hands by Friday, and you have just made price a secondary conversation. Speed is a differentiator almost nobody is defending, because almost nobody has measured it.

That’s four returns on one fix. And unlike a hire, it doesn’t come with payroll tax.

Here’s the whole thing. It takes about ninety minutes to run the first time. You can do it this week.

Do not try to audit your whole business. You will get overwhelmed and quit by Wednesday. That’s not discipline failure, that’s scope failure, and it’s on the design of the exercise, not on you.

Pick one repeatable process that touches revenue directly. For most people it’s one of these:

Choose the one that feels sloppiest. Your gut is usually right about which one is bleeding, and if your gut is wrong you’ll find out in step three anyway.

Write down exactly what starts the clock and exactly what stops it. Be obnoxious about this. “When the project kicks off” is not a definition. “The timestamp on the signed contract PDF” is a definition.

Then pull your last twenty to thirty instances of that loop and record two dates for each. Start and stop. That’s it.

You do not need software for this. A spreadsheet with three columns and thirty rows will tell you more than most operators learn in a year. If your systems can’t easily tell you when things started and finished, write that down too, because that’s a finding.

Now calculate your average. Then find your worst case. The worst case matters more than you’d think, because that’s the one the client tells people about.

This is the step that does the work, and it’s the one people skip because it requires talking to humans.

For five of those instances, walk the path backward with whoever touched it. Ask a simple question at every stage: how long did this actually take you, and how long did it sit before you got to it?

Build two columns. Touch. Wait.

You are looking for the gaps. The three days a proposal sat waiting for you to approve pricing. The week between kickoff and the first working session because that’s when calendars aligned. The four days a deliverable sat in review because review is nobody’s actual job.

Add up the wait column. That number is your opportunity, and it’s usually large enough to be uncomfortable. Good. Uncomfortable is useful.

If you want the touch time half of this to be honest rather than remembered, this is where a real time tracker earns its keep. Most people guess at their own hours and guess badly, usually in the flattering direction. I use Rize for this. It runs in the background and tells you where your hours actually went instead of where you thought they went. For a cycle time audit that’s the difference between a real number and a comfortable story.

Here’s where most people blow it. They look at the audit, find the stage that takes the most labor, and try to optimize that.

Wrong move. Optimizing a task that takes six hours of touch time inside a stage that has nine days of wait time is rearranging furniture in a house that’s on fire.

Find your single largest wait block. One. Then ask what it’s waiting on. It’ll be one of four things, essentially always:

Each of those has a fix, and three of the four are free.

Decision waits get killed with pre-authorization. Write down the conditions under which your team can proceed without asking you. “Anything under five grand with standard terms, go.” You just deleted three days.

Calendar waits get killed by removing the meeting or standing the meeting. Either the step doesn’t need synchronous time and you kill it, or it needs it every single project and you put a recurring slot on the calendar so nobody is ever scheduling from scratch.

Information waits get killed at the front. Every piece of information you need from a client, you ask for in one batch, before you need it, with a deadline. Not as you go. Every “oh and can you also send” is another two day round trip.

Capacity waits are the only ones where you should think about hiring. And now when you do hire, you’ll know exactly which stage to hire into instead of guessing.

“My work is custom. Every project is different.”

Sure. And every one of them still has a proposal stage, a kickoff, an approval, and a delivery. The content varies. The shape doesn’t. Audit the shape.

Also, I’d gently point out that “every project is different” is the most common thing operators say right before they discover that eighty percent of their projects follow one of three patterns. Custom is often a story we tell because it feels more valuable than repeatable. Your clients don’t care whether it’s custom. They care whether it’s good and whether it’s on time.

“The client is the delay. I can’t control them.”

Partly true and mostly a cop out. Client delays are a design problem. If your process gives a client four separate opportunities to go quiet on you, they will use all four. If it gives them one, with a clear deadline and a clear consequence, most people respond.

Batch your asks. Set default decisions. “If we don’t hear back by Thursday, we proceed with option B.” That single sentence in your process documents has saved businesses I know weeks per project. Clients are not offended by it. They are relieved by it, because you just took a decision off their plate.

“We’re already fast.”

Then the audit takes ninety minutes and confirms it, and you go into every sales conversation from here on out with a hard number instead of an adjective. “We’re fast” is what everybody says. “Our average from signature to first deliverable is four days, and here’s the data” is what nobody says. That’s worth ninety minutes on its own.

You almost certainly do not have a time problem. You have a waiting problem wearing a time problem’s coat.

Your business has a speed limit, and it isn’t set by how hard your people work or how many of them there are. It’s set by how long things sit still between the moments somebody touches them. That number is measurable, it’s usually much worse than you think, and it’s fixable in weeks rather than quarters.

My friend, by the way, didn’t make the two hires. He killed three approval bottlenecks by writing down what his team could decide without him, moved kickoff calls to two standing slots a week, and batched his client information requests into a single onboarding form.

Eleven days to four. Same team. Same building. Nine weeks.

He hired one person eventually, six months later, into the one stage that turned out to be a genuine capacity constraint. Cost him half of what he was about to spend, and it actually worked, because by then he knew where the problem was.

Open a spreadsheet. Three columns: start date, end date, days elapsed.

Pick your signature to first deliverable loop, or whichever one made you wince when you read the list. Pull your last twenty. Fill it in.

Do not analyze it yet. Do not fix anything. Just get the number and sit with it for a day.

Twenty minutes. That’s the whole assignment. The number you get will tell you more about why your business feels stuck than another quarter of working harder ever will.

Refined. Relentless. Unapologetic.

Marcus