All insights

Growth Can Hide a Broken Operating Model

Revenue can rise while implementation delays, working-capital needs and customer dissatisfaction rise faster.

The sales chart moves up and to the right. New customers sign each month. The company hires to keep pace and the next financing looks easier to explain than the last.

Inside the business, a different chart is forming.

Implementation takes longer. Projects wait for senior employees who understand the exceptions. Customers use only part of what they bought. Support volume grows faster than the customer count. Cash falls because suppliers and staff are paid long before invoices are collected.

Revenue is growing. The operating model is becoming less stable.

Growth does not repair a weak system. It sends more volume through it.

Watch what grows with revenue

Healthy growth should create some form of operating leverage. The business learns, delivery becomes more repeatable and each new unit of revenue requires proportionally less effort.

When every new customer requires another implementation lead, another custom workflow and more intervention from the founders, revenue is scaling labour and complexity rather than a system.

The company may still be viable. Its true model may be a service business with software inside it. The danger comes from planning as though gross margins and capacity will behave like a standardized product.

Bookings can conceal the cash requirement

A signed contract can make the future look secure while increasing the immediate need for cash.

Inventory must be purchased. People must deliver the work. Customers may pay after acceptance or on sixty-day terms. Growth therefore consumes working capital before it produces it.

A company can become less liquid as it becomes more successful. If management watches contracted revenue without mapping the full cycle to collected cash, each sales win can bring the business closer to a financing emergency.

This is one reason to separate temporary cash needs from long-term risk and choose financing that matches the problem.

The queue tells the truth

Backlogs are often described as demand. Sometimes they are evidence that the company cannot deliver what it has sold.

Look at the queues:

  • days from contract to implementation start;
  • work waiting for engineering or executive approval;
  • unresolved support issues;
  • invoices waiting on customer acceptance; and
  • customers waiting to reach the promised result.

If these queues lengthen with every sales month, the operating system is borrowing from the future.

Customer dissatisfaction often arrives late

Early customers may tolerate delay because they know the founders, care deeply about the problem or receive unusual attention.

As the company grows, newer customers encounter the standard process. They may wait longer, receive less context and discover that the product requires more internal effort than the sale suggested.

Renewal and reference behaviour reveal this gap later than bookings do. By the time churn appears, the company may have hired and forecast against customers whose adoption was always fragile.

A successful pilot is therefore only the beginning. The company must know whether the outcome repeats without heroic involvement.

Founders can become the hidden infrastructure

Many young companies work because the founders connect everything manually.

They remember what sales promised, translate it for the product team, reassure the customer and solve the exception. This can be appropriate while the model is being discovered. It becomes a constraint when no one measures the work because it happens inside the founders’ heads.

A useful test is to remove the founder from one customer journey on paper. Where does the process stop? Which decision lacks a rule? Which relationship depends on personal trust? Those points describe the operating system the company still needs to build.

Slow down the right thing

The answer is not always to stop selling. It may be to narrow the offer, sequence implementations, change payment terms, decline poor-fit customers or dedicate a period to removing the most expensive source of variation.

Management should choose the constraint deliberately. If onboarding capacity is fixed, sales can prioritize customers with the best fit and economics. If inventory is scarce, pricing and deposits can reflect it. If product reliability is the issue, adding customers may be less valuable than correcting the failure that affects all of them.

Measure the result, not only the transaction

Revenue remains essential. It proves that someone is willing to pay and gives the company resources to continue.

It becomes more informative when paired with the measures that explain how it was produced:

  • time and cost to implement;
  • time to first customer value;
  • gross margin after delivery and support;
  • cash collected and working capital consumed;
  • usage, retention and expansion; and
  • the amount of founder intervention required.

A company with slower sales and improving delivery may be becoming more valuable. A company with faster bookings and worsening economics may be financing its own confusion.

Growth is strongest when it reveals a sound operating model. When it hides one, the numbers eventually catch up.