Reducing a tool's cost to zero means replacing its utility with something else, often at a higher cost. It moves the burden, but the burden remains.

Example: A software team finds that removing a SaaS dependency requires engineers to spend an additional five hours per week on manual configuration and debugging. The SaaS cost is gone, but the work is not.

When you eliminate a tool that increased accepted work by 30% for $200 per engineer, you create a deficit. Filling this gap with labor means more hours worked at a significant increase in total cost.

Example: A department maintains the same output after cutting a productivity tool. Unseen, each employee now works 10 additional hours weekly, making the actual cost of delivery much higher.

Focusing solely on reducing a bill to zero ignores the value that spend unlocked. A healthy metric shows the return on investment, not just the reduction in expenditure.

Example: A team stops using a valuable mapping service to eliminate its cost. Delivery remains "flat" because the team compensates by spending two days per week manually verifying addresses, reducing available capacity for new features.

Shifting costs to different budgets or forcing employees to absorb expenses does not make the costs disappear. It makes them invisible to the balance sheet, but immediately apparent to those paying the price.

Example: BYOP — Bring Your Own Power — moves laptop charging to employees under the slogan “Your power. Our productivity.” The electricity disappears from Facilities and reappears in kitchens, battery banks, and idling cars.