AI has been positioned completely wrong. It gets sold as a way to do less, cut headcount and save money, and that's the smallest return you can get from it. The companies winning with AI are using it to get twice the output from the same people, and they measure it in revenue per headcount, not dollars saved.
This is my opinion, and I know plenty of smart operators disagree. Here's why I hold it.
Why the cost-cutting pitch falls flat
The cost-cutting case sounds clean on a slide. Automate a few tasks, eliminate a few seats, and the savings pay for the software.
In practice, three things go wrong.
First, the savings are a one-time event. You cut a role, the number drops once, and then it's flat. Nothing compounds.
Second, your team hears the message loud and clear. The moment AI becomes the thing that takes jobs, your best people stop suggesting where to use it. They're not going to volunteer the list of tasks that could make them redundant.
Third, you end up with the same revenue and fewer people to chase the next dollar. That's not a growth plan. It's a shrink plan with better tools.
I've watched founders chase this and come back a year later with a modest savings line and a team that doesn't trust the rollout. I've watched others freeze entirely and call it being cautious. Neither one grew.
What the multiplier looks like on paper
Run the math on a simple example. Picture a 10-person operations team. Every one of them works 40 hours, and if you watch a normal week, about half of those hours go to work that only needs effort: scheduling, confirming, updating, copying data from one system to another.
That's 200 hours a week of effort work across the team.
The cost-cutter looks at that number and sees 5 seats. Cut them, bank the salaries once, and ask the other 5 to cover the same volume with new software. Revenue stays flat at best.
The multiplier looks at the same 200 hours and sees capacity. Keep all 10 people. Let AI carry most of the effort work. Now those hours go to the things only a person can do: calling the customer who's about to churn, pricing the tricky job, following up on the proposal that went quiet.
Same team. Same 40 hours. Twice the output. That's the multiplier effect, and at the end of the day it's the only AI math I care about.
Split every role into two buckets
The framework starts with one role, not the whole company.
Pick a role that's stretched. A logistics coordinator is a good example. In a normal week that person is scheduling jobs, confirming appointments, chasing updates and answering customer follow-ups.
Now split that week into two buckets:
- Judgment work. Handling the upset customer, deciding which job gets priority when two crews cancel, spotting the vendor who's about to become a problem.
- Effort work. Sending the confirmation, updating the status, drafting the follow-up, copying data from one system to another.
AI goes after the second bucket. The person keeps the first bucket and gets more time for it. That's where your revenue lives, because judgment is what customers pay for and what keeps them coming back.
Measure revenue per headcount, not dollars saved
If you measure AI by cost saved, you'll make cost-saving decisions. If you measure it by revenue per headcount, you'll make growth decisions.
The tool calls this ROAI: revenue generated divided by the cost of the employee. The goal is to move that number up while the headcount stays steady. You're paying the same dollar for twice the output.
Two more rules keep this honest.
Buy the commodity, build the advantage. Off-the-shelf tools handle scheduling, drafting and bookkeeping just fine. Save your real money for what makes you different.
Security before speed. Set the policy, the governance and the access rules first. A fast rollout that leaks customer data costs more than any savings it produced.
What to do this week
You can do this in one leadership meeting.
- Pick your single most stretched role.
- Ask the person in it to list everything they did last week, task by task.
- Mark each task "judgment" or "effort."
- For the top three effort tasks, ask: "Is there a tool we could buy today that handles this?"
- Write down what that person would do with the hours that come back. Be specific.
If step 5 is blank, stop. You don't have an AI problem yet. You have a clarity problem about what that role is for.
AI Multiplier
The AI Multiplier walks you through the four principles (output over ease, the role audit, buy vs. build, security first) and runs the numbers on a real role. Start with one position, sort the tasks, and see what the capacity gain looks like before you spend a dollar on software. It takes a few minutes and gives your leadership team a concrete starting point instead of a vague AI initiative.
Open the AI Multiplier →Get the next lesson in your inbox
Short, practical lessons like this one for founders running $1M–$20M companies, plus every new free tool before anyone else.
If this is the call in front of you, let's talk it through.
A focused 30-minute conversation. No pitch. Just a direct discussion about the decision and whether I can help.
Book a call with Danny →
Danny Feldman is a 3× founder and the advisor behind Feldman Advisory. He founded and scaled Stellar to $100M in annual revenue across 15 states, raised $55M+ as a founder, and used AI to double revenue before exiting to private equity. Earlier, he recruited and trained 55,000+ sales reps at Cutco and grew a division from 1 to 58 locations. Operator to operator, he now helps founders of $1M–$20M companies get out of the middle of the business, build the leadership team, and raise capital. Book a 30-minute call →