What does searching cost? An honest DAM savings calculation

The most expensive work in many teams is the work nobody books as work: searching. Not the dramatic cases where a file is gone for good — the daily five minutes here, ten minutes there, across folders, mail attachments and shared drives.

How much that is can be quantified. According to a McKinsey analysis, knowledge workers spend around 1.8 hours a day — roughly 9.3 hours a week — searching for and gathering information. The same source, incidentally, backs the number we quote on our home page: up to 35% less search time when information is centrally findable.

The maths, laid open

To make the number tangible, here is the worked example — deliberately with every assumption visible, so you can replace them with your own:

Put differently: around 60 working days a year that do not go into projects, campaigns or client work, but into "where is that again?". Multiplied by the number of people affected, this quickly becomes a six-figure line item — one that shows up in no cost centre.

What a DAM realistically changes

A digital asset management system attacks exactly this invisible position: one central inventory instead of scattered filing, metadata and keywording instead of guessing filenames, a search that also finds what is named differently.

Assume — as an assumption, not a promise — that this cuts search effort by 80%:

• Reduced search time: 9.3 h × 0.2 = 1.86 hours per week
• Remaining search cost: 1.86 h × €23.85 × 52 weeks = around €2,330 a year
• Savings: a good €9,200 per head and year

How close your team gets to the 80% depends on the starting point — teams that already keyword cleanly save less; teams searching grown folder structures often save more. The point of the calculation is not the exact figure but the order of magnitude: search time is a real, recurring cost block, not a comfort topic.

Conclusion

Whether a DAM pays off is not a matter of belief — it is arithmetic with your own numbers: hourly rate, team size, estimated search time. Run it once and you see why search is the first argument for a DAM, not storage space. What it feels like in practice is covered in What is a DAM? — including the functions that turn the savings assumption into practice.