5 min read
A signed contract feels like the end of a sales process. From the organization's point of view, it is closer to the beginning of a larger system.
The commitment still has to move through contracting, onboarding, delivery, evidence, billing, and collection before it becomes cash.
Each stage may be owned by a different team, supported by a different system, and measured by a different definition of success. Every department can be performing well on its own terms while the end-to-end outcome remains slow.
That makes revenue flow a useful example of a broader strategic problem.
The org chart hides the system
Sales owns the commitment. Legal owns contract language. Operations owns delivery. Finance owns billing and collection.
The customer does not experience those functions separately. The customer experiences one company.
Problems tend to appear at the boundaries. A term negotiated in sales is not captured in a form operations can use. Legal and finance approvals run serially. Customer information is entered into multiple systems. Delivery evidence is incomplete when billing should begin. Collections cannot see the context behind a dispute.
No single step looks catastrophic. The accumulated delay can be substantial.
Why the visible owner may not own the cause
When DSO rises or invoices are delayed, finance naturally receives the problem.
The cause may sit far upstream.
It could be the way contracts are structured, how onboarding data is captured, when delivery is considered complete, which system owns a customer attribute, or an approval rule created years ago for a different business model.
This is why functional optimization has limits. A team can improve its local process and still fail to improve the system around it.
The strategy question is end to end
A useful revenue strategy asks different questions.
Where is value actually waiting? Which handoffs create delay without changing the outcome? What information should move automatically? Who should own the full flow? Which exceptions deserve special treatment and which should be designed out? What technology changes would improve the system rather than only one department?
Those questions can lead to automation, integration, process redesign, clearer ownership, different decision rights, or a combination of them.
The point is not to create a perfect revenue process map.
The point is to identify the few changes that materially improve the outcome and sequence them into an executable strategy.
Revenue gets stuck between sales and cash because the space between departments is still part of the business, even when nobody owns it on the org chart.