top of page

Revenue Can Be Growing While the Business Is Getting Harder to Run

3 days ago
7 min read
Modern office scene with ascending blocks, plants, binders, and Provident Solutions Group branding, representing business growth and operational scalability.

Revenue growth is worth celebrating. But revenue alone does not tell you whether the business is actually getting stronger.

I get more curious about operations when a company is growing quickly — not less.

A strong revenue month can make almost everything look healthier than it really is.

Sales are up.The pipeline is strong.New customers are coming in.The team is busy.Leadership feels momentum.

Those are all good things.

But they are only part of the picture.

When revenue increases, I want to know what came with it.

Did accounts receivable grow faster than collections?

Did overtime increase?

Did margins hold?

Did customer issues rise?

Did onboarding slow down?

Did the backlog become harder to manage?

Did managers absorb the additional volume without losing control?

And most importantly:

Did the company add revenue that its current operating model can actually support?

Because growth and operating health are not the same measurement.

A company can generate more revenue while simultaneously becoming slower, harder, and more expensive to run.

That is why I would never look at the top line alone and conclude that the operating model is working.

Growth Creates a Bill

Every new dollar of revenue asks something from the organization.

Sometimes it requires more labor.

Sometimes it requires inventory, equipment, working capital, technology, customer support, administrative capacity, or additional management attention.

And almost always, it requires more coordination.

More communication.

More decisions.

More handoffs.

More opportunities for something to fall through the cracks.

Most businesses know how much revenue they sold.

Far fewer can quickly explain the operating demand created by that revenue.

That becomes a problem when growth moves faster than the company's ability to understand the cost and complexity of serving it.

In founder-led and service businesses, that strain does not always appear immediately on the income statement.

It usually shows up in behavior first.

People start working later.

Customers need more follow-up.

Billing requires more cleanup.

One manager suddenly carries twice the coordination load.

Processes that used to work consistently begin producing exceptions.

Leadership starts solving problems that previously resolved themselves.

One of those issues by itself may not mean much.

When several start happening at the same time, leadership should pay attention.

Is Growth Producing Cash — or Consuming It?

Revenue is not cash.

That sounds obvious until a growing company realizes how much money can sit between making a sale and collecting the payment.

A new customer may require labor today.

Materials today.

Payroll today.

Subcontractors today.

Customer support today.

But the cash connected to that work may not arrive for 30, 60, or even 90 days.

If that gap grows as the company grows, the business can appear successful while becoming increasingly cash constrained.

That is why I want to look beyond revenue and ask:

  • How much accounts receivable is outstanding?

  • How old are those receivables?

  • How much completed work has not yet been billed?

  • How many invoices are disputed?

  • How quickly are completed jobs being invoiced?

  • How long does collection take?

  • Are write-offs increasing?

  • Is cash conversion improving or getting worse?

These are not just Finance questions.

They are operational questions.

A billing delay may be a process problem.

A disputed invoice may point to a communication or documentation problem.

Unbilled work may indicate a handoff problem.

Slow collections may expose issues much earlier in the customer lifecycle.

The speed at which revenue becomes cash tells you a lot about how well the business is operating.

What Happened to the Margin?

A company can grow itself into worse economics.

Revenue increases, but producing that revenue requires more:

  • Overtime

  • Rework

  • Supervision

  • Expedited purchases

  • Subcontracting

  • Customer concessions

  • Support staff

  • Management intervention

The top line looks better.

The economics underneath it do not.

This is why I prefer looking at growth in pairs.

Revenue and gross margin.

Revenue and overtime.

Revenue and labor utilization.

Revenue and customer acquisition cost.

Revenue and cost to serve.

Revenue and rework.

That second number often tells you what the first one is hiding.

For example, a 20% increase in revenue sounds great.

But if overtime increased 40%, margins dropped, customer complaints doubled, and leadership is spending every Friday fixing billing problems, the company did not simply become 20% stronger.

It became bigger.

Those are not necessarily the same thing.

Can the Business Actually Absorb What Sales Is Selling?

Most businesses have some form of sales pipeline.

I also want an operating pipeline.

The sales pipeline tells us what we hope to win.

The operating pipeline answers a different question:

What happens if we win it?

Do we have the labor?

Do we have management capacity?

Do we have the equipment?

Do we have the inventory?

Do we have onboarding resources?

Do we have scheduling capacity?

Do we have the working capital?

Do we have the customer-support bandwidth?

Do our systems and technology have enough capacity?

And if we do not have those things today, when will we?

This is where growth planning becomes operational planning.

A company can sell work much faster than it can build the capability required to deliver it.

That gap creates risk.

It can leave the business with more demand than its current systems can absorb but not enough time to build the missing capacity thoughtfully.

The result is usually a collection of expensive short-term responses:

Rushed hiring.

Excessive overtime.

Emergency outsourcing.

Training shortcuts.

Schedule compression.

Lower selectivity.

Last-minute purchases.

More executive involvement.

None of those responses is automatically wrong.

Sometimes they are exactly what a business needs to do.

But leadership should be making those tradeoffs intentionally — not discovering them after the revenue has already been committed.

Watch the Exception Rate

One operating indicator I pay close attention to is something many companies do not formally track:

How often does normal work require an exception?

Special pricing.

Manual billing adjustments.

Schedule overrides.

One-off workflows.

Customer escalations.

Manual spreadsheets.

Executive approvals.

Technology workarounds.

Emergency staffing changes.

A certain amount of exception handling is normal.

The question is what happens as volume increases.

If the business doubles its revenue and also doubles the amount of managerial improvisation required to deliver it, the company has not necessarily scaled.

It may have simply become busier.

A scalable operating model should allow more work to move through the organization without requiring a proportional increase in executive intervention, manual fixes, and special circumstances.

When exceptions begin growing faster than volume, I want to understand why.

Because eventually, exceptions become the operating model.

Information Has to Scale Too

Another warning sign appears when the company is growing faster than its reporting.

At a smaller size, leadership can often run the business through proximity.

The owner knows the customers.

The leadership team knows which projects are behind.

Someone remembers which invoice has not been paid.

Managers know who is overloaded.

Everyone knows where the bottleneck is because they can see it.

Growth weakens that advantage.

More employees.

More customers.

More projects.

More locations.

More systems.

More transactions.

At that point, operational information has to move through reliable systems instead of through memory and proximity.

If reporting does not mature with the organization, leadership begins managing from partial information.

Revenue might be current.

Operational reality might be three weeks behind.

That is when surprises get expensive.

Five Numbers I Would Put Beside Revenue

Every company is different, so I would not prescribe one universal dashboard.

But when a business is scaling, I want revenue sitting beside measures from at least five categories.

1. Margin

Is the economic quality of the revenue holding?

Revenue growth is much more meaningful when the company can maintain or improve the economics behind it.

2. Cash Conversion

Is earned revenue turning into cash at the expected speed?

Watch receivables, invoicing speed, collections, disputes, and working-capital requirements.

3. Capacity

How much of the organization's delivery capability is already committed?

Look at labor, schedules, equipment, inventory, management bandwidth, and any other resource that limits delivery.

4. Labor Pressure

Is the team absorbing growth sustainably?

Watch overtime, utilization, vacancies, turnover, management span, and workload.

5. Quality and Exceptions

Is additional volume producing more problems?

Track rework, complaints, delays, refunds, concessions, escalations, and manual intervention.

Put those categories beside revenue and leadership gets a very different picture of the business.

Instead of asking only:

“Are we growing?”

You can ask:

“Are we growing in a way the organization can sustain?”

The Goal Is Not to Slow Growth

None of this is an argument for becoming afraid of growth.

Quite the opposite.

Growth creates opportunity.

It creates resources.

It creates career paths.

It can strengthen market position and increase the long-term value of the company.

But growth also changes what the organization requires.

The systems that supported a $5 million company may not support a $10 million company.

The management structure that worked with 20 employees may not work with 50.

The reporting cadence that felt sufficient when the owner knew every customer personally may become dangerous when hundreds of transactions are moving through the business.

Growth eventually asks the company to become a different organization.

The leadership question is not simply:

Can we sell more?

It is:

Can the company absorb more while protecting the margins, cash flow, customer experience, accountability, and operating discipline that made the growth attractive in the first place?

Those are very different questions.

And the faster the answer to the first question becomes “yes,” the more important the second question becomes.

A Simple Operating Health Check

The next time your company reports a particularly strong revenue month, celebrate it.

Then take another ten minutes and ask:

What happened to margin?

What happened to cash?

What happened to overtime?

What happened to capacity?

What happened to the exception rate?

What happened to customer delivery?

What happened to management workload?

If those indicators are healthy too, you may have something genuinely scalable.

If several of them are moving in the opposite direction, revenue may only be telling half the story.

Growth should make the business more valuable — not simply more complicated.

Is Your Growth Exposing Operational Gaps?

Strong sales can hide weak processes for a surprisingly long time.

If your company is growing but leadership is spending more time fighting fires, chasing information, correcting handoffs, or solving issues that should already have an owner, the problem may not be demand.

It may be the operating model underneath it.

As a Fractional COO / Integrator, I help leadership teams build the structure, accountability, processes, reporting, and operating cadence needed to support the next stage of growth.

If the business is growing faster than the systems behind it, let's talk.

Comments


bottom of page