Revenue can hide the capacity consumed by avoidable operational failure.
The account looked healthy.
Revenue was on plan. The client relationship was stable. The work was moving. In the monthly commercial review, there was no obvious reason to worry.
Then someone looked past the account total and into the work itself.
Briefs were arriving incomplete, so teams filled the gaps. Assets came back for another round because an approval had been assumed rather than confirmed. Reports were rebuilt when data did not reconcile. Account managers chased decisions across email, chat and meetings. Senior specialists stepped in late to protect deadlines.
None of these events looked dramatic on its own. Each was absorbed as part of serving the client.
That was the problem.
The dashboard counted the revenue and the planned delivery effort. It did not count the repeat work, the recovery work or the management attention required to keep the account looking healthy.
An account can look profitable when avoidable work is treated as normal service.
Revenue is not profit. And activity is not cost.
Rework consumes capacity that could have served another customer, improved quality or reduced pressure on the team. It can turn a reasonably priced engagement into a fragile one while everyone continues reporting that the account is “busy.” Busy is easy to see. Cost-to-serve is harder.
This does not mean every revision is waste. Client changes, creative refinement and legitimate learning can be part of the value being purchased. Rework is different. It is effort repeated because an input was incomplete, a control was missed, a decision was unclear or a preventable defect escaped downstream.
If those categories are not defined, the organization cannot distinguish a demanding account from a poorly managed operating system.
The answer is not another layer of timesheet bureaucracy. It is enough operational visibility to see the pattern. Where is work coming back? Why? Who owns the handoff? Which causes are internal, which are client-driven and which are built into the commercial model? What does the account actually consume once exceptions and senior rescue are included?
That visibility should change the management conversation. Roles clarify who can reject incomplete inputs. Processes establish acceptance criteria. Tools provide one place for decisions and evidence. Meetings address recurring causes instead of celebrating recovery. Reporting shows cost-to-serve, not only revenue. Analytics identifies where margin leaks. Continual improvement removes the demand that should not exist.
The commercial question I would put on the table is simple:
If we priced this account today using the work it actually consumes, would we accept the same terms?
If the answer is no, the issue may not be the client or the price alone. It may be the management architecture around the work.
If this sounds familiar, my book, The 7 Essential First-Line Management Systems, goes deeper into the practical systems that make work, accountability and improvement visible. You can explore it at https://www.imadlodhi.com/flm1.
