CG Common Ground | A 204-unit multifamily: value engineering (Nevada, 2026)
The decision and the reasoningCompleted

The decision and the reasoning

Confirm the number, and say whose it is

The project came to LÏEF in the first week of January 2026 through the manufacturer of a structural panel system. A developer was carrying a multifamily project in Nevada on a stick-framed number, because wood framing is the assumption every general contractor, appraiser and lender in that market already knows how to underwrite. The manufacturer wanted a budgetary comparison it could put in front of the developer: the project built the conventional way against the project built on the system. The developer's question, underneath the manufacturer's, was simpler. Is the alternative actually cheaper on my building, and by enough to be worth the thinner track record.

One fact first, because a lender would want it first. The system on the low side of this comparison is one LÏEF prices and builds, and its manufacturer was the customer of the comparison. The stick number is a market benchmark, not a bid we solicited. This is not a neutral third party's bid against ours. I say it once here rather than on every page, and I hold the constants where a stranger can check them.

The people in it were the manufacturer's principal, who brought the project and wanted a number that would sell; the developer's team, who wanted a number that would hold; my general contracting partner on the comparison, who would have to build it; and me in the estimating seat. The developer's number was the midpoint of a budgetary range, not a priced bid, and the panel system's numbers came from smaller jobs and from the manufacturer's own sample-wall arithmetic. What they actually needed was not a lower number. It was two numbers built on the same scope, plan set and finish allowances, with the variance stated where the risk lives, and a clear line between what a per-square-foot rate proves and what a project total would require before anyone could act on it.

Price the whole project, not the sample wall

There were two ways to answer. Take the developer's benchmark, take the manufacturer's sample-wall arithmetic, and hand over a clean sheet. Or price the system side against the project's own plans at full scope, hold every line the system cannot touch identical on both sides, and let the comparison land where it landed. The first is what an interested party usually does. The second is what I did, because a sample wall measures a wall and this was a building.

The harder call was where to stop. A per-square-foot comparison built on identical scope is a validated rate, and the pull to multiply it across the project and call the product a project total is strong, because the arithmetic is correct and everyone in the room wants the bigger number. I hold that a rate and a total are different claims. The rate is validated by holding program, finish level and scope constant on both sides and pricing both at full scale. The total is a claim about a measured quantity, and it carries things a rate never touches that only a bottom-up trade build, reconciled against the rate-times-quantity figure, can earn. So the deliverable was the rate, with its basis, its scope boundary and its variance beside it, and the developer's own next document was the total.

A rate claim and a total claim

A rateA total
What it saysA price per square foot on a stated scopeWhat the project will cost
What validates itThe same program, finish level and scope boundary on both sides, priced at full scaleA quantity measured from the drawings, a bottom-up build by trade, and the two reconciled
What it carriesThe structure, the envelope, the allowances it namesEverything the rate carries, plus contingency, phasing, waste, sequencing and change orders
What it provesWhich system is cheaper per foot on this building, and by about how muchWhat to borrow and what to build
The unmeasured termNone, if the scope is pinnedThe quantity, until someone measures it, and the trade build, until someone runs it

How I came at this one

The question I asked first was which lines of a multifamily cost stack a wall system can physically touch, before anything about what the industry prices. It fit because a two-story duplex product with a shared party wall puts framing, envelope and roof on a short list, and everything else was going to cost the same on both sides. The second question was whose interest sat in each number, because I had one, and a comparison from an interested party is only worth reading if it says so and holds the constants where a stranger can check them.