Design-Build Proposals are Not Design Proposals with a Contractor Stapled on

Integrated project delivery is reshaping federal AEC procurement. Design-build, progressive design-build, CMAR, and public-private partnership structures now account for a growing share of federal construction dollars — USACE, NAVFAC, GSA, VA, and DOE all continue to shift work toward alternative delivery because it produces better schedule and cost outcomes when done correctly.

But alternative delivery only works when the team actually delivers it alternatively. And federal evaluators know the difference.

Every year, AEC firms lose design-build pursuits they should have won. The pattern is consistent: they treated the proposal like a design proposal with a contractor stapled on. Or a construction proposal with a designer named in the teaming chart. What they didn't do was write an integrated response to an integrated delivery requirement.

What is a federal design-build proposal actually evaluating?

A federal design-build RFP evaluates more than qualifications and price. Federal procurement research consistently shows evaluators weight team qualifications and integrated project understanding heavily in design-build selections — often more heavily than the specific technical design approach itself. What the government is buying in design-build is the team's ability to execute an integrated delivery model, not just the design concept or the construction plan.

That means evaluators are looking for proof of four things.

Team integration. Evidence that the design firm and the construction firm actually work as one team, not two firms with a joint logo. This includes prior joint experience, shared approaches to critical decisions, integrated staffing plans, and joint ownership of outcomes.

Project understanding. A demonstrated grasp of the specific project's technical, operational, and mission requirements. Generic language about "complex federal projects" doesn't cut it. Evaluators want to see that you understand why this specific project exists, what success looks like for the agency, and where the real risks live.

Past performance relevance. Not a list of everything your design firm has ever designed and everything your construction firm has ever built. Relevant design-build past performance, delivered by teams structurally similar to the one proposed, on projects similar in scope, complexity, and delivery model.

Management approach. How the team will actually run the project — decision-making protocols, design-construction interface management, cost management during design, and risk allocation between the design and build partners.

If your proposal doesn't have clear, evidence-backed answers to all four, you're competing for a design-build contract with a design-bid-build response in a new cover.

The five places AEC firms lose design-build pursuits

After evaluating design-build proposals across USACE, NAVFAC, GSA, and VA opportunities, the failure modes cluster.

Failure one: the teaming chart tells you everything you need to know. Open the proposal. Find the organizational chart. If the design firm and construction firm report to a joint "design-build manager" position that clearly doesn't exist in either firm's day-to-day operations, and every other role reports up through the firms separately, you're not proposing integration. You're proposing coordination. Evaluators have seen a thousand of these charts. They know what real integration looks like and what organizational theater looks like.

Failure two: the technical approach is two documents glued together. Read the technical approach out loud. If you can tell which paragraphs came from the design firm and which came from the construction firm without being told, it's not an integrated response. Design-build technical approaches should reflect joint problem-solving. The design decisions should show evidence of constructability input. The construction approach should reflect design intent. The two should be inseparable.

Failure three: the schedule is a waterfall schedule with a design-build label. Real design-build schedules have specific structural features — early procurement decisions, overlapping design and construction activities, constructability reviews at defined design milestones, target value design elements, and decision gates that reflect joint authority. A schedule that shows design finishing before construction starts, with no overlap and no joint decision gates, is a design-bid-build schedule. Evaluators catch this immediately.

Failure four: the risk register is generic. Design-build projects have specific risk profiles. Design-construction interface risk. Scope creep during design development. Constructability issues discovered late. Cost growth when design changes post-GMP. A risk register that lists weather, supply chain, and labor availability misses the entire point. Federal evaluators scoring design-build proposals are looking specifically for evidence that the team understands the risks their delivery model introduces.

Failure five: the cost approach looks like a standalone estimate. In a real design-build response, the builder's input shaped the design, not just validated it. Target value design thinking should be visible. The cost approach should demonstrate joint authorship, shared assumptions, and a clear pathway from concept to GMP. When the cost volume reads like a standalone construction estimate bolted onto a design narrative, evaluators know the two firms didn't actually integrate.

Where integration has to happen — and when

Integration cannot be manufactured during proposal development. Teams that try to integrate under proposal deadline pressure produce proposals that read like exactly what they are: two firms trying to sound like one team for the first time.

Real integration happens before the RFP drops.

It starts with partner selection for the right reasons. The most credentialed firm in the country is the wrong design-build partner if your teams can't integrate — if decision-making styles clash, if the executive sponsors don't trust each other, if the project teams can't communicate fast enough to keep a design-build schedule honest. Pick partners based on integration compatibility, not brand name.

Then the teams have to actually work together before the pursuit. Not through a single kickoff meeting. Through real joint activity — a charrette on a conceptual project, a joint approach document for a specific customer segment, a shared past performance write-up that demonstrates the integration claim.

By the time the RFP is out, the team should already have a shared point of view on:

• How this customer typically defines success on projects like this
• What the critical technical risks are and how the team would approach them together
• What the joint decision-making structure looks like in practice
• How design-construction interface is actually managed day-to-day
• Where the project's biggest cost and schedule risks live

If any of those are still undefined when proposal development starts, the proposal will reflect that gap.

The proposal-level fixes that actually work

When capture-stage integration is real, a few proposal techniques amplify it.

Write in one voice. Assign a single lead author for each volume. Yes, SMEs from both firms contribute content. But one writer synthesizes. The finished proposal should read like one team produced it, because one team did.

Use joint voice intentionally. Instead of "the design firm will" and "the construction firm will," use "our design-build team will." This isn't cosmetic. It signals to evaluators that the team is thinking as an integrated entity.

Show your joint work. If the team ran a joint constructability session, reference it. If the builder's input changed a specific design direction, describe how. Specific evidence of prior joint decision-making is one of the highest-leverage things you can include in a design-build proposal.

Lead with integrated past performance, not individual firm past performance. Three projects your team delivered together — structurally similar to this opportunity — will outperform six projects the individual firms delivered separately.

Address integration risk directly. Don't pretend design-construction interface is a solved problem. Address it. Show how your team manages it, what's worked in prior projects, and why this pursuit's integration approach will work.

The Summit Win System™ view

In the Win System, the Position peak is where design-build teams either build the foundation for an integrated proposal or start the pursuit already behind. Positioning a design-build team isn't about having the right logos in the same teaming chart. It's about demonstrating a real, pre-existing integration that evaluators can recognize on the page.

AEC firms that win design-build pursuits consistently treat integration as a pre-RFP discipline. They invest in partner relationships before they need them. They do joint work on speculative pursuits to build the muscle. And by the time a real RFP hits, the proposal is documenting integration, not inventing it.