Stops-Per-Day Capacity Estimator

The estimate is a bottom-up stop-cycle model. Subtract your fixed daily overhead from the paid workday to get productive minutes, divide by the time one stop takes (service + drive), and round down — you never count a stop you can't finish.

productiveMin   = workdayMin − fixedOverheadMin     (workdayMin = hours × 60)
cycleMin        = serviceMin + driveMin
stops/day       = floor(productiveMin ÷ cycleMin)
driveShare      = (stops/day × driveMin) ÷ productiveMin
dailyRevenue    = stops/day × avgTicket
monthlyStops    = stops/day × workingDays × techs
monthlyRevenue  = monthlyStops × avgTicket
sensitivity     = floor(productiveMin ÷ (serviceMin + max(driveMin − 5, 0))) − stops/day

Round down, always. Capacity is a physical ceiling, so a fractional stop is no stop. The monthly roll-up floors the daily count first, then multiplies by working days and technicians.

Drive time is the dominant lever. The tool shows what shaving 5 minutes of drive between stops would add — on a typical route, that's one or two more stops a day. Drive-time share above 40% of the productive day is flagged as a route-density warning; it never caps the computed stops/day.

Default bands (12–18 stops/day general pest, 6–10 complex/termite; 5–7 productive hours; $800–1,200 daily route revenue) are typical industry figures used as sanity captions, not hard-coded multipliers. This tool keeps no addresses, no map, no live route sequencing, and no saved stop/customer records — the monthly figure is a recomputation of your current inputs.

Sources: ServiceWorks technician-utilization / capacity model (productive ÷ available); CalcMyBid billable-hours "5–7 productive hours/day" anchor; Pest Control Millionaires route- efficiency bands (12–18 / 6–10 stops; $800–1,200/route).