Design-build delivery is projected to account for 47% of U.S. construction spending by 2028, according to Dodge Data & Analytics. That is not a niche trend. It is the industry reorganizing around a fundamental insight: the wall between design and construction is a liability, not a protection.

The firms driving this shift understand something that the traditional architectural design workflow was built to deny. Design and construction are not sequential phases. They are concurrent disciplines. And the firms whose tools reflect that reality are pulling ahead.

What design-build changes about the workflow

In traditional design-bid-build delivery, the separation is contractual and structural. The architect designs. The drawings go out for bid. The contractor prices them and builds. Each party has a distinct scope, a distinct contract, and a distinct set of tools. The workflow is sequential by design.

Design-build collapses this separation. The designer and the builder share a contract, a timeline, and a P&L. The incentive structure inverts. Instead of protecting your scope through separation, you gain by integrating early. The architect who understands construction cost makes better design decisions. The contractor who sees the design intent early avoids rework downstream. The owner gets a faster, more predictable project.

This is the delivery model nearly half the industry is moving toward. The architectural design workflow should reflect it.

The tool problem nobody wants to talk about

Here's where design-build's promise collides with reality. Most firms pursuing design-build are operating with tools built for the old model.

The architect works in Revit. The estimator works in a spreadsheet or a separate takeoff tool. The contractor uses different software for scheduling, means and methods, and field management. Each tool was built for a distinct phase, optimized for a distinct discipline, and connected to the others through exports, imports, and manual coordination.

The tools enforce the sequential handoff even when the delivery model demands concurrency.

This is not a minor friction. It's a structural mismatch. The design-build contract says "work together." The tools say "work separately and email each other." The firms feel it every day. They run more coordination meetings. They produce more interim exports. They build elaborate workarounds, shared spreadsheets, weekly alignment calls, parallel models that someone manually keeps in sync, to compensate for tools that were never designed for concurrent work.

FMI's research on construction productivity has consistently identified tool fragmentation as a primary driver of the $1.85 trillion in annual global rework costs. Design-build reduces rework contractually by aligning incentives. But the tools are still generating it operationally by forcing sequential workflows on concurrent teams.

What the leading firms are doing differently

The design-build firms winning the most work in 2026 are the ones whose architectural design workflow matches their delivery model. Not partially. Fundamentally.

They work in shared environments where the architect and the estimator see the same model. Where cost updates as geometry changes. Where the contractor's construction intelligence is present during design, not delivered as a review package after the fact.

This is more than better collaboration. It is a different kind of work. When the designer can see cost implications in real time, they make different decisions. When the estimator is working from a live model instead of a static export, they catch issues earlier. When the contractor's knowledge of means, methods, and site constraints is embedded in the design tool, the design reflects constructibility from the start.

The coordination meetings get shorter because there is less to coordinate. The exports get fewer because the model is shared. The rework drops because the decisions were informed from the beginning.

The competitive advantage of the concurrent workflow

The firms that match their tools to their delivery model gain advantages that compound across every project.

Faster response to RFPs. When feasibility, cost, and constructibility intelligence are native to the design environment, the firm can produce a credible proposal faster than a firm that assembles the same information across four tools and three teams.

More accurate pricing earlier. Cost intelligence embedded in the design model means the estimate evolves with the design, not after it. Clients see real numbers at the schematic phase, not a guess that gets refined for three months.

Smoother downstream workflows. Coordination that happens during design, not after, eliminates the misalignments that generate change orders downstream. The contractor sees the design as it develops. The architect sees the cost as it accrues. Issues surface when they cost a conversation, not a change order.

More pursuits with the same team. When the cycle from pursuit to proposal is shorter, the same team can pursue more work. This is not about working harder. It's about the tool environment eliminating the dead time between disciplines.

This is not a marginal improvement. It is a structural advantage. The firms that have it will outpace the firms that don't. Not because they have better architects or better builders. Because their tools let the architects and builders actually work together.

Connected Constructible Design is built for this

Connected Constructible Design is the architectural design workflow that design-build has been waiting for. It's what happens when design and construction intelligence share the same environment, the same model, the same moment.

In Arcol, the architect designs with cost intelligence present. The structural feasibility evaluates as the floor plate changes. The estimator works from the same model the architect is drawing. The workflow is concurrent because the tool was built for concurrency. Not adapted for it. Not extended toward it. Built for it.

This is what it means to match the tool to the delivery model. The design-build contract promises integration. The architectural design workflow should deliver it.

The firms that align will set the pace

The design-build delivery model is built on the idea that design and construction should be integrated. Nearly half the industry agrees. The delivery model has changed. The contracts have changed. The incentives have changed.

The tools are the last piece.

The firms that align their technology to their delivery model will set the pace. They will pursue more work, win more often, and deliver more predictably. They will spend less time coordinating across tool boundaries and more time doing the work that the design-build model was built to enable.

The rest will keep working around tools that were built for a workflow they have already abandoned. The architectural design workflow of design-build is not sequential. The tools should stop pretending it is.