What 90 Minutes of Daily Data Entry Actually Costs a 15-Person Team

When I first talked to this client about their data entry problem, they described it as annoying. By the time we'd finished the numbers, they described it as catastrophic. Same problem, different frame.

Here's how that reframe happened, and why it matters for how you think about the manual work in your own business.

The surface problem

The business processes around 15 building compliance jobs per day. Each job requires reading a set of building plans and entering the relevant specifications into their job management system: orientation, construction type, window details, insulation, and about 40 other fields.

An experienced assessor takes roughly 90 minutes to do this properly for a typical job. A newer assessor takes longer.

When I first heard 90 minutes, I thought: that's a lot of time spent on something that isn't the actual assessment work. But I didn't have the full picture yet.

The real cost isn't what you think

The obvious cost is time. 90 minutes per job, 15 jobs per day, five days a week. That's over 100 hours a week of assessor time spent on data entry. At any reasonable hourly rate for a skilled professional, that number becomes uncomfortable very quickly.

But the obvious cost isn't the real cost. The real cost has three other components that don't show up in a simple time calculation.

The first is error rate. Manual data entry from complex documents produces errors. Not because people are careless, but because 90 minutes of careful reading and typing is cognitively exhausting, and attention degrades. An error caught before an assessment is submitted is an inconvenience. An error caught after is a rework event, sometimes a compliance issue, occasionally a client dispute. The downstream cost of errors is almost always higher than the upstream cost of the entry itself.

The second is throughput ceiling. If your assessors are spending 90 minutes per job on data entry, that's 90 minutes they're not spending on assessments. Your maximum daily output is constrained not by how many assessments your team can do, but by how much data entry they can tolerate. Growth, in this model, means hiring more people to do more typing. That's an expensive way to scale.

The third is the one that tends to land hardest with business owners: the opportunity cost of senior time. Data entry is not a task that requires experience or expertise. When a skilled assessor spends 90 minutes entering data, you're paying experienced-professional rates for work that could theoretically be done by anyone. Or, as it turns out, by software.

Running the actual numbers

For this client, 15 jobs a day at 90 minutes each comes to 22.5 hours of data entry per day across the team. Over a standard working year, that's roughly 5,500 hours.

At an all-in cost of around $60 per hour for their assessors (salary, super, overheads), that's $330,000 per year spent on data entry alone.

That number doesn't include error-related rework. It doesn't include the growth ceiling imposed by the bottleneck. It doesn't include the intangible cost of putting skilled people through hours of repetitive work every day and wondering why retention is a challenge.

The forecast $750,000 bottom-line improvement in year one isn't just the direct labour saving. It includes the increased throughput from removing the bottleneck, the reduction in error-related rework, and the ability to grow volume without proportional headcount growth.

The reframe that changes everything

Before we ran these numbers, the client described data entry as an annoying but manageable part of the job. It had always been this way. Everyone did it. It was just the cost of doing business in their industry.

After the numbers, it looked like a strategic problem hiding in plain sight: a fixed cost of $330,000 per year that delivered zero value to clients, created a ceiling on growth, and consumed the time of the people whose expertise was the whole point of the business.

That reframe is the most important part of any operational improvement conversation. Not "what tools can we use?" but "what is this actually costing us, in full, and what would it be worth to fix it?"

In this case the answer was: worth a lot more than the fix cost.

The broader point

Every business has a version of this. A process that's been running manually for years, accepted as normal because it's always been normal, whose true cost has never been properly calculated.

The 90-minute data entry task was visible because it was large and daily. Most hidden costs are smaller and more distributed: the 20-minute report that gets compiled five times a week, the manual handoff between systems that takes 15 minutes per transaction, the weekly reconciliation that eats a Friday afternoon.

None of those feel like strategic problems. Added up across a year, at real labour costs, they usually are.

The question worth asking isn't whether your manual processes can be automated. It's whether you actually know what they're costing you.