The Line Item Nobody Tracks
Every construction firm has a P&L. Every P&L has line items. Labor. Materials. Equipment. Subcontractors. Insurance. Software licenses.
None of them, in almost any construction firm we've ever audited, has a line item for the single largest operating expense the firm actually pays.
That expense is manual coordination.
It's the project manager rebuilding the same spreadsheet for the fifth time. The superintendent re-typing field notes into three different systems. The CFO chasing change orders across email, Excel, and a folder share that nobody admits to using. The owner's rep recreating a financial summary because the platform that was supposed to produce it doesn't talk to the platform that has the data.
It is invisible because no invoice ever arrives for it. It is enormous because it consumes, by every credible study we've reviewed, somewhere between 25 and 40 percent of your team's working hours.
This guide is the document that makes it visible.
If you finish reading this and run the math against your own organization, you will find a number large enough to fund the entire switch to a modern platform — three or four times over — in the first year.
The number has been there the whole time. You just didn't have the framework to see it.
The Counterintuitive Truth About Software Cost
Most teams evaluate construction software by comparing license fees. Procore costs X. Autodesk costs Y. Jet.Build costs Z. The cheapest one wins.
That comparison is not just incomplete. It is structurally backwards.
The cost of construction software is not the license fee. The cost of construction software is the total labor required to compensate for what the software doesn't do.
A platform that costs $50,000 a year and saves your team 200 hours a month is paying you to use it. A platform that costs $25,000 a year and forces your team to spend 400 hours a month working around its limitations is the most expensive thing on your balance sheet.
The license fee is the tip of the iceberg. The coordination tax is the iceberg.
Until your team learns to evaluate platforms on total cost of operation rather than total cost of ownership, you will keep choosing the wrong platforms — and you will keep wondering why margin keeps slipping despite your best efforts to control it.
The $177 Billion Problem
Let's start with what we know at the industry level.
Multiple studies, conducted by separate organizations across the past decade, have arrived at remarkably similar conclusions. U.S. construction professionals lose somewhere between 30 and 40 percent of their working time to inefficient, manual coordination tasks. Industry-wide, this represents over $177 billion in annual productivity losses.
Read that number again. One hundred seventy-seven billion dollars. Per year. Lost to coordination friction that better software would eliminate.
If construction were one company, $177 billion would be the largest line item on its income statement after labor and materials. It would be larger than the company's profits. It would be larger than its capital expenditures. It would be the single most consequential operational metric on the entire business.
But construction isn't one company. It's tens of thousands of firms, each absorbing their proportional share of that loss, each treating it as the cost of doing business, each accepting it because the alternative — running the math — would be too uncomfortable.
Until now.
The Anatomy of the Coordination Tax
Let's get specific. The coordination tax shows up in seven places. We'll walk through each, briefly.
One. Status updates that exist only because systems don't talk.
When your scheduling tool, your accounting tool, your document management tool, and your field reporting tool are separate systems, somebody has to translate between them. That somebody is your project manager. That translation work, repeated across every project every week, is the single largest source of coordination tax in most firms.
Two. Reports rebuilt because dashboards don't reflect reality.
Your CFO needs a cash flow report. The platform produces one — but it groups the data wrong, or excludes a category, or shows last month instead of last week. So somebody exports the data and rebuilds the report in Excel. Every Friday afternoon. Every month-end. Every board meeting.
Three. Approvals chased across channels.
A change order needs three signatures. One signer is on email. One signer prefers texts. One signer wants a phone call. The change order doesn't move until somebody manages all three channels in parallel. That somebody — usually a senior PM — spends hours a week on what should be a 30-second action.
Four. Field data re-entered from paper or photos.
The superintendent files a daily log on a phone in the field. The data is correct. The format is wrong for the office system. So someone in the office re-enters it, often the next morning, often with errors that have to be reconciled later.
Five. Document searches that take longer than the work itself.
A subcontractor asks where the latest set of revised drawings live. The answer requires checking three folders, two cloud drives, and an email thread. Twenty minutes to answer a question that should take twenty seconds.
Six. Onboarding that repeats every quarter.
A new PM joins the team. They spend four to six weeks figuring out where things live, who approves what, why the firm does X this way. That ramp time exists almost entirely because institutional knowledge lives in people's heads rather than in the system.
Seven. Reconciliations that nobody officially owns.
The accounting system says one number. The project management system says another. Somebody has to figure out which is right. That somebody is rarely the same person twice, the work is rarely tracked, and the cost is rarely accounted for.
Each of these is a small leak. Together, they are a hole in the boat.
How to Calculate Your Own Coordination Tax in 90 Minutes
Most CFOs assume the coordination tax is unknowable. It isn't. It just requires a structured 90-minute exercise that almost no firm bothers to run.
Here is the framework. Run this in a single conference room session with three people: your CFO, your most senior PM, and your operations lead.
Step One. List every role on the team that touches project coordination.
Project managers. Assistant project managers. Superintendents. Estimators. Owner's reps. Project accountants. Document controllers. Be exhaustive. The point is not to be precise. The point is to capture every role whose work exists, in part, because the systems don't talk.
Step Two. For each role, estimate the percentage of weekly hours spent on coordination work.
Be conservative. If your senior PM has a 50-hour work week, and you genuinely believe 30 percent of those hours are coordination tax, write down 30 percent. The number for most roles in most firms lands between 25 and 40 percent. Lower than 20 percent indicates either an exceptional firm or wishful thinking.
Step Three. Calculate the fully loaded labor cost for each role.
Salary, benefits, taxes, overhead allocation. Fully loaded. Most senior PMs in major U.S. metros land between $140,000 and $200,000 fully loaded. Use real numbers from your own organization, not industry averages.
Step Four. Multiply percentage by fully loaded cost. Sum across roles.
The number you arrive at is your annual coordination tax.
For a small firm of fifteen people, this number is typically $400,000 to $750,000 per year. For a mid-sized firm of fifty, it's $1.5 million to $3 million. For an enterprise firm of two hundred, it's often north of $10 million.
These are conservative estimates. They use the firm's own self-reported coordination percentages, which always undercount.
The first time a CFO sees their own number, the conversation about whether to switch platforms changes permanently.
What CFOs Discover When They Run the Numbers
We've watched this exercise play out in dozens of firms. The patterns are consistent enough to be predictable.
Owner-developers including NY Developers & Management have eliminated the translation tax across portfolios of 12+ active projects without adding operational headcount — see how →
The CFO's first reaction is denial. That can't be right. Let me check the math.
The math checks. The CFO recalculates with even more conservative inputs. Reduces every percentage by five points. Strips out the most senior salaries. Excludes overhead. The number comes down — but only by 20 percent. The original estimate was already conservative.
The second reaction is curiosity. If the number is real, where is it going?
This is the moment the conversation gets useful. Because once you know the coordination tax exists at scale, the next question is what would actually reduce it. The answer, in 2026, is no longer “hire more PMs” or “implement better processes.” The answer is software that eliminates the coordination work itself — by making the systems talk, the data unified, the approvals frictionless, the reports automatic.
The third reaction is strategic. If we eliminated even half this tax, what would that fund?
A firm we worked with last year ran the math and found $1.8 million in annual coordination tax. They invested $180,000 in a modern platform. The platform recovered, by their own measurement at the 12-month mark, roughly $1.1 million of that tax in the first year alone. The remaining $700,000 was recovered in year two, after team adoption deepened.
The ROI was 510 percent in year one. Nearly 1,000 percent in year two. These numbers sound implausible until you remember that the alternative was paying $1.8 million a year forever to maintain a coordination problem the firm didn't know it had.
The Three Lies the Coordination Tax Tells You
The coordination tax is not just expensive. It is deceptive. It tells your team three lies that prevent action.
Lie One: “This is just how construction works.”
It isn't. Construction worked this way for a long time because the technology to coordinate at scale didn't exist. That changed. Modern operating systems for construction have eliminated entire categories of coordination work — not by improving them, but by making them unnecessary. Teams who haven't seen this in action assume it's impossible. Teams who have seen it cannot understand how they ever worked the old way.
Owner-developers including AMS Acquisitions have replaced spreadsheet-and-email operating models with unified platforms — see how →
Lie Two: “Our team is just inefficient. We need to train them better.”
Almost certainly false. The teams running the highest coordination tax are usually the most disciplined teams in their firms. They are the people compensating, hour by hour, for the fact that the tools won't do what the work requires. Blaming the team for software-induced friction is a category error that punishes the people who are holding the firm together.
Lie Three: “Switching software would cost more than it would save.”
This is the most expensive lie of all. It is the lie that justifies inaction in the face of overwhelming math. The cost of switching to a modern platform — including license fees, implementation, change management, and team training — is typically a small fraction of a single year's coordination tax. The question isn't whether switching saves money. The question is how much money you've already lost by not switching sooner.
A Note for Operators Who Have to Sell This Internally
If you've gotten this far, you may be the person in your organization who has to make the case to a skeptical CFO, COO, or board.
Here's the framework that consistently moves these conversations forward.
Lead with the firm's own number, not industry data. We ran the math. Our coordination tax is $X. Here's the calculation.
Compare that number to the cost of the alternative. A modern platform costs Y per year. The math says we recover X minus Y in year one.
Acknowledge the switching cost honestly. Migration takes 14 days of focused team attention. The team will be uncomfortable for a week. Then it will be over.
Frame inaction as the expensive choice. Every quarter we don't switch, we pay another quarter of X. By Q4, we've paid for the migration four times over and gotten nothing for it.
The CFOs who hear this framing don't always say yes immediately. But they almost always start running their own version of the math — and once a CFO has run the math, the platform decision is already made. They just need a few weeks to come to it themselves. For the framework that helps CFOs evaluate the platforms themselves, see The Construction Software Buyer's Guide.
What This Looks Like When It's Working
A year after eliminating the coordination tax, the firms we work with describe the change in unexpected ways.
They don't talk about how much faster their reports run. They talk about the projects they were able to take on because their team had bandwidth to take them on. They don't talk about the hours saved. They talk about the senior PM who didn't quit because the work finally felt meaningful again. They don't talk about the software. They talk about the year their margin came back.
This is the deeper truth about the coordination tax. It is not just a cost. It is a constraint. Eliminating it doesn't just save money — it unlocks capacity. The firm becomes capable of work it could not have considered before.
The tax is invisible while you're paying it. It is unforgettable once you've stopped.
A Final, Hard Question
If, by the end of this guide, you can write down a number for what manual coordination is costing your firm — and that number is meaningful at the scale of your business — then exactly one question remains.
What is the cost of waiting one more quarter to do something about it?
Most operators answer that question with optimism. We'll get to it next year. We'll address it after this project closes. We'll figure it out when the team has more bandwidth.
The coordination tax doesn't care about optimism. It compounds quarterly, regardless of intention. Every 90 days you delay is another 90 days of the same number, paid in full, recovered by no one.
The teams who win the next decade in construction are the ones who name this cost, run the math, and make the platform decision while their competitors are still telling themselves the tax doesn't exist.
The math is on the table. The framework is in your hands.
The next move is yours.
This guide was written by the team at Jet.Build. We help owners, developers, GCs, and construction managers eliminate the coordination tax — typically recovering 60 to 80 percent of it within the first year on a modern operating system.