It comes up on almost every call: “We already run HeavyBid — do we still need this?” The short answer is yes, because the two tools sit at opposite ends of the same bid week and never touch the same number. HeavyBid (and B2W) build your estimate — quantities, production rates, the bid you hand to the owner. Sub-bid leveling, which is the heavy-civil estimating layer Bid Reasoner provides, evaluates the 5–15 subcontractor bids that come back to you on each package. One builds your number. The other tells you which sub’s number to trust. They are not competitors; one feeds the other.
What HeavyBid and B2W actually do
HCSS HeavyBid and B2W Estimate are takeoff and cost build-up engines. You give them quantities — cubic yards of excavation, tons of asphalt, linear feet of pipe — and they help you price the work from the ground up:
- Takeoff and quantities. Measure the plans, capture the units of work in each pay item, and roll them into a structured estimate.
- Crew and production rates. Build activities from labor, equipment, and material with production rates, then let the cost recalculate as you tune the crew.
- Cost build-up. Layer indirects, markup, bond, and contingency on top of direct cost to arrive at a sell price.
- Your bid to the owner. The output is the GC’s own number — the figure you submit on bid day for the self-perform scopes you carry.
This is where most of an estimator’s week goes, and it is genuinely hard, specialized work. None of it is what Bid Reasoner does. We do not measure plans, we do not hold production rates, and we never generate a quantity. If you need takeoff, you need HeavyBid or B2W — full stop.
What sub-bid leveling does
The scopes you don’t self-perform — striping, electrical, structural steel, guardrail, drilling, landscaping — come back to you as bids from subs. On a mid-size highway or bridge package that is routinely 5 to 15 PDFs per scope, each in its own format, each carving up the work differently. Leveling is the job of putting those bids on a common basis so you can compare them honestly and defend the pick. Concretely, that means:
- Reading each sub bid PDF and extracting every line item, regardless of how the sub formatted it.
- Normalizing line items to your scope of work so “mobilization,” “mob/demob,” and “general conditions” land in the same row across all bidders.
- Mapping coverage against your SOW to surface what each sub left out and what they added — the apples-to-oranges that sink a naive low-bid pick.
- Scoring each bidder on six dimensions: price, scope, schedule, compliance, performance, and risk.
- Recommending a winner with page-cited evidence from the source PDFs, plus the seven Word documents (Reasoned Award Memo, Evidence Report, and more) you need to put the award on the record.
For a step-by-step on the leveling mechanics themselves, see our walkthrough on how to level subcontractor bids. The point here is narrower: this work starts after HeavyBid’s work ends.
The handoff between the two
Picture a single bid week on a $14M reconstruction package. The two tools run in sequence, not in parallel competition:
- HeavyBid / B2W (days 1–9): your estimators take off quantities and build the self-perform number. They also set a budget line for each subbed scope — the carry you expect striping, electrical, and steel to cost.
- Subs respond (days 7–11): quotes land in your inbox as PDFs, often in the last 48 hours, in every format imaginable.
- Sub-bid leveling (days 11–12): you load those PDFs, normalize and score them, catch the scope gaps and price outliers, and pick the sub to carry — with the memo to back it.
- Back to HeavyBid (bid day): the leveled sub numbers drop into your estimate as the subbed-scope carries, and you finalize the bid to the owner.
Side-by-side: what each tool owns
The cleanest way to see that these don’t overlap is to put the two jobs next to each other.
| Dimension | HeavyBid / B2W (estimating) | Sub-bid leveling (Bid Reasoner) |
|---|---|---|
| Core job | Build your own estimate | Evaluate the sub bids you receive |
| Input | Plans, quantities, crews, rates | 5–15 subcontractor bid PDFs per package |
| Does takeoff? | Yes — that is the point | No, never |
| Direction of work | Your number going out to the owner | Sub numbers coming back to you |
| Key output | Your bid / sell price | Leveled scores + recommended award + memo |
| When in the week | Most of the week | The 24–48 hours before bid day |
| Who lives in it | Estimators | Precon lead / VP precon making the award call |
Notice there is no row where they fight over the same task. The closest thing to overlap is the subbed-scope budget line — and even there, HeavyBid holds your expected carry while leveling tells you which actual bid to take against it.
Why they are complementary, not competitive
Three reasons the “replace or keep?” framing is the wrong question:
1. Different math, different data
Estimating math is bottom-up: quantity × rate, rolled up with markup. Leveling math is comparative: each line normalized against the peer median of the bids you actually received, with four deterministic risk rules running on top — unbalanced unit prices at or below $1.00, peer outliers more than 2× or under 0.5× the peer median, total-bid outliers more than 20% off the group, and front-loaded mobilization above 10% of the total. HeavyBid has no peer set to compare against, because it only knows your own estimate. Leveling has no quantities to take off, because the subs already priced the work.
2. Different failure modes
A weak estimate loses you the job (too high) or wins you a loser (too low). A weak leveling job is quieter and more dangerous: you award to the “low” sub who quietly excluded traffic control, and the gap surfaces as a change order in month three. Catching that exclusion is a scope-coverage problem, not an estimating one — and it’s exactly what gap analysis on the normalized line items is built to flag.
3. Different evidence trail
When an owner or your own PM asks “why this sub?”, a HeavyBid file won’t answer it. The defensible answer lives in the leveling record: the recommended winner, the six-dimension scores, page-cited quotes from each bid PDF, and a forced-override audit trail if your precon lead went against the recommendation. If you want a quick read on how much that defensibility is worth in change-order risk and rework hours, the free ROI calculator puts rough numbers on it in a couple of minutes.
So — do you keep HeavyBid?
Yes. Keep HeavyBid or B2W exactly where it is. Bid Reasoner doesn’t touch your takeoff, your crews, or the number you send the owner. It sits one step downstream, on the pile of subcontractor PDFs that lands every bid week, and turns that pile into a leveled, scored, defensible award. If your estimators are still leveling those bids by hand in a spreadsheet the night before bid day, that’s the gap the heavy-civil estimating layer closes — without asking you to rip out a thing.