Hiring an Estimator: When, Who and How to Do It

In most growing construction companies the owner estimates at night, after the job walks and the phone calls. It works for years, and when it stops working the failure is invisible: bids submitted at the deadline, projects underpriced by a few points, opportunities skipped entirely, and nobody comparing any estimate to what the job actually cost.

The signs that the owner can no longer estimate

In most growing construction companies, the owner estimates at night. It works until it does not, and the failure is rarely dramatic — it shows up as a slow erosion nobody attributes to estimating:

Bids are submitted at the deadline, or skipped entirely, because there was no time.
The win rate falls, not because prices are wrong but because proposals are thin and late.
Scope gaps appear in the field, discovered by a superintendent instead of during takeoff.
The owner stops visiting jobs, which is where the relationships and the quality live.
Nobody knows the real numbers, because no estimate was ever compared with the job cost afterwards.

The cost of not hiring is invisible. Bids not submitted, projects underpriced by a few points, a growing backlog of work nobody analyzed. None of it appears on a financial statement as "missing estimator", which is exactly why the hire is delayed for years.

Decide which role you are actually hiring

"Estimator" covers several different jobs, and hiring for the wrong one produces an expensive mismatch:

Takeoff and quantity specialist. Fast, accurate measurement and material quantities. Often the right first hire, and the easiest to train.
Estimator. Builds the full price: quantities, labor, production rates, subcontractor pricing, overhead and markup.
Chief estimator or preconstruction manager. Runs the process, decides which projects to pursue, manages relationships with owners and design teams.
Project manager who also estimates. Common in smaller companies, and workable only if the workload genuinely allows both.

A useful first step is to write down every task involved in producing a bid and mark which ones you actually want to stop doing. That list, not a job title, is the job description.

Keep reading — free

The rest of this article is worth the 20 seconds

Tell us where to send it and the full piece unlocks right here, along with everything else on this blog.

Rather just talk? Message us on WhatsApp.

Where they come from and what to look for

From the field. Superintendents and foremen who know how the work is really built often make the most accurate estimators, and they already understand your company.
From suppliers and subcontractors, where takeoff and quoting are daily work.
From competitors, which brings both speed and a rolodex, and which requires care about confidential information.
From construction management programs, for a longer-term investment in someone you train your way.

What matters more than software experience is judgment. Software can be taught in weeks; understanding why a crew will take longer on the third floor than on the first takes years.

Before you hire: three alternatives worth testing

A full-time estimator is not the only answer, and for companies under a certain volume it may not be the right first move:

Outsourced takeoff services. Quantities produced per project for a fee, which removes the most time-consuming part of the work without adding payroll. Accuracy depends on drawing quality and on how well you specify what you need.
A part-time or retired estimator, often available two or three days a week, which suits companies bidding a handful of projects a month.
Better software and templates, which frequently cuts estimating time substantially when the real bottleneck is rebuilding the same spreadsheet on every job.

Each of these buys time and none of them builds institutional knowledge, which is the argument for eventually hiring. A practical path is to outsource takeoff for a year, use the freed-up hours to build a proper cost history, then hire someone into a company that can actually train them.

Paying an estimator without distorting the bids

Compensation quietly shapes estimating behavior, and some common structures create exactly the wrong incentives:

Commission on jobs won pushes toward lower numbers and thinner margins, which is the opposite of what an estimator is for.
Bonuses on projects completed under budget encourage padding, which loses bids the company should have won.
A salary with a company profitability bonus aligns the estimator with the outcome that matters without tying them to any single bid.
Recognition for accuracy — estimates that land close to actual cost in either direction — is the behavior worth rewarding explicitly.

Good estimators are also scarce and portable, and they leave for reasons that have little to do with money: being blamed for field problems they warned about, being excluded from the bid decision, and never learning how their estimates actually turned out. Fixing those three costs nothing and retains people that a raise alone would not.

Test them before you hire them

Interviews reward people who talk well about estimating. A paid practical exercise reveals who actually estimates well:

Give a real project you already built, with drawings and the actual final cost withheld.
Ask for a takeoff of two or three systems and a narrative of assumptions.
Review how they handle ambiguity. The best answer to an incomplete drawing is a written assumption, not a guess or a stall.
Compare their number to your actual cost, but judge the reasoning more than the total.
Pay for their time. Serious candidates are working, and free multi-hour tests filter for the wrong people.

The first ninety days decide everything

Estimators fail in new companies for one reason above all: they were handed bids without being handed the company's actual costs. The onboarding that works is unglamorous:

Walk active jobs with the superintendents in the first two weeks.
Review three completed projects line by line: what was estimated, what it cost, what explains the difference.
Hand over the historical cost data, however messy it is, and be honest about what it does not cover.
Introduce them to subcontractors and suppliers personally, because those relationships are half the job.
Start with smaller bids and review each one together before submission, for the first several.
Explain the unwritten rules — which clients get different treatment, what the company will not bid, how aggressive the markup usually is.

Feed the estimator or the estimate is a guess

An estimator without job cost feedback is producing opinions. The loop that makes them accurate is a company responsibility, not an individual one:

Consistent cost codes used in the field and in accounting, matching the estimate structure.
Job cost reports the estimator actually reads, not only the accountant.
A post-project review on every job, comparing estimate to actual by category.
Production rates that are updated based on your crews, not on a published national table.
Field feedback without blame. A superintendent who is punished for reporting an underrun stops reporting anything.

The estimate is a prediction; the job cost is the grade. A company that never compares the two is hiring someone to make expensive guesses with better formatting.

How to know whether they are good

Estimate accuracy — the variance between estimated and actual cost by category, tracked over many jobs.
Win rate by project type and client, which reveals where your pricing is competitive and where it is not.
Bid volume, meaning how many qualified opportunities were actually pursued.
Scope gaps discovered in the field, which should decline steadily.
Turnaround time from invitation to submission.
Subcontractor coverage — how many real quotes were obtained per trade rather than one and a guess.

Judge the first two over at least a year. Estimating is a long-cycle discipline, and a bad quarter can be entirely the market.

What the owner must keep doing

Hiring an estimator does not remove the owner from pricing, and the companies that treat it that way lose money quietly:

The go or no-go decision on which projects to pursue stays with leadership.
Final markup and risk pricing is a business judgment, not a takeoff.
Client relationships that produce negotiated work cannot be delegated with the spreadsheet.
The bid review meeting before submission, where the field, the estimator and the owner look at the same number.

The arithmetic of the hire

Round numbers, for a company doing $8 million a year:

Fully loaded cost of an experienced estimator: roughly $135,000 including benefits and software.
Bids submitted rises from 40 to 70 per year, because capacity is no longer the limit.
At a 20% win rate, that is 6 additional projects, averaging $400,000 — $2.4 million in additional revenue.
At a 10% gross margin, that is $240,000, before counting the estimates that stopped being wrong.
The owner returns to the field and to client relationships, which is where the next negotiated project comes from.

Mistakes that waste the hire

Hiring without historical cost data and expecting accuracy anyway.
Judging them in the first quarter, before a single estimated job has been completed.
Keeping the owner as a bottleneck who reviews everything but is never available.
No post-project reviews, which removes the only feedback that improves estimating.
Isolating them from the field, producing estimates that are arithmetically perfect and practically wrong.
Loading them with project management until estimating becomes the thing they do at night — which is where this problem started.

Where to start

Before recruiting, do one thing: take three completed projects and compare the estimate to the final cost, category by category. That exercise tells you what your real production rates are, how reliable your cost data is and which parts of estimating are actually hurting you. It also creates the training material your new estimator will need in week one. Companies that do this first hire the right role and keep the person. Companies that skip it hire someone to make faster versions of the same mistakes.

More bids only help if better projects are invited.

We build the offer, run the traffic and close the follow-up gap so your estimator is pricing the work you want — then report what it returned.

Talk on WhatsApp See how it works

Frequently asked questions

When should a contractor hire an estimator?

The usual signal is not revenue but symptoms: bids going out at the deadline or being skipped entirely, a falling win rate caused by thin and late proposals rather than by price, scope gaps being discovered in the field instead of during takeoff, the owner no longer visiting jobsites, and nobody comparing any estimate to the final job cost. The cost of waiting is invisible because it never appears on a financial statement as a missing estimator, which is why the hire is typically delayed for years. Before recruiting, it is worth testing three alternatives: outsourced takeoff services, a part-time or retired estimator working a few days a week, and better software or templates when the real bottleneck is rebuilding the same spreadsheet on every project.

How do you evaluate an estimator candidate?

Interviews reward people who talk well about estimating, so use a paid practical exercise instead. Give a real project the company already built, with the actual final cost withheld, and ask for a takeoff of two or three systems plus a written narrative of assumptions. What matters most is how the candidate handles ambiguity: the strongest answer to an incomplete drawing is a documented assumption rather than a guess or a stall. Compare their number to your actual cost, but judge the reasoning more than the total. Pay for their time, because serious candidates are already employed and unpaid multi-hour tests select for the wrong people. Judgment matters more than software experience, since software can be taught in weeks and production intuition takes years.

Why do estimators fail after being hired?

Most often because they were handed bids without being handed the company's actual costs. An estimator without job cost feedback produces opinions, and creating that feedback loop is a company responsibility: consistent cost codes used in the field and in accounting that match the estimate structure, job cost reports the estimator actually reads, a post-project review on every job comparing estimate to actual by category, production rates updated from your own crews rather than a published table, and field feedback given without blame. The other common failures are judging them within a quarter, before a single estimated project has been completed, isolating them from the field, and loading them with project management until estimating becomes the thing they do at night.