Here’s a number worth spending five minutes with: $75,000.
For a construction company with 10 back-office employees, three hours per week spent moving and reconciling information between disconnected systems adds up to $75,000 per year in loaded labor.
10 employees × 3 hours/week × $50/hour × 50 weeks = $75,000/year
The math isn’t complicated, but the number tends to get people’s attention.
Before you read any further, run it for your own company. Swap in your headcount and loaded hourly rate. Treat the result as a starting point, not the total.
What the $75,000 Estimate Leaves Out
Empower’s own model is explicit about what that $75,000 does not include:
- Errors introduced when data is rekeyed manually across systems
- Delayed billing that slows cash flow
- Missed or underpriced change orders
- Slower collections
- Management decisions made on information that’s already a week or two old by the time it reaches the people who need it
Each of these can create a measurable financial impact beyond the labor baseline.
Industry research helps put some of those excluded costs in context. A 2026 AEC analysis estimated that recreating a single batch of records across disconnected platforms could require roughly 125 hours and $6,250 in labor, with ongoing updates adding another 250 hours and $12,500.
A Construction Dive-sponsored case study documented a firm that saved 600 hours and $30,000 annually by eliminating a single redundant data-entry workflow between two systems.
How Disconnected Systems Increase Change Order Costs
Change orders are worth spotlighting specifically because they’re among the most common places where disconnected-system costs quietly compound. One industry analysis estimates approximately $420 in administrative handling per change order, including PM administration, superintendent review, and owner/architect communication. For a commercial project in the $20 million range with 35–50 change orders, that amounts to roughly $14,700-$21,000 in administrative effort throughout the project.
McKinsey has estimated that closing construction’s long-standing productivity gap could add roughly $1.6 trillion in annual value globally. The macro figure reinforces a larger point: small, recurring productivity losses compound quickly across construction. For an individual contractor, the more useful exercise is to identify which of those losses can be measured within the business.
What Contractors Tolerate in the Back Office They’d Never Accept on the Job Site
Construction companies are relentless about managing productivity in the field. Crews are scheduled, equipment downtime is challenged, and subcontractors are coordinated. If workers repeatedly handled the same material, manually transferred information from one crew to another, or waited hours for what they needed to keep working, management would address it immediately.
Yet many of those same companies tolerate exactly that kind of inefficiency in the back office every single week.
Accounting enters information into one system, payroll uses another, project managers maintain spreadsheets, and estimating operates separately. Field applications generate still more data. Employees export, rekey, reconcile, email, and manipulate information simply to assemble a complete picture of the business. Nobody decided this was a good idea. It’s just what the system became over time.
The question worth asking is: if you managed your job sites the way your back office is managed today, would you consider the operation efficient?
Apply Field Productivity Discipline to the Back Office
The same discipline contractors apply to field productivity can be applied to the flow of information in the office. That means identifying time spent exporting, importing, rekeying, reconciling, and rebuilding reports, then working to eliminate it.
That discipline starts with doing the math.
Four Questions to Test Back-Office Efficiency
If the calculation is material, the next step is to identify where that cost is being incurred. A practical review can start with four dimensions:
- Information handling: Where is the same data being entered more than once?
- Field-to-office latency: How long does field activity take to appear in job-level reporting?
- Single source of truth: Are accounting, operations, and project management working from the same numbers?
- Administrative capacity: Could the back office support 20% revenue growth without adding headcount at the same rate?
These are operational questions that should be answered before any discussion of systems, software, or solutions. That analysis gives leadership a more disciplined basis for deciding whether the next step is tighter process discipline, stronger integration, or a broader construction ERP roadmap.
Run the Math
If you haven’t run the calculation yet, start there. Then look beyond labor hours to the downstream effects on billing, change orders, reporting, and decision-making. A Construction Profit & Efficiency Review can help quantify where that drag is occurring and determine what should change next.