Every Friday afternoon, around 3pm, Patricia opens three windows on her screen. Not her real name — she asked me not to use it, and honestly, the ritual itself is more interesting than she is. One window is the point-of-sale system. One is a shipping spreadsheet three different warehouse people update throughout the week. One is the bank app, open to check which deposits actually cleared. She copies numbers from each into a fourth window: the weekly report her boss reads every Monday morning.
It takes her about ninety minutes. She knows this because she's timed it, half-joking, half-resentful. Ninety minutes, every Friday, to produce six numbers her boss glances at for maybe ninety seconds.
I want to talk about what ninety minutes a week actually costs, because almost nobody calculates it, and the real number is usually bigger — and more fixable — than people expect.
Why nobody notices the cost until someone adds it up
If you asked Patricia's boss whether the company could afford to lose ninety minutes of a skilled employee's time every single week, he'd say no, obviously not. But nobody frames it that way. Framed as "the Friday report," it feels like a chore, not an expense. It's baked into the week. It's just what Fridays look like.
This is how recurring costs hide. A single instance of copying numbers between three systems never feels expensive enough to fix. It's not a crisis. It's not even annoying most weeks — Patricia has her process, she knows which cells to check first, she's gotten fast at it. The cost isn't in any one Friday. It's in the fact that this Friday, and the Friday before, and the fifty Fridays before that, all cost the same ninety minutes, and nobody ever stops to add the fifty-two together.
I've seen this with inventory counts, sales summaries, timesheet reconciliations, and — more than once — a "simple" report that started as a five-minute task two years ago and has quietly grown to include four more columns nobody remembers approving.
The math is almost insultingly simple
Here's the calculation, and it takes less time than the report itself:
Minutes per week × 52 weeks ÷ 60 = hours per year.
For Patricia: 90 minutes × 52 = 4,680 minutes, or 78 hours a year. That's nearly two full forty-hour workweeks spent exclusively on copying numbers between systems that already have those numbers. Not analyzing them. Not acting on them. Copying them.
Multiply that by her hourly cost to the business — salary, benefits, overhead, whatever number your accountant uses — and you have a real figure. For most small and mid-size businesses I've worked with, that number lands somewhere between a decent conference registration and a decent used car. Every year. Forever, unless something changes.
And that's one report, from one person. Most businesses I walk into have two or three versions of Patricia, each with their own Friday ritual, each convinced their report is too company-specific to automate.
It's rarely about laziness or bad tools
I want to be clear about something: Patricia isn't inefficient. She's good at her job. The ninety minutes isn't wasted because she's slow — it's wasted because the task itself is structurally repetitive work that a computer should be doing. Humans are bad at being reliable copy machines, not because we're careless, but because we're expensive, easily interrupted, and prone to the exact kind of small transcription error that causes next week's meeting to start with everyone wondering whether that number is even right.
This is the same work, every week, pulling from the same three sources, assembled the same way, for the same purpose. That's not a job description. That's a specification for a dashboard.
What changes once the report builds itself
A dashboard that pulls from the point-of-sale system, the shipping spreadsheet, and the bank feed automatically doesn't make Patricia's judgment obsolete — it removes the part of her week that never used her judgment in the first place. The ninety minutes she spent copying numbers becomes ninety minutes she spends on literally anything else: the two or three decisions a week that actually need a competent person's attention, instead of a competent person acting as a human cable between three systems that could talk to each other directly.
This is also why I think the instinct to say a dashboard isn't affordable right now is usually backwards. The real comparison isn't the cost of a dashboard against zero. It's the cost of a dashboard, paid once, against seventy-eight hours a year, every year, indefinitely. The report doesn't get cheaper with time. The dashboard does — it gets cheaper every year you keep using it, because the ninety minutes a week is gone for good.
The reframe that actually matters
A dashboard isn't a luxury upgrade for companies that have outgrown spreadsheets. It's reclaiming time that's already being spent, permanently, on a task that doesn't need a human doing it. The business doesn't gain some new, exotic capability. It gets back ninety minutes a week, fifty-two weeks a year, for as long as the dashboard keeps running — which, unlike Patricia's patience for this particular Friday ritual, is indefinite.
If your team has a Patricia — a report somebody quietly rebuilds by hand every week, every month, or every quarter — it's worth doing the math before deciding it's not worth fixing. Ninety minutes feels small. Seventy-eight hours a year rarely does.