Why AI deliverables should be judged by outcomes, not effort

A client receives two deliverables…

Both solve the problem they were hired to solve. Both are accurate and useful, and they lead to the same business outcomes. The client is happy with the work and sees no meaningful difference in the results.

Then they learn that one deliverable took 20 hours to create while the other took 20 minutes. Now the questions start rolling in:

• Was AI involved?
• Should the faster deliverable cost less?
• Is the person who completed it somehow less skilled because they found a way to work more efficiently?

What’s interesting is that most of us have completely different reactions to AI depending on which side of the transaction we’re sitting on. We love using AI to save ourselves time, but many become uncomfortable when they’re the customer and discover AI was used to create something they purchased.

I recently ran a LinkedIn poll asking a simple question: If the outcome is great, do we really care how it was made?

The responses reinforced something I’ve been thinking about for a while. The biggest objections people have to AI often have little to do with quality.

The time vs. value fallacy

I think part of the discomfort comes from the fact that we’ve spent decades connecting value to effort.

• Long hours feel valuable.
• Fast work feels suspicious.
• Struggle feels like expertise.

The harder something appears to be, the easier it is to justify its price.

The story is about a ship engine that stopped working. After multiple attempts to repair it, the owners brought in an engineer with decades of experience. He inspected the engine, tapped it once with a small hammer, and the machine roared back to life.

His invoice was $10,000.

The owners were furious and demanded an itemized bill.

The response:

• Hammer tap: $2
• Knowing where to tap: $9,998

The debate whether this is a true story or just a fun tale that people like me use to validate value-based pricing. Whether the story is true almost doesn’t matter. The lesson does.

People aren’t paying for the tap. They’re paying for the expertise behind it.

That’s what makes AI such an interesting topic. It forces us to confront a question many of us have avoided for years:

• Are we paying for expertise or for visible effort?

Those aren’t always the same thing.

The objections that actually matter

To be clear, not all objections to AI are bad ones. I certainly haven’t had an issue sharing my opinion.

In fact, I think some of the strongest arguments against AI have very little to do with how quickly something was created.

These are all legitimate concerns, and what’s interesting is that none of these concerns has much to do with how long it took to create the deliverable.

They’re questions of trust.

• Can the output be trusted?
• Can the recommendation be defended?
• Can someone confidently stand behind the work if it’s questioned six months…