The work, decision by decision

The work, one question at a time

1. Fix the basis before pricing anything. What was known: the developer had a plan set and a benchmark, and the manufacturer had a cost story built on a sample wall. The question I asked was what the comparison would hold constant, because a comparison is only as good as the list of things it refuses to let move. The answer was slab plus structure, vertical construction only. Building slabs and under-slab trenching, the structural system, the interior build-out by allowance and the mechanical, electrical and plumbing systems were in on both sides. Site work, amenities and off-site utilities were out on both sides. Finish allowances were held identical across both options, so no part of the gap could come from a nicer kitchen on one side of the page. What it changed: the gap could only come from the structure.
2. Take the benchmark as a range, use its midpoint, and say so. What was known: the developer's number was what wood-frame multifamily budgets at in that market. I used the midpoint of the market's budgetary range for the stick side and wrote the range beside it, because the developer deserved to know that the baseline itself had a width. Pretending the benchmark was a hard bid would have made the gap look sharper than it was. What it changed: the stick side carried its own honest uncertainty from the first page.
3. Map what the system can physically touch. What was known: on this product, the panel system replaces the wood frame and most of the exterior envelope and leaves the interior alone. The question was which cost lines could move at all, because that list bounds the size of any possible gap before a single rate is applied. What it changed: everything in the right-hand column of the box below was pinned before pricing began, and the comparison became a test of the left two columns, not of the building as a whole.

1. Price the system side at full scope, on the project's own plans. What was known: the plan set showed two-story duplex buildings with a shared party wall. The system side carried the panel material at the manufacturer's pricing as it stood that week and our own labor to set it, priced against the same program and the same scope boundary as the stick side. What it produced: a delta below the benchmark, driven by removing the framing and envelope scopes and by the schedule compression that follows, which shortens general conditions and overhead. What it changed: the manufacturer's sample-wall story was replaced by a number built on the developer's drawings.
2. State the variance where it lives. What was known: the delta would be bought out by subcontractors, and buyout is where a budgetary number meets the market. I put the variance on the delta at subcontractor buyout, not on the whole rate, because the delta is the claim being made and the stick side already carried its own range. What it changed: the developer could see the width of the gap, not only its center.
3. Stop at the rate. What was known: a validated rate times a building area is correct arithmetic and a new claim. The question I asked was what a project total would need that this comparison did not have, and the answer was a measured quantity from the drawings, a bottom-up build by trade, and the two reconciled before either went to anyone. Neither existed at a budgetary stage. What it changed: the comparison went to the developer as a rate with its basis and variance, and the structural system selection stayed where it belonged, inside the developer's broader investment and operating strategy.

What the two numbers say, and how wide each one is

In one line: the stick midpoint, the system-adjusted rate, and between them the framing and shell line that falls and the panel install line that gives part of it back. The two end rates are the comparison's own. The split between the cut and the install line is an allocation drawn to show the mechanism, and it is labeled that way behind the gate, because the comparison as issued attributes the gap to the removed scopes and to schedule compression on general conditions without pricing them as separate lines. A reader who wants the mechanism verified should ask for the material and labor split behind each line, and so should I.

What I would say to a lender: the gap between the two rates is narrower than the width of the market's own budgetary range for wood framing. Both things are true at once. The system is cheaper on this building, on identical scope, by a margin that holds through its buyout variance. And a hard general-contractor bid on this program that came in low in the benchmark's range would eat most of the gap. That is the reason the comparison is a rate and not a total, and it is the reason the developer's next move is a hard bid on both sides, not a bank draw.

What I kept, replaced and installed

Kept: the developer's benchmark as the baseline, at its midpoint, with its range printed beside it, because the number the developer already trusted was the right thing to test against. Kept: the finish allowances identical on both sides, so the comparison could not be won in the kitchen.

Replaced: the manufacturer's sample-wall arithmetic, with a full-scope price on the developer's own plan set. Nothing in the developer's process changed; the document in front of him did.

Installed, in LÏEF's own estimating, and I put it in myself: a basis sheet in front of every system comparison that states the scope boundary, the constants held, the lines the system can touch, the basis of the baseline and where the variance sits; and a rate-to-total gate, under which no project total leaves the shop on a rate times an area. A total waits for a measured quantity from the drawings and a bottom-up trade build, reconciled before either goes to a developer, a lender or a public page. The faulty logic it corrects is an ordinary one in estimating. A rate earns credibility by surviving a like-for-like comparison, and multiplication lets a total borrow that credibility without earning its own, because the arithmetic is correct and nobody stops to ask whether the quantity was ever measured. It had to change now because this was the first time the comparison went to a developer at this scale, and a number at a budgetary stage travels. Other people carry it into documents that treat it as a total, and the place to stop that is before the number leaves.

What it costs to hold the line, and what I watch

Holding the line costs a sales document. A comparison that says budgetary, midpoint of a range, variance at buyout and no total reads slower than the sheet the manufacturer would have liked to hand the developer, and a competitor with a cleaner page gets an easier afternoon. It also costs me the mechanism claim. Until the material and labor split behind the framing line and the install line is on paper, the gap is a rate I stand behind and a mechanism I describe, and I would rather print that distinction than paper over it.

What I watch. The hard stick bid on the program, because a bid that lands low in the benchmark's range narrows the gap and a bid that lands high widens it, and either one turns a budgetary comparison into a decision. Local erection capacity and plant lead time, because a lower rate is not a better decision if the crews and the plant cannot deliver on the project's clock. Mechanical, electrical and plumbing routing through a panel shell, which most panel projects price as chases and penetrations and which this comparison holds unchanged by allowance. The schedule compression on general conditions, which the comparison claims and the first buildings will measure. And appraiser and underwriter familiarity, because the market prices the stick default for a reason, and the thinner track record is a cost the rate does not carry. The structural system selection was the developer's to make on his broader investment and operating strategy, and this comparison was built so he could make it with the constants in view and the width of every number beside it.

What it produced

The system-adjusted rate landed below the stick-framed midpoint on identical scope, with the variance stated at subcontractor buyout rather than on the whole rate. The gap was real, and it held narrower than the width of the market's own budgetary range for wood framing, which is itself a reason to get a hard bid rather than bank the number. The comparison went to the developer as a rate with its basis and variance beside it; the structural system decision stayed his, inside his own investment and operating strategy. A project total was never part of the deliverable: that waits on a measured quantity from the drawings and a bottom-up trade build, reconciled before either number leaves the shop.

A slice of the project list

A few related projects.

• Canyon Corporate: takeoff, pricing structure and bid revision for a Phoenix office-to-residential conversion (2026)
• A modular housing fabrication center (Arizona, 2026)
• Soft-Story Retrofits: takeoff and bid method for a multifamily retrofit program (2026)