Three estimators, 60 percent more bid capacity, and nothing thinner about the work
The usual way to bid more jobs with the same team is to spend less time on each one. A three-person estimating team carrying up to 200 bids a year added around 60 percent more capacity without making that trade.
Author
Ido Gedanken, CEOPublished

Bring a current or completed project and see how Piper saves review time, surfaces scope gaps, and applies your company's knowledge.
See Piper on your project- Type
- Customer story
- Read
- 4 min
- Published
On this page
Three estimators. Between 100 and 200 bids a year. Work that out per person and it is a new tender landing every working day or two, each one a fresh pile of documents nobody has read yet.
That team now carries roughly 60 percent more bid capacity than it could before, with the same three people, and without spending less time on the work that decides the number.
The contractor is not named, at their request. The figures are published with their agreement.
About 60% more
12 to 13 hrs
4 hrs to 1.5 hrs
The challenge
- Three estimators against a bid calendar of 100 to 200 jobs a year, roughly one new tender each per working day or two
- About four hours of reading before anyone could say whether a tender was even worth pursuing
- Scope and takeoff preparation consuming the bulk of every bid, leaving the judgment work for whatever time was left
What changed
- The first pass dropped to about ninety minutes, so walking away early stopped being expensive
- Scope and takeoff preparation dropped by about a third
- The same three people now carry roughly 60 percent more bids, at the same depth of review
Why more capacity is usually a bad deal
Any estimating team can bid more jobs. The question is what it costs.
The normal way to raise capacity without hiring is to spend less time per bid, and the time always comes out of the same places. Scope gets a lighter read. Fewer exclusions get chased. More of the number rests on an assumption nobody had time to test. The bids go out faster, the win rate may even hold, and the cost does not surface until a job is running and somebody finds out what was carried.
That trade is so normal it is barely noticed. It is also a bad one, because capacity bought by lowering the bar is not capacity. It is deferred risk, and it arrives later with interest.
We could always have bid more jobs. We just would have had to do a worse job on each one, and everybody knows what that costs you two years later. That is the trade we did not want to make.
Why the confidence held
The reason is in where the hours came from.
None of the savings came out of judgment. No decision moved from a person to a machine. What changed is the work surrounding the decision: opening the documents, reading them, finding what matters, structuring it, and assembling it into something a person can act on. That work is necessary, it is expensive, and almost none of it is what an estimator is actually paid for.
Piper does that layer. The estimator still sets every number, still decides what to carry, still owns the price. They simply reach those decisions with the reading done and the material organised, rather than spending most of the bid getting to the point where the real questions can be asked.
So the review did not get thinner. If anything it got easier to do properly, because the estimator arrives at it with hours left instead of on the last afternoon.
The work I am actually good at is the last few hours of a bid. I used to get to it exhausted. Now I get to it with time.
The numbers
| Stage | Before | After | Time back per bid |
|---|---|---|---|
| Initial project review | About 4 hours | About 1.5 hours | About 2.5 hours |
| Scope and takeoff preparation | Baseline | About a third less effort | About 8 hours |
| Proposal creation | Baseline | Faster | About 2 to 3 hours |
| Manager review | About 1 hour per bid | Not yet measured | Excluded from the total |
About twelve to thirteen estimator hours back per bid, before counting anything manager review gives back. That line is excluded on purpose. There is about an hour of it per bid today and the team expects it to fall further on work produced by junior estimators, where the review is heavier. None of that is in the figure.
Turning that into capacity: scope and takeoff dropped by about a third, and that third is worth about eight hours, so the stage used to take around twenty four hours and now takes around sixteen. With the first pass moving from about four hours to about one and a half, those two stages went from roughly twenty eight hours a bid to roughly seventeen and a half. Twenty eight divided by seventeen and a half is 1.6.
Sanity check: run three estimators through a normal working year at the old hours per bid and you get a calendar of roughly 140 to 150 jobs, which sits inside the 100 to 200 the team actually runs.
The initial project review figure is measured. The scope, takeoff and proposal savings are the team's own working estimate of their workflow rather than instrumented measurements, and the manager review saving is excluded rather than estimated.
Saying no is the other half
One number deserves pulling out even though it is not the headline.
The first pass, the read that answers whether a tender is worth pursuing at all, went from about four hours to about ninety minutes.
At this bid volume that changes the economics of saying no. A no-bid decision that used to cost half a day now costs an afternoon. Walking away early stops being a luxury, which means fewer hours spent on jobs that were never winnable, and more spent on the ones that were.
Half a day to work out that we did not want a job is half a day we did not spend on one we did. At our volume that is the whole game.
The point
More bids is the easy half of this. Every team knows how to produce more bids, and most know exactly what it costs to do it that way.
The result worth having is more bids at the same standard: the same depth of read, the same exclusions chased, the same confidence in the number that goes out. That is what the extra sixty percent is made of here, and it is the only version of extra capacity that is still there in two years.
See also where preconstruction teams spend their time, and for a review on a much larger bid, what a final bid review found in a bid that was already finished.
Related reading
Where do preconstruction teams spend their time?
Bid leveling and scope assembly dominate precon hours (often 40-50 hours of leveling and 30-40 hours of MEP scope work per project), leaving little capacity for judgment. A synthesized view of where the time goes.

Why bid leveling eats estimator time
Manual quote comparison hides exclusions, scope gaps, and carry risk. Here is where the hours actually go before judgment even starts, and how to measure it on your own projects.

Construction scope generation: a practical guide for GCs
How general contractors turn drawings, specifications, addenda, and company standards into trade scopes a subcontractor can price, an estimator can trace, and a senior reviewer can challenge.

A finished bid, one more review, and a price that changed before it went out
A $2.5B general contractor had finished a bid and reviewed it internally. One more pass found 38 issues, a third of them serious enough to hold the price. None of them were arithmetic.

Piper removes manual review from the critical path and brings project data, company knowledge, and expert checks into every preconstruction decision and workflow
See Piper on your project
Bring a current or completed project and see how Piper saves review time, surfaces scope gaps, and applies your company's knowledge.