Why Western U.S. Developers Need a Contractor Engaged at Feasibility

The Question Most Developers Ask Too Late

At what point in your development process do you bring in a general contractor?

For most developers, the answer is: after the design is done. Sometimes after entitlements. Often not until they're ready to go out for bids. By that point, the project's cost structure, schedule assumptions, and risk profile have already been established — largely without the input of the person who will actually build it.

This is one of the most common and costly patterns in Western U.S. development. And it's one that Tekton is specifically built to change.

What Happens When a Contractor Isn't Engaged at Feasibility

When a developer builds their pro forma without a contractor at the table, they're making construction cost assumptions based on incomplete information. Comparable project data, published indices, and rule-of-thumb numbers can get you close — but they rarely capture the specific conditions that drive cost on a given site in a given submarket at a given point in the construction cycle.

Soil conditions, utility infrastructure, local labor markets, material lead times, subcontractor capacity, municipal inspection timelines — these variables shape construction cost in ways that a spreadsheet built in isolation cannot account for. When those assumptions prove wrong, they don't surface as minor line item adjustments. They surface as value engineering exercises that compromise the project, financing shortfalls that delay closing, or change orders that erode the return.

The further along a project is before those realities are confronted, the more expensive they become to address.

What Changes When the Contractor Is There from the Beginning

Early contractor engagement doesn't mean handing over control of the project. It means adding a voice to the process that has direct, current knowledge of what things cost and how long they take to build — and doing so at the moment when that knowledge can actually change the outcome.

At feasibility, a contractor's input can validate or challenge the construction cost assumptions in a pro forma before capital is committed. That's the lowest-cost moment to discover that a project's budget assumptions don't hold.

During design development, a contractor who is already familiar with the project can flag constructability issues, identify value engineering opportunities, and provide real-time cost feedback as design decisions are made. Every decision that gets made during design — structural systems, envelope specifications, mechanical approaches, finish levels — has a construction cost implication. A contractor in the room means those implications are understood when the decision is made, not discovered when the bid comes back.

During preconstruction, early contractor engagement allows procurement to begin before design is complete, which compresses the overall project schedule. In markets where subcontractor capacity is constrained — which describes most of Tekton's Mountain West markets — early commitment to key trade partners can be the difference between a project that breaks ground on schedule and one that waits six months for subcontractor availability.

The Developer Perspective That Tekton Brings

Tekton's leadership team has spent significant portions of their careers on the development side of the table. Our General Manager has managed projects from entitlement through delivery for four decades. Our Director of Land Development has navigated entitlement processes across the Western U.S. for over 40 years. Our Director of Business Development has led development ventures as a C-suite executive across multiple sectors.

That background shapes how we approach early engagement. We're not showing up at feasibility to pitch our services. We're showing up to contribute to a conversation about whether a project makes sense, what it will cost to build, and how to structure the delivery program to protect the developer's investment thesis.

Developers who engage us early get a construction partner who thinks like an owner — because our leadership actually has been one.

What Early Engagement Looks Like in Practice

Early engagement doesn't have to be a formal contract. It can start with a feasibility conversation. Tekton regularly sits down with developers during site evaluation to provide preliminary cost feedback, identify site-specific risk factors, and discuss delivery method options. That conversation costs nothing and often produces information that materially changes a project's trajectory — in a good way.

For projects that move forward, we offer Preconstruction Services as a standalone engagement — providing detailed cost estimates, constructability reviews, value engineering support, and lender-ready documentation before a construction contract is executed. For developers who want continuity, that preconstruction engagement transitions seamlessly into a General Contracting or CM at-Risk relationship.

The Bottom Line

The Western U.S. construction market — particularly the Mountain West — is not forgiving of projects that enter the ground with unvalidated assumptions. Construction costs are volatile, labor markets are tight, and lender scrutiny of project budgets has intensified across the board.

In that environment, the developers who consistently protect their returns are the ones who treat construction knowledge as a preconstruction input — not a post-design variable. Engaging a contractor at feasibility is the single highest-leverage change most developers can make to their project development process.

If you're working on a project in Idaho, Colorado, or Arizona and haven't had a construction conversation yet, that's the right place to start.