Ask your CFO what the software stack costs and you will get a real number: the subscription line, negotiated annually, benchmarked against peers. Ask what it costs to operate that stack, the re-keying, the reconciling, the exports into spreadsheets, the approval-chasing across a dozen systems, and you will get a shrug. The shrug is the software tax: the payroll your business spends working for the software instead of the business, and in most mid-market companies it is the larger half of the cost.
You cannot manage a number nobody has calculated. Here is the walkthrough, one working session with your leadership team.
Step 1: Count the systems
List every application a customer-facing process touches, from first inquiry to paid invoice. Most mid-market businesses find 15 to 40. The count itself is not the tax, but every seam between two systems is a place where a human moves data by hand, and the seams grow as the square of the systems.
Step 2: Find the operating hours
For each core role, estimate the weekly hours spent on software operation rather than judgment or customers: entering the same data twice, reconciling two systems that disagree, building the weekly spreadsheet, chasing an approval through email. Do not survey people with a form; sit with one person per role for thirty minutes and walk their week. The pattern is consistent and the estimates land quickly.
Step 3: Price the hours
Multiply hours by loaded cost per role, annualize, and put the number next to the license line. This is the moment the room goes quiet. A business with 200 employees averaging even six operating hours a week is spending roughly 60,000 hours a year working for the software. At mid-market loaded costs, that is a seven-figure line item that has never appeared in a budget review.
Step 4: Run the careers-page test
Open your own careers page and read the postings honestly. Count the roles that exist primarily to move information between systems: coordinators, processors, schedulers, reconcilers. Each one is the software tax converting itself into permanent headcount. You budgeted for software that was supposed to do work, and then hired people to operate the software.
What to do with the number
The software tax is the first of five pressure points where the AI return concentrates in mid-market businesses, and it is usually the easiest to attack because the work is repetitive, rule-bound, and nobody loves doing it. The play is not another integration project; it is rebuilding the workflow so AI does the operating and your people return to judgment and customers. The evidence, the precedents, and the sequence are in the full Software Tax chapter, published open, and the program that attacks it is in The 2026 AI Strategy. Price the tax first. Everything after that is easier to decide.
