If you're spending $5K on basic operational necessities (email, security patches, backup systems), calculating ROI is theater. These aren't investments, they're cost of doing business. You don't calculate ROI on your building's fire suppression system.
If you're implementing mandatory compliance requirements, ROI calculations are irrelevant. You either comply or you face penalties. The "return" is avoiding regulatory consequences, not generating business value.
If you're fixing something that's actively broken and costing you customers or revenue, the ROI is "we stop bleeding money." You don't need a spreadsheet to justify stopping a hemorrhage.
But here's when ROI accountability absolutely matters: When you're spending $50K+ on projects sold as "strategic." When vendors promise "transformation" or "competitive advantage." When IT proposes major platform changes or new capabilities. When the business case is "everyone else is doing it" or "we need to modernize."
The difference between $20M to $100M companies that use technology as leverage versus those that let it become a cost center? They can answer this question for every major IT investment: "What specific business outcome changes if we spend this money, and by how much?"
I've watched companies spend $200K on systems that delivered zero measurable business value because no one asked that question upfront. Not "Will this be useful?" but "What metric changes, and can we track it?"
Strategic IT leadership isn't about denying investments, it's about ensuring every significant dollar has a defensible business case before you spend it, not just a hopeful one.
What IT investment are you being asked to approve without clear ROI?
Want to talk through how this applies to your company?
Schedule a conversation