Hourly billing hates Productivity

by Sep 27, 2022

Why hourly billing isn’t working anymore.

It hates productivity. There is no incentive to improve it.

Suppose we define increasing productivity: fewer hours for the same result.

So, what would happen if we bought a tool for €1000 that reduces our work by 20%? You think that would be a good deal, don’t you?

But the result is that you can invoice 20% less! Doesn’t sound like a good deal now anymore, isn’t it?

A quote which describes this so simply:

IF you bill yourself out by the hour
AND you increase your productivity
THEN you lose money

Jonathan Stark

Hourly billing hates Productivity!

Subscribe to
The Daily Friction

A daily newsletter on automation and eliminating friction

Related Content

SpecFlow: Great concept, flawed execution.

SpecFlow: Great concept, flawed execution. SpecFlow, a BDD framework designed to make writing scenarios a breeze for requirement analysts. The problem: It falls short of its promise. ❌ The reality? Analysts rarely, if ever, write the specs themselves. Instead,...

read more

What if…? Production has a Staging slot.

What if...? Production has a Staging slot. Staging or QA environment needs to be the same or as close to production as it can be. Preferably, you want to restore a recent backup 💾 from Production as Staging and then deploy your changes 🔄. Kudos 👏 if you've fully...

read more

UUID v7 coming in .NET 9

UUID v7 coming in .NET 9 For those that didn't know, you can create Guids in different ways (algorithms). System.Guid supports UUID v4 out-of-the-box, the most used version. UUID v7 is now added, which creates Guids based on the current time. This means Guids can be...

read more