
A back-of-napkin framework for putting a number on the busywork nobody's measured yet.
Nobody has measured this
Ask a team how much time they lose to repetitive work and you will get a shrug and a guess. The work is spread thin enough across enough people that it never shows up as a line item, which is exactly why it survives.
A rough framework
Take one recurring process. Count how many times it runs a month, how long each run takes, and how many people touch it. Multiply it out and apply a loaded hourly cost. The number is almost always larger than anyone expected, and it is almost always an undercount.
It undercounts because it misses the expensive part: context switching, the errors that get caught late, and the single person who becomes a bottleneck because only they know the exceptions.
What to do with the number
Don’t use it to justify a purchase. Use it to pick which process to fix first. The largest number is rarely the right starting point — the most annoying one usually is, because that is the one people will actually help you change.
01
Keep reading
More from the blog
Give your team its time back.
Start your 14-day free trial. No credit card required, and most teams launch their first agent in under 10 minutes.
Lumora
The AI workspace that gives your team its time back.


