Software is one of the largest and fastest-growing lines of operating expense at most companies. It is also one of the least understood at the leadership level. The people who could act on it often cannot see it, and the people who can see it often cannot act on it.
This is not an oversight by any one person. It is a structural gap, and the waste tends to collect right in the middle of it.
Two leaders, two blind spots
Consider the two executives who might own this problem.
Finance leadership sees the total. They know how much the company spends on software in aggregate, because it shows up in the budget. What they usually cannot see is the composition: which tools, which teams, which overlaps, which renewals are avoidable. To them software is a large, somewhat fixed number that gets approved once a year and then becomes a sunk cost. They are rarely close enough to the detail to know that a chunk of it is duplicative or dormant.
Technology leadership sees the tools. They know what the organization runs and why. What they usually do not carry is direct accountability for the profit-and-loss impact of all of it. Cost efficiency is somebody else's headline metric. So the person who understands the stack is not measured on trimming it, and the person measured on cost does not understand the stack.
Between those two vantage points is a gap, and software spend falls straight into it. Neither leader is ignoring the problem. Each simply sees only half of it.
The correlation nobody draws
The unlock, when it happens, is almost always the same: someone finally connects the software detail to the financial impact in a way both sides can see at once. When a leader can look at the portfolio and see not just what the tools are but what they cost the business, and not just the total spend but where inside it the waste sits, the problem stops being abstract. It becomes a number attached to a decision, and numbers attached to decisions get acted on.
Until that correlation is drawn, software spend stays in a strange limbo. Everyone agrees it is large. No one owns reducing it. And the annual approval quietly rolls forward, because challenging it would require a level of visibility that neither the finance side nor the technology side has on its own.
Whose problem this really is
If you are trying to get software spend taken seriously, the practical lesson is to aim higher and to speak in the language of the profit and loss. The message that resonates is not a feature list. It is a clear line from the software detail to the financial outcome, put in front of the person whose performance is measured on that outcome.
The waste is not hiding because it is small. It is hiding because it sits in the seam between two leaders who each see only part of it. Close that seam, show the whole picture to the person accountable for the number, and the problem that fell through the gap finally has an owner.