Zero RFI
Something notable surfaces in conversations with owners and developers who have been around long enough to remember the early promises of construction technology.
They spent the money. They mandated the platforms. They went through the implementations. And when you ask them honestly whether the projects got better (whether the data improved, the cost certainty improved, the outcomes improved) the honest answer is: not really.
That is not an accident. And it is not the fault of bad technology. It is a structural problem in how the industry thinks about what software is supposed to do.
The archive problem
Walk into most construction firms and ask where project decisions get made. The answer is email, text, phone calls, and weekly meetings. Now ask where that information goes after it is captured. Into Procore. Into Autodesk. Into whichever system of record the company pays for.
Notice the order. Decisions happen in real time, in conversations, in the field. The software captures what happened, after the fact. The project management platform is not where work gets done. It is where work gets documented once it is done.
That is not a tool. That is an archive.
The moment you see this, a lot of things click. People default back to spreadsheets because the spreadsheet is where they actually think. The “system of record” is where they prove they thought. Tell your team they can no longer use email or spreadsheets and see what happens. Nothing moves.
Too many tools, too little integration
There has been an extraordinary amount of investment in construction software over the past decade. Hundreds of products, many of them solving legitimate problems: scheduling, safety, quality management, prefab coordination, drone surveys, cost tracking.
The problem is not the quality of the products. It is the quantity and the fragmentation. Every tool added to a project team’s stack is a workflow change request sent to people whose primary job is building something on time and on budget.
Implementation has a cost that rarely appears in the software budget. Training time. Workflow disruption. The cognitive overhead of switching between systems. A project team asked to use eight new tools is a project team with diminished capacity to actually manage the project.
The result: tools get purchased, partially implemented, and quietly abandoned mid-project. The firm shows them in the pitch. They rarely survive contact with an active project schedule.
Every project is different
A second structural mismatch is equally significant: software built around workflow templates assumes workflows are consistent. They are not.
Building a hospital is not like building a multifamily development. A ground-up industrial facility does not run like a renovation of an occupied office building. Even within the same project type, owner requirements, site conditions, delivery methods, and team configurations vary enough that any rigid workflow model creates friction.
Construction is not like manufacturing. It is closer to filmmaking, a temporary organization assembled for a specific project, then dispersed. Every project assembles a unique team, faces unique conditions, and requires unique judgment calls. Software designed for repeatable processes struggles with something that is fundamentally unrepeatable.
What owners actually need
If you are a building owner or developer trying to get real value from technology, the question to ask is not “which platforms are my contractors using?” It is “where is my real-time data, and what decisions can I make with it?”
The technology that delivers owner value is not the tool that makes project teams more efficient at recording what happened. It is the tool that gives owners visibility into what is happening, surfaces risks before they become change orders, and creates accountability that does not depend on reading a monthly report.
That technology exists now. It is not the project management platform your GC is using. It is the layer that sits above the project, connects to the data that actually exists, and gives the owner a clear picture of where they stand.
The question is whether your project partners are investing in your transparency or their own.
