How Many Estimates Does It Take to Win a Job?

A remodeler asked us this straight: "How many estimates does it take to win one job?" He wasn't being philosophical. He'd sent 11 estimates in a month, booked 4 jobs, and wanted to know if that was normal or if something was broken.

The math answer is simple. The useful answer is different, and it has almost nothing to do with the number itself.

{h2}The Math Behind the Question

Start with close rate, because that's what actually drives the number. If you close 40% of the estimates you send, you need 2.5 estimates on average to land one job. Close 25%, and it's 4 estimates per job. Close 50%, and it's 2.

So the direct answer: at a typical residential close rate of 30-40%, expect to send somewhere between 2.5 and 3.5 estimates per job won. If you're outside that range, it tells you something — but not necessarily what you think. What is a good close rate on contractor estimates? walks through benchmarks by trade, because a 25% close rate on high-ticket remodels is fine, while the same number on $400 handyman jobs usually means something's off in your pricing or follow-up.

Here's the trap: contractors read that math and treat it as a target. "I need to send more estimates to hit my number." That's backwards. The number of estimates it takes to win a job isn't something you should be optimizing. It's a symptom. The thing you can actually control — and the thing that determines whether chasing a higher win rate makes sense at all — is what each estimate costs you to produce.

{h2}Why Close Rate Alone Is the Wrong Thing to Obsess Over

Picture two contractors, both closing 35% of their estimates.

Contractor A builds each estimate by hand: measures the job, drives home, opens a spreadsheet, prices it out, formats a PDF, emails it. Call it 2 hours per estimate, all-in. To win one job, he's burning roughly 5.7 hours of unpaid work (2.5 estimates × 2 hours) before he ever picks up a tool.

Contractor B uses a price book and a tablet on-site. He builds the estimate standing in the room, taxes and markup calculate automatically, and the customer gets a professional PDF before he's back in the truck. Call it 15 minutes per estimate. Same 35% close rate, same 2.5 estimates per job — but that's under an hour of total estimating time to win the job.

Same close rate. Wildly different businesses. Contractor A is one bad month away from feeling like estimating is eating his life, because it is. Contractor B can afford to send more estimates, follow up more aggressively, and even lose a few he wouldn't have minded losing, because the cost of losing is almost nothing.

That's the real lever: cost per estimate, not estimates per job.

{h2}The Math Changes Everything Once You Add Time

Run the numbers on what a lost estimate actually costs, and the close-rate conversation looks different.

At 2 hours per estimate and a 40% close rate, every job you win carries about 3 hours of estimating overhead baked into it (1.5 losing estimates × 2 hours, roughly). If your average job profit is $600, that's real money walking out the door in time you'll never bill for. You genuinely can't afford to lose 60% of your estimates at that pace — the math punishes you for every "no."

At 15 minutes per estimate and the same 40% close rate, the overhead per win drops to about 22 minutes. Losing 60% barely registers. You can send estimates more liberally — including to borderline leads you'd otherwise screen out — because the downside of a "no" is trivial.

This is why two contractors can look at the exact same close-rate benchmark and draw opposite conclusions. One should be tightening who they estimate for. The other should be sending more estimates to more people, faster, because their cost of being wrong is nearly zero.

{h2}What to Actually Do With This

Before you worry about raising your close rate, figure out your real cost per estimate. Time yourself on the next five: site visit, pricing, formatting, sending. Most contractors doing this by hand land somewhere between 45 minutes and 2 hours depending on job complexity — and most underestimate it, because the work is scattered across a notebook, a calculator app, and a text thread rather than happening in one sitting. The hidden cost of creating estimates manually breaks down where that time actually goes.

Once you know the number, you have two honest paths:

{ul}"If estimates are cheap to produce (under 20-30 minutes), stop worrying about close rate and focus on volume and speed of follow-up instead. [How fast should contractors respond to new leads? matters more than squeezing out a few extra percentage points of win rate.","If estimates are expensive (an hour or more), your priority isn't sending more — it's cutting the time each one takes, so a 60% loss rate stops being a math problem."]

{h2}Cutting the Cost, Not Just Counting the Losses

The fastest way to shrink cost per estimate is to stop rebuilding pricing from scratch every time. A price book with your real labor and material rates already loaded means you're selecting line items on-site instead of doing mental math in the truck. Our free estimate calculators for painting, roofing, fencing, drywall, flooring, and pressure washing are a reasonable starting point if you want to see what that looks like before committing to anything.

Trusso takes that further: estimates are generated from your own price book, built on-site in minutes, with 3D room scans that cut down on measuring time entirely. The goal isn't to win every estimate — nobody does. It's to make losing one cost you almost nothing, so you can send more of them, follow up harder, and let the math work in your favor instead of against you. Pricing is flat at $29/mo for an owner plus 2 crew, $59/mo up to 10, or $99/mo unlimited — no per-estimate fees, 14-day free trial, no contract.

So: how many estimates does it take to win a job? Usually 2 to 4, depending on your close rate. But the number that decides whether your business is healthy isn't that one — it's how many hours each of those estimates costs you. Fix that, and the win-rate math stops being something to fear.