Measure AI by profit, not by productivity
Productivity is AI's comfortable metric, it always looks good and commits to nothing. We prefer the uncomfortable one, which concrete gain did the system move.
Almost every AI project justifies itself with the same word, productivity. It is a comfortable metric. It always looks good, nobody audits it, and it commits to nothing. “The team is more productive” is a sentence you can neither invoice nor refute.
We prefer the uncomfortable metric, which concrete gain did the system move. Hours that stopped being paid to a mechanical task. Inquiries that used to go cold and now get closed. A service that could not be offered before and now can. If we cannot point at the gain, we do not defend the project.
Fuzzy productivity is the symptom of a fuzzy project
When a project can only justify itself with generic productivity, it is usually because nobody defined what it was supposed to move. The capability got built, “now we have an assistant”, instead of the outcome being pursued, “inquiries get answered in minutes and the team closes more viewings”.
The difference shows in our own cases. At the real-estate agency we work with, the measure is not “the team moves faster”. It is more than three hours a day that stopped going into screening inquiries, each one previously costing five to ten minutes of manual checking. At the property manager, the measure is that invoices stopped being typed. Small, concrete figures. They can be checked, which is why they count.
How to buy AI with this yardstick
Our method starts there, and it is sometimes uncomfortable. The first phase is not choosing technology, it is mapping where it hurts and translating every candidate use case into its expected gain. The second is discarding. Of all the cases AI “could” solve, most usually do not make the cut. Either the gain is fuzzy or the case is not viable yet. If something does not pay off, we say so before invoicing it, because a project without a defined gain is exactly the kind that dies at month six. And the ones that do launch still face the second exam, staying alive.
This also changes budget conversations. A system that saves three hours of qualified work a day defends itself in front of any finance director. A system that “improves team productivity” competes with everything else that also improves it, from a second monitor to a better chair.
The transformation that multiplies
There is a deeper reason to be demanding about the metric. Digital transformation was largely additive, each tool contributed its saving. AI transformation, done well, is multiplicative. A system that filters inquiries does not just save the screening hours, it changes what the team can do with its day, and that changes how many deals fit in a month. Precisely because the potential is multiplicative, measuring it with an unauditable metric wastes it.
Productivity comes anyway, and we do not dismiss it. But it comes as a consequence, not as the justification.
The question fits in any meeting. What concrete gain did this system move last month? If the answer starts with “productivity”, you are hearing once more the sentence that can neither be invoiced nor refuted.
If you have a concrete process where the gain can be pointed at, start with AI workflow automation. If you are still deciding where to apply it, the AI agents guide covers how to separate the cases that pay off from the ones that do not. The other half of that sum is what the system costs, and we break it down in the cost guide.