Revenue growth can create the appearance of progress while the economics of the business become harder to see.
That is not because revenue is unimportant. Revenue is a necessary outcome for most businesses. It is because revenue is a result, not an explanation. More revenue can arrive with more implementation effort, deeper discounting, expensive support demand, rework, custom commitments, or complexity that was not priced into the deal.
When the top line grows and margin worsens, the instinct is often to treat the margin problem as a finance problem. Finance gets asked to explain the variance, publish a more detailed report, or find an expense category to reduce. Sometimes that is appropriate. Often the economic change is being created much earlier, in commercial decisions and operating conditions that the margin report only reveals later.
The better question is not “Why is Finance missing the margin?” It is: “What work, customer mix, pricing decision, or operating condition is causing each additional dollar of revenue to produce less economic value?”
Growth is an outcome, not an explanation
A revenue number compresses a great deal of activity into one line.
Two businesses can grow by the same amount and create very different economics. One may have strong customer fit, repeatable delivery, disciplined pricing, and a cost-to-serve that stays stable as volume increases. The other may win larger accounts by making exceptions, carrying more implementation work, adding service commitments, and relying on people to solve problems manually.
Both businesses can report growth. Only one is creating the same amount of economic value from that growth.
This is why the first step is to disaggregate the outcome. Look at revenue by customer type, product, segment, channel, region, contract shape, and stage of the customer relationship. Then look at the work required to create and retain each part of the revenue. The point is not to produce an enormous profitability model that no one can use. The point is to see where the economics differ.
Useful questions include:
- Which customers are growing fastest, and which require the most non-standard work?
- Where are discounts or concessions most common?
- Which implementation or support activities are included in the commercial promise?
- Where does work leave the standard process and become an exception?
- Which customers generate expansion, and which generate recurring service effort without an equivalent return?
The OECD discussion of productivity measurement makes a similar point at a broader level: aggregate measures can hide important differences between firms and the drivers underneath performance. The same logic applies inside a company. A blended revenue number can hide the places where value is being created and the places where it is being consumed.
Look at the work underneath the revenue
Margin worsens when the work required to create revenue changes faster than the economics of the revenue itself.
That work may be visible in staffing, but staffing is only one part of the picture. It can appear as extra meetings, handoffs, bespoke reporting, manual data cleanup, escalations, rework, delayed decisions, or support commitments that were made during the sale and never converted into a repeatable operating model.
The important distinction is between work that creates value for the customer and work that compensates for a broken system. A complex implementation may be necessary because the customer’s environment is complex. Or it may be complex because scope is unclear, responsibilities are not defined, or every exception is treated as a new promise. A support team may be busy because demand is healthy. Or it may be busy because customers cannot find the right path to an answer.
Both versions show up as effort. They point to different levers.
Mapping the work means following the revenue through the operating system. Where does the customer enter? What has to happen before value is realized? Which team receives the handoff? Where does the work wait? Which decisions are repeated? Which activities are tracked as “service” even though they are really rework?
This is where customer economics becomes operational. The question is not only what the customer pays. It is what the business has to do, repeatedly, to deliver what was sold.
Find the driver before cutting the cost
Cost reduction is an intervention, not a diagnosis.
If margin is deteriorating, reducing spend may improve the reported number for a period. It may also damage the capabilities that protect revenue, increase churn, slow implementation, or push more work into another part of the organization. A lower cost line is not automatically a better business.
The driver might be customer mix. High-value customers may be expensive to serve because their contracts include complexity that was never priced. The lever could be segmentation, commercial boundaries, or a change in how service is packaged.
The driver might be discounting. Sales may be trading price for speed, access, or a reference logo, while delivery absorbs the consequence. The lever could be approval logic, deal structure, a clearer value case, or a defined exception process.
The driver might be operating rework. Teams may be doing the same work multiple times because definitions, ownership, or handoffs are unclear. The lever could be a workflow redesign, a decision right, a better input standard, or work that should stop.
The driver might be growth itself. A process that worked at one scale may now create delay and management overhead. The lever could be a different operating cadence, automation, capacity planning, or a change in where decisions are made.
Each of these situations can be described as “cost pressure.” The label is too broad to choose the right action.
Connect the change to economic effect
Once the driver is visible, make the impact explicit.
The impact may be margin, but it may also be capacity, cash flow, risk, speed, retention, or revenue quality. A change that reduces implementation effort can improve capacity before it improves margin. A change that improves pricing discipline may protect margin without changing headcount. A change that removes rework may reduce risk and create room for growth before it shows up in a quarterly financial statement.
This prevents the team from overpromising a financial result that the operating change cannot directly produce. It also helps executives see why an apparently small lever matters. A better handoff may not look like a finance initiative, but if it removes repeated work across four functions, the economic effect can be material.
The McKinsey analysis of cutting sales costs without cutting revenues is a useful reminder that customer value and service cost have to be considered together. The relevant decision is not simply to spend less. It is to understand which customers and activities create attractive economics and which operating changes can improve the relationship between revenue and effort.
Use a smaller, better economic conversation
Executives do not need a perfect answer to begin making progress. They need a shared view of the most important driver, the lever within reach, and the effect that should follow.
A focused conversation might sound like this:
Revenue grew in enterprise accounts, but margin declined because the accounts require more custom implementation and service work than our standard model assumes. The immediate lever is to separate priced implementation from ongoing service, define the exception boundary, and track time-to-value and cost-to-serve by segment. We expect the change to improve margin and implementation capacity over the next two quarters.
That statement is not a forecast. It is a testable explanation. It tells the organization what to change and what to watch.
Growth is not the problem. Unexamined growth is. When revenue and margin move in different directions, trace the outcome backward until the work, decision, or condition creating the difference becomes visible. Then choose the intervention that fits.