Thinking

The End of the Timesheet: Why AI Will Force Us to Rethink the Value of Engineering

For more than a century, professional services have been built around a simple assumption. Time equals value.

Lawyers bill by the hour. Consultants bill by the day. Software engineers estimate projects in weeks or months. Our commercial models have always assumed that the amount of time spent creating something is a reasonable proxy for its value.

Artificial intelligence challenges that assumption.

Today, an AI assisted engineer can produce work that might once have taken days, or even weeks, in a matter of minutes. That does not necessarily mean the work is less valuable. In many cases, the opposite is true. Faster delivery, broader analysis, more comprehensive testing, and greater consistency can all increase the value delivered while dramatically reducing the time required.

So what happens when eight hours of engineering effort is compressed into five minutes?

If we continue to bill purely for elapsed time, we risk undervaluing expertise, architecture, design thinking, validation, and the experience required to guide AI towards the right outcome. The hours worked become increasingly disconnected from the value created.

The software industry has seen this pattern before. We no longer measure computing power by how long a processor spends thinking. We measure outcomes such as transactions, storage, throughput, and consumption. AI may require a similar shift for knowledge work.

Perhaps the future is not measured in hours.

Perhaps it is measured in validated outcomes.

Imagine a world where software projects are assessed not by how long they took to produce, but by the complexity solved, the quality delivered, the risks eliminated, the testing completed, the documentation generated, and the confidence that the solution will perform as intended.

That would fundamentally change the conversation between clients and technology providers.

Instead of asking, "How many hours did this take?", we might ask, "How much engineering value was created?"

This is not simply a billing discussion. It is a broader conversation about how we measure productivity in an AI native world.

Traditional metrics such as hours worked, lines of code, and even story points were designed for human development. As AI becomes a genuine engineering partner, those measurements become increasingly disconnected from reality.

The organisations that thrive over the next decade will be the ones that develop new ways of measuring knowledge creation, decision quality, software evolution, and business outcomes, rather than simply measuring human effort.

We are entering an era where intelligence itself becomes a measurable asset.

The companies that recognise this shift first will not simply build software faster. They will help redefine how engineering value is measured in the age of AI.