When revenue grows but the cash does not follow

Gross margin, contribution margin, operating margin, and cash conversion answer different questions. A single percentage cannot tell you whether the problem is price, direct delivery cost, overhead, or the time between paying for work and collecting from the customer.

Reconcile the income statement to cash before choosing an intervention. If gross margin is stable but cash is deteriorating, working capital or overhead may be the constraint. If gross margin falls as revenue grows, inspect price, mix, scope, and delivery before making broad expense cuts.

• Bridge revenue to gross profit by price, volume, and mix.
• Measure direct cost and rework by customer or offer where possible.
• Separate recurring delivery requirements from one-time acquisition cost.
• Track billing terms, receivables, inventory, and work in progress alongside margin.

Company averages allow a weak customer, service line, or contract structure to hide behind healthier work. Rank accounts and offers by the profit they contribute after the costs required to serve them, then inspect the tails. The point is not to create false precision; it is to find where volume and value have separated.

Include costs that accounting systems often distribute broadly: senior intervention, expedited work, custom reporting, repeated change requests, and the idle capacity created by uneven workflows. A large account can be strategically important and economically poor at the same time. That is a decision to make explicitly, not a fact to discover accidentally.

Cost reduction feels more controllable because it can be authorized internally. But if the offer has expanded while price remained fixed, cuts ask delivery to absorb the same promise with fewer resources. That may improve a monthly statement while weakening retention and future pricing power.

Test whether the company is charging for the scope it now provides. Examine discount patterns, exceptions, renewal increases, and the gap between standard work and what customers actually request. A price decision should specify which customers, which offer, what changes in scope, and what evidence would cause the company to revise it.

Sometimes the price is defensible and demand is real, but the path from sale to delivery forces expensive work through a narrow capability or approval point. Hiring more people everywhere or cutting the apparently idle team can make the imbalance worse.

In BridgeStride’s software-company case, projects were late while some capability sat idle and another was overwhelmed. The decision changed intake and flow and added capability at the actual constraint. Gross margin later moved from 17% to 31% without layoffs. That result belongs to that company; the transferable lesson is to trace the work before treating utilization as proof of excess capacity.

• Map queue time and rework, not only labor utilization.
• Identify the capability every project must pass through.
• Check whether sales promises create nonstandard delivery paths.
• Make the pricing and operating decisions together when they share a cause.