We put our AI takeoff head-to-head with a senior estimator

Everyone selling “AI estimating” shows you the demo where it works. We wanted the other test: hand a real package to a senior estimator and to Forgecast at the same time, price it both ways, and see exactly where the software holds up and where it doesn’t.

The package was a real one a multi-skid structural steel job, the kind of equipment-support steel a fab shop bids every week: wide-flange framing, base plates, clip angles, a bottom deck plate. Our estimator took it off the way he always does, sheet by sheet, scaling and counting and weighing. Forgecast read the same PDF set. Then we put the two side by side.

Where they matched

On the structural steel, the two takeoffs landed within about a percent of each other. That isn’t luck. On a native CAD drawing, Forgecast doesn’t “look” at the sheet and guess it reads the actual drawn line geometry, pulls the exact member lengths and the size callouts, and weighs them from the AISC shape table. Run it twice and you get the same pounds twice. For the bulk of the framing, the tool and the estimator were reading the same reality.

The estimator caught something the software missed — and that’s exactly the kind of miss we want to hear about.

The one it missed

There was a bottom steel plate that showed up only in a plan view. It wasn’t in the beam schedule and it wasn’t in the member list, it was just drawn, in one place, on one sheet. Forgecast’s first pass didn’t carry it. The estimator did, because he’s seen that exact trick a thousand times.

Here’s what we did with that: we built a flag for it. Now when a plate appears on a plan or section view but isn’t in any schedule, Forgecast surfaces it. 
“Here’s a plate shown on the drawing that isn’t in a schedule; take it off separately.”
It doesn’t silently guess the weight, and it doesn’t silently drop it. It tells you it’s there and lets you make the call.

Quantities are one problem; rates are another

The second gap wasn’t a takeoff error at all. It was pricing. The tool’s default shop labor rate wasn’t this shop’s rate. Once we set it to the estimator’s own loaded rate, the dollars lined up. It’s a useful reminder that a takeoff has two halves: how many pounds (a drawing problem) and what they cost (your problem). Forgecast does the first and uses your numbers for the second, so the total comes out in your money, not a generic one.

The catch at the end

The part the estimator liked best came last. Forgecast doesn’t just produce a number, it reconciles line by line against your estimate and flags every difference: over, under, missing, wrong size. On this job that pass surfaced a roughly $10,000 discrepancy, a member the drawings sized heavier than the quote had carried. Caught before the bid goes out, that one check pays for the tool.

What it actually changes at the desk

None of this is the software replacing the estimator. It’s the opposite. The estimator is still the one who knows the plan-view-plate trick and reads the intent of the sheet. What the tool does is take the slow, mechanical, error-prone part — the scaling and counting and weighing — down to minutes, hand it back graded so you know what to trust, and cross-check it against your own numbers so a heavy member or a fat-fingered quantity gets caught instead of shipped.

That’s why every Forgecast takeoff comes with a grade (Bid, Budget, or Low) and a line-by-line reconcile. On this package the structural came back bid-grade, the plate got flagged, and the $10k got caught. That’s a good day at the estimating desk.

Details of the package have been kept general to protect a customer’s bid. The accuracy figures are from Forgecast’s own validation on live fabrication work.