Cost per square foot calculator: ROM checks both directions

What cost per square foot includes, and what it hides

Cost per square foot (psf) is the blunt instrument of construction estimating: total cost divided by gross floor area. Its usefulness is exactly equal to how clearly you define both numbers. The trouble is that two estimators can quote wildly different psf for the same building and both be right, because they drew the scope boundary in different places.

A psf figure may include only hard costs (the physical construction: structure, envelope, finishes, mechanical, electrical, plumbing) or it may also carry soft costs (design fees, permits, financing, insurance, contingency). It may or may not include sitework, demolition, utilities to the property line, and offsite improvements. It almost never includes the land. So before any number means anything, you have to know which costs are inside the fence and which were left out.

Why the same building moves by multiples

Cost per square foot is not one rate, it is a family of rates that shift with building type, region, and geometry. A warehouse shell, an office fit out, and a hospital are not variations on a theme; they are different products, and their psf can differ by a factor of five or more because of system density (how much mechanical, electrical, and plumbing per square foot), finish level, and code requirements.

Region moves it through labor rates, material logistics, and local code. Building height and floor plate move it because tall and skinny buildings carry more structure and vertical transportation per usable foot than low and wide ones. A renovation inside an occupied building carries phasing and protection costs a greenfield slab never sees. None of this is captured by a single national average, which is why averages make poor estimates.

Use it as a sanity check, not a bid basis

The honest job for a psf number is the reasonableness check. You finish a detailed quantity takeoff and assembly estimate, divide by the area, and compare the resulting psf to your own history for that building type and region. If your bottom up number lands far outside your historical band, that is a signal to hunt for an error: a missing system, a double count, a units mistake. The psf did not produce the estimate; it audited it.

What psf cannot do is serve as the bid. A bid built by multiplying area times an assumed rate has no quantities behind it, no scope definition, and no defensible basis when a client asks why. Psf is a top down screen; the bid is a bottom up build. For the full bottom up workflow see how to estimate construction costs.

Build your own psf from job actuals

The single most valuable psf to you is the one you compute from your own completed projects, because it already carries your scope conventions, your region, and your overhead structure. After each job, divide the final cost by the gross area and file it by building type. Over time you accumulate bands that are calibrated to how you actually build and price, which is exactly what the Derive your psf mode above is for.

Keep the hard cost and soft cost split explicit so your bands stay comparable; see the glossary on hard costs and soft costs. That discipline is also where Ruh helps: it reads your drawings, builds the quantity takeoff, and prices it against your own price book so your psf history comes from real assemblies rather than guesses, with your estimator reviewing every line.