Estimate slots per month
People × estimates per person per week × 4.33, the average number of weeks in a month.
Before you buy more leads, check whoever runs the estimates. If their week is full, more leads just wait longer.
By the BlueSmith team · Updated
Revenue your sales team could still sell per month: $219,600
2 people × 8 estimates a week (4.33 weeks a month), 40 booked now, 30% closed at $25,000.
See what we’d build for these numbersStarts with example numbers. Change them to yours. Arithmetic only, not a promise of results.
Enter how many people run estimates and how many one person can handle in a week.
Add your booked estimates per month, close rate, and average project value.
If open slots are near zero, sort out sales capacity before you add leads.
People × estimates per person per week × 4.33, the average number of weeks in a month.
Estimate slots − booked estimates. If you’re already booked past capacity, it shows zero.
Open slots × close rate × average project value. What the empty part of the calendar could sell at your normal rate.
2 people × 5 estimates a week × 4.33 = 43.3 slots. 30 booked leaves 13.3 open. At a 25% close rate and $20,000 a job, that’s about 3.3 jobs and $66,500 a month.
That one measures production: jobs your crews can build. This one measures sales: estimates your people can run. A full sales calendar with idle crews is a different problem from the reverse.
What one person really does in a normal week, counting drive time, write-ups, and follow-up calls. Not the best week they ever had.
No. It treats every booked estimate as held. No-shows free up a slot but don’t bring revenue. The no-show cost calculator covers that side.
Open slots show zero. In practice, estimates get pushed out and homeowners wait, which is when they call someone else. That’s the case for another estimator or tighter qualifying before booking.
Seven questions. Two minutes. See the one part of your engine holding your projects back.
Show me where I’m losing jobsFree 2-minute assessment · No pitch, no obligationAvg response time 2.5 minutes