The true cost of six disconnected systems

Most electrical and mechanical contractors aren't running one procurement system. They're running six.

The ERP or accounting system (Sage, Vista, Acumatica) handles job costing and invoices. Individual supplier portals handle pricing checks and order placement. A spreadsheet (or a series of them) tracks what was purchased and where it went. A separate tool tracker, or nothing, manages equipment across job sites. Email and text handle field requisitions. A WMS or manual count manages the warehouse. Six systems, none connected, each one adding a layer of translation work that nobody accounts for until something breaks.

According to AlignOps-sponsored research via Construction Dive, 79% of contractors manage procurement, asset tracking, and maintenance across three separate functional systems. That's the minimum. In practice, each of those functional buckets contains the multiple tools named above. In a recent study of construction businesses, the average technology count per company has risen to 6.2, up from 5.3 the prior year. The number isn't surprising to anyone who has looked at what these companies actually run.

The count is a symptom. The gap between those systems (the email threads, the manual reconciliation, the phone calls filling the space where data should flow) is where the cost actually lives.

What a fragmented construction software stack costs

When systems don't share data, people fill the gap. Field teams text purchase requests to the office. The office checks the supplier portal, cross-references the spreadsheet, confirms the job cost code in the ERP, and sends the purchase order by email. The request that could move in minutes moves in hours. Multiply that by dozens of active jobs and a purchasing team running at capacity.

The same AlignOps-sponsored research via Construction Dive found that 97% of contractors lack real-time asset visibility. Workers spend 30 to 60 minutes per day searching for tools they already own, and 98% of teams report doing this frequently or sometimes. The tools haven't gone anywhere. They're sitting on another job site, in the back of a van, or tagged to a project that closed six months ago. Without a system that tracks location and custody, the search loop repeats on every job.

At a mid-size electrical contractor with a 50-person project management team, procurement tasks consuming 20% of PM time at $120K loaded cost per person burns roughly $1.2M in capacity annually. Not on project work. On coordination between systems that weren't built to talk to each other.

That's before counting what disappears through procurement leakage. When purchasing runs through disconnected supplier portals and manual spreadsheet tracking, 20 to 35% of spending flows as maverick spend: off-contract, unmanaged, paid at prices nobody negotiated. Unmanaged spend costs 5 to 20% more than managed spend. At any material volume, that difference compounds fast.

The five hidden costs draining project profits from material management (carrying cost, shrinkage, duplicate purchasing, administrative overhead, and lost productivity) trace back to the same root. When there's no single record of what's been ordered, what's on hand, and what's been released, every layer of the operation runs on incomplete information.

At firm level, an Autodesk/FMI study puts the waste at $2.4M per firm annually from non-optimal activities alone. Globally, $1.85 trillion is lost annually to bad data across the construction industry. Only 26% of contractors rate their data quality as high.

Most contractors don't have real-time inventory visibility across job sites. The dollar cost of that absence accumulates on every project.

The project-level proof

According to AlignOps-sponsored research via Construction Dive, one large mechanical contractor was running $300K to $400K in per-project tool loss. Equipment disappeared between job sites. Teams searched, ordered duplicates, wrote off the original as lost, then found it three projects later. The problem wasn't the people managing the equipment. It was the absence of any system that tracked where everything was.

After implementing connected asset tracking, that per-project loss dropped to nearly zero.

The math every exec in this segment can run: multiply average per-project tool loss by annual project count. For a contractor running 20 to 30 projects per year, the exposure is a capital line item that the systems never surfaced.

The mechanical contractor case also surfaces a secondary cost that rarely gets tracked: the time PMs spend managing the fallout from missing equipment. Duplicate purchase orders take administrative time to process, receive, and reconcile. Insurance claims for written-off tools require documentation. Foremen fielding calls about missing equipment are pulled off job site oversight. These downstream costs don't appear in a tool-loss figure, but they're real capacity burned on a solvable problem.

Why "hire more people" doesn't close the gap

The reflex response to this kind of friction is headcount. Add a coordinator. Hire another purchaser. Give the field team another admin contact.

The problem is that the labor pool to absorb these roles is contracting. 92% of construction firms already report difficulty finding qualified workers, and the industry needs 439,000 net new workers in 2025 alone. The people to throw at the system's problems aren't available. And when they are, adding them to a broken process doesn't fix the process. It adds cost to the symptom.

The capacity burn calculation makes this clear. Every hour a project manager spends checking supplier portals, chasing field requisitions, and reconciling spreadsheet POs is an hour not spent on the job they were hired to do. That's the system extracting labor from the people you've already hired. It doesn't stop when you add more people. It scales with them.

The instinct to hire is understandable, but the problem is structural. Adding a coordinator to a broken process creates a better-staffed broken process. Until the systems share data, the translation work doesn't disappear. It just gets redistributed.

What connected operations looks like

The before-state (six systems, manual translation at every seam) has a structural answer: connected operations. A single system where the field request, the purchase order, the receipt, the inventory record, and the job cost entry all live in the same place.

Guarantee Electrical used this approach to run $200M in annual material purchases through a single connected system, reducing the share of staff time going to material handling. The number is large enough to benchmark against most mid-market electrical contractors' total annual material spend.

The connection points matter more than the count. When field ordering flows directly into purchase approvals, POs match receipts automatically, and inventory updates in real time across locations, the 30-to-60-minute daily tool search becomes a lookup. The maverick spend problem closes because purchasing runs through contracted suppliers on negotiated pricing. The PM capacity burn converts back to project work.

The architecture is the problem

The case for change in connected operations isn't about software features or dashboard views. The architecture of a fragmented construction software stack (ERP here, supplier portals there, spreadsheets bridging the middle, field requisitions coming in by text) creates a compounding tax on every project. The tax shows up as capacity burned, materials lost, spend unmanaged, and projects delivered over budget.

Industry data consistently shows that fewer than one in three construction projects land within 10% of the original budget. Schedule compression has tightened the window further: contractors are absorbing faster delivery expectations on compressed timelines, leaving no margin for the friction that disconnected systems introduce.

The six-system stack isn't a legacy problem that resolves on its own. The data is clear on where it lands: $300K to $400K per project in tool loss. $1.2M in PM capacity. $2.4M in firm-level waste annually. A procurement system where 20 to 35% of spend flows through no contract at all.

That's the cost of disconnected systems. The decision isn't whether to address the architecture; the numbers make that case. The decision is how long to carry the cost before making the change.

If your operation runs on a version of these six systems, book a demo — we'll walk through what connected procurement looks like against your current stack.