Growth Problem or Efficiency Problem? How to Tell Which One You Have

A business growth bottleneck is always one of two things: you are not creating enough demand, or you cannot convert and deliver the demand you already have. Those two require opposite responses, and spending on the wrong one is the most common expensive mistake a small company makes.

The reason it gets confused is that both present identically from the founder's chair. Revenue is flat, everyone is busy, and the obvious conclusion is that you need more leads. Sometimes that is right. Often it is precisely wrong, and adding leads to a delivery problem makes everything worse while looking like action.

The four tests

You can usually settle this in an afternoon with numbers you already have.

Look at what happens to your conversion rate as volume rises. If more enquiries produce proportionally more customers, demand is your constraint and you should go and get more. If conversion falls as volume rises, you have found a delivery ceiling, and every extra lead past that point is waste dressed as pipeline.

Count how long a customer waits. Not how long the work takes, how long the job sits. If a two-hour piece of work takes nine days to come back, roughly none of that is capacity. It is queueing, handoffs and approvals, and no amount of new demand improves it.

Ask where deals die. If they die before a first conversation, that is a positioning and reach problem, which is the growth half. If they die after a demo, or after a proposal, or during onboarding, that is a delivery and process problem wearing growth clothing.

Ask your team what they would fix. This one is unscientific and startlingly reliable. The people doing the work know exactly which step is broken. They have usually mentioned it, and it has usually been deprioritised in favour of something with a revenue number attached.

Why the wrong diagnosis is so expensive

Treating a delivery problem as a growth problem costs you twice.

You spend money on demand generation, which works, so more people arrive. They arrive into the same broken onboarding, so a larger number of customers have a worse first experience. Your churn rises, your reputation takes the hit at exactly the moment more people are watching, and the team that was already stretched is now stretched across more work.

The cruel part is that the growth spend will look like it failed. It did not. It did its job and delivered demand into a system that could not hold it, and the conclusion most founders draw is that the channel does not work, so they try another one.

The reverse mistake is real but cheaper. Optimising delivery when you have no demand produces a beautifully efficient business that nobody buys from. You will notice within a quarter, because the absence of customers is loud in a way that a broken handoff is not.

The order that usually works

Fix the constraint that is binding now, then the other one, then re-test.

If delivery is the constraint, map the process end to end before changing anything. You cannot fix a handoff you cannot see, and in most small companies the whole picture has never been in one place. This is the case for building a working model of how the business actually runs rather than relying on the org chart, because the org chart shows reporting lines and the problem is almost always sideways. It is free and a first pass takes about ten minutes.

If demand is the constraint, the problem is rarely effort and usually clarity. Most companies with a demand problem are reaching people who do not have the problem acutely, or reaching the right people with a description they do not recognise. That is what a proper go-to-market strategy is for: ICP and positioning, the channels that fit, and a dated roadmap rather than a list of tactics, for £97 one-time.

The connection between the two halves is not a coincidence. A go-to-market plan makes promises about what happens after someone says yes. If the delivery side cannot keep those promises, the plan is fiction, and the better it is at generating demand the faster the fiction gets exposed.

What makes this genuinely hard

The honest complication is that most companies have both problems, and the answer to "which one" is a matter of degree rather than kind.

There is also a case for doing the growth work first even when delivery is the constraint, and it is stronger than efficiency people usually admit. If you are close to running out of money, a broken process that produces revenue beats a clean process that produces none. Survival is allowed to be the priority, and a founder who spends three months on operational tidiness with eight weeks of runway has made a worse decision than one who sold badly and lived.

So the test is not only which problem is bigger. It is which one kills you first.

Re-run it every quarter

The constraint moves. A company that fixes delivery becomes demand-constrained within a couple of quarters, and one that fixes demand becomes delivery-constrained almost immediately.

That is the normal rhythm of a growing business rather than a sign anything is wrong. What goes wrong is deciding once, in year one, that you are a growth-constrained company, and still believing it three years later while your onboarding quietly falls apart.