Ask any preconstruction leader what keeps a project profitable, and you'll hear some version of the same answer: certainty, early. Know what you're building, what it costs, and what can go wrong — before you've committed to a direction you can't afford to reverse.

Now ask how their team actually works. You'll hear something very different.

Design happens in one tool. Takeoffs happen in another. Estimates live in a spreadsheet. Schedule lives somewhere else. Risk gets its own workstream entirely. Five systems, five handoffs, five chances for the signal to degrade before anyone makes a decision.

The design-build firms that are the most successful in 2026 aren't the ones with the best estimators or the best designers. They're the ones who've eliminated the gap between a design decision and a construction decision.

The five-handoff problem is a margin killer

Here's what a typical design-build preconstruction workflow actually looks like.

An architect updates a massing model on Tuesday. By Thursday, the precon team gets a PDF export. By the following Monday, someone has manually extracted quantities and plugged them into a cost model. By Wednesday, the estimate is ready — but the architect has already moved on to a new iteration. The numbers are a week stale before anyone reads them.

This isn't a technology problem. It's a structural one.

The average contractor operates with five to seven software systems across estimating and project workflows. Each transition between tools requires manual exports, duplicated data entry, assumption checks, and version control. Research across industries shows that this kind of context switching alone reduces productivity by 20-30% — and in preconstruction, that productivity loss shows up as rework after addenda, outdated cost logic, and compressed pricing timelines.

The math is straightforward. Every handoff introduces lag. Lag introduces stale data. Stale data introduces risk. And risk, in preconstruction, is margin walking out the door.

Design-build projects were supposed to fix this. Same company, same P&L, same incentive to get the answer right the first time. But most design-build projects still operate as if design and construction are separate teams. Not because the team members want to — because their tools enforce it.

Risk lives in the gaps between teams

When people talk about risk in preconstruction, they usually mean a specific deliverable — a risk register, guaranteed maximum price, a contingency line item, a Monte Carlo simulation on schedule. Those are valuable. But they're not where most risk actually accumulates.

The real risk is quieter. It's the structural assumption buried in a schematic design that nobody flagged because the estimator hadn't seen the model yet. It's the unit mix that penciled on paper but doesn't work with the structural grid — discovered six weeks into precon instead of six days. It's the unit cost assumption based on outdated data because the design was unclear.

This kind of risk doesn't show up in a register. It lives in the gaps between teams — in the lag between when a design decision is made and when its downstream impact becomes visible.

Design-build teams have a built-in advantage here. They're under one roof. The designer and the estimator work for the same firm, share the same goals, and carry the same risk. But if those two people are working in entirely separate systems — passing files back and forth, waiting days for updated quantities — that organizational advantage gets neutralized by the tooling.

Over 95% of project data captured in construction goes unused. Not because teams don't want the data. Because the data is locked in tools that don't talk to each other, in formats that require manual translation, on timelines that don't match the pace of design.

The gap between systems is where risk compounds. And the wider the gap, the more expensive the surprises.

The new loop we're building at Arcol

The preconstruction role is evolving. As Ediphi recently noted, preconstruction is "no longer about defending a number — it's about explaining it." The firms doing this well have shifted from a linear workflow — design, then estimate, then schedule, then risk — to something more like a continuous loop.

In a loop model, a design decision gets immediate feedback from the data that determines whether the project pencils. Not a handoff weeks later. Not a PDF export that someone manually processes. A loop — where the people making design decisions and the people evaluating cost, constructability, and feasibility are working from the same information, at the same time, in an connected tool stack.

This is the future Arcol is building toward. The estimate stops being a deliverable that arrives after design and becomes a living reflection of design intent — updating as decisions are made, not after they've been locked.

For design-build projects specifically, this model isn't aspirational. It's the logical conclusion of why design-build exists in the first place. 

It starts with getting out of silos

The shift from five handoffs to one loop doesn't happen overnight. But it does have a clear starting point: getting design and construction teams into a shared environment.

Not shared files. Not a shared folder on a Common Data Environment. A shared environment — where the design model and the project data it generates are visible to everyone who needs to make decisions, in real time.

This is what Arcol is building. A constructible design environment where design-build teams work together from day one — where architects and precon teams aren't passing exports between disconnected systems, but collaborating in a single space where design decisions and construction decisions coexist.

Arcol doesn't replace your estimating software or your scheduling tools (at least not yet). It collapses the wall between design and the construction intelligence that should be informing it. Today, that means getting teams out of silos — designers and builders working in the same model, seeing the same data, iterating at the same pace. Over time, it means deeper integration: tighter feedback loops between design intent and project reality, with workflows that connect the decisions that matter most.

The firms that figure this out first won't just deliver projects more efficiently. They'll win more work — because they can move faster in pursuit, price more accurately in competition, and de-risk decisions their clients make based on their work.

The gap is the opportunity

Design-build was built on a simple premise: bring design and construction together, and you get better outcomes. Faster timelines. Fewer surprises. Tighter margins.

But the tools and collaboration practices haven't caught up to the contract model’s aspirations. Most design-build teams are still running a design-bid-build workflow with a design-build org chart. Same silos, same handoffs, same lag — just under one company name.

The firms that break this pattern — the ones that replace five handoffs with one continuous loop — will define how design-build preconstruction works for the next decade, complete with the competitive advantage it affords them.

The gap between design decisions and project decisions is where margin goes to die. It's also where the biggest competitive advantage lives, for the teams willing to close it.

—

Arcol is a constructible design platform that brings design and construction teams into a single environment from day one. See how design-build firms are using Arcol to close the gap between design intent and project reality at arcol.io.