Industry
Snow Removal Estimating Software:Per-Push, Per-Event and Seasonal Prices from Site Measurements and Snowfall Normals
Snow removal estimating software on HubSpot: FieldRanger prices per-push, per-event and seasonal contracts from site measurements and snowfall normals.
Snow removal estimating software turns a site's measurements and the local snowfall record into a price for a winter of plowing and salting. FieldRanger builds that estimate on the HubSpot deal or in FieldRanger, and the won deal becomes the jobs, salt logs and invoices of the season.
Estimating is the selling half of snow removal business software: the estimate decides what each storm is worth before the first flake falls. Three contract types divide the weather risk differently between contractor and customer, and each one needs a different input from the snowfall record. This page works through those inputs for one city, Duluth, Minnesota, and one published salt rate.
Contract types and the risk each one prices
| Contract | Billed per | Input the estimate needs | Weather risk |
|---|---|---|---|
| Per push | Each plowing pass at or above the trigger depth | Price of one pass for the site | Customer pays more in a heavy winter |
| Per event | Each storm, which may be tiered by total depth | Price per depth tier | Customer pays more in a winter with many storms |
| Seasonal | A fixed price for the winter, in installments | Expected number of trigger events | Contractor absorbs a heavy winter, keeps the margin of a light one |
The per-push and per-event prices come from the site: area, equipment, hours and salt. The seasonal price adds one more input, the number of events a normal winter brings, and that number comes from climate normals.
Duluth snowfall normals as estimate inputs
NOAA's National Centers for Environmental Information publish 1991-2020 normals for each weather station, including the average number of days a year with snowfall at or above set depths (NCEI, annual and seasonal normals, Duluth station USW00014913, checked November 12, 2026). For Duluth:
| Measure | Normal |
|---|---|
| Annual snowfall | 90.2 inches |
| December to February snowfall | 50.6 inches |
| Days with at least 0.1 inch of snowfall | 62.4 |
| Days with at least 1 inch | 24.8 |
| Days with at least 2 inches | 13.8 |
| Days with at least 3 inches | 8.7 |
| Days with at least 5 inches | 4.2 |
| Days with at least 10 inches | 0.7 |
The counts are calendar days, not storms. A storm that drops 3 inches on each of two days counts twice, and a storm spread as 1.5 inches on each of two days counts at neither the 2-inch nor the 3-inch line. An estimator reads the table as the expected number of days a crew is sent out at a given trigger, which is the number a seasonal price has to cover.
Seasonal price as a count of expected events
A seasonal price is a per-event price multiplied by the number of events the contractor expects to plow. With Duluth's normals, the trigger depth sets that multiplier:
- At a 2-inch trigger, a normal winter brings 13.8 trigger days. A seasonal price equal to 13.8 per-event prices breaks even in a normal winter.
- At a 1-inch trigger, the count rises to 24.8 days, 1.8 times as many. At the same per-event price, the seasonal price that breaks even is 80 percent higher.
- At a 3-inch trigger, the count falls to 8.7 days, about 63 percent of the 2-inch count.
Deep storms set the tiers. A day of 5 inches or more comes 4.2 times in a normal Duluth winter, and a day of 10 inches or more 0.7 times. A per-event contract tiered at 5 and 10 inches prices those days separately; a seasonal contract has to carry them inside the fixed price.
Per-push pricing has a ceiling the normals also set. If every 2 inches of Duluth's 90.2-inch normal were pushed as it fell, a lot would see about 45 pushes. Snow that falls in amounts under the trigger and settles or melts is never pushed, so the actual count sits below that ceiling, and a per-push customer can use it as the upper bound of a winter's bill.
Salt quantity per application from an extension rate
University of Minnesota Extension states that "A coffee mug of salt (about 12 oz.) is all that is needed for about 1,000 sq. ft." of pavement (University of Minnesota Extension, the effects of deicing salts on landscapes, reviewed 2024). The rate is written for walks and drives cleared of snow first. Commercial applicators adjust their own rates by pavement temperature and product, and the estimate states whichever rate it assumes.
Applied to an acre of pavement, which is 43,560 square feet, the Extension rate gives:
- 43,560 ÷ 1,000 × 12 ounces = 522.7 ounces per application.
- 522.7 ÷ 16 = 32.7 pounds per application.
- Salted once on each of Duluth's 62.4 days with measurable snowfall: 62.4 × 32.7 = about 2,040 pounds, or about 1 ton, per acre per season.
Freezing rain and refreeze days add applications that a snowfall count does not show. The season's salt line on the estimate is the per-application quantity times the expected applications times the contractor's own price per pound, and the salt actually spread is checked against it once the winter is under way.
Site measurements on the estimate
The site walk produces the quantities the price depends on: paved area in square feet, sidewalk length in linear feet, the areas where snow can be stacked, and the curbs, islands, drains and fire lanes that limit the plow. The estimator photographs each obstacle before the season on a site survey job in FieldRanger; the photos attach to that work order and sync to the customer's HubSpot record, so damage claimed in March can be compared with the condition recorded in November.
The estimate is built on the HubSpot deal, without leaving HubSpot, or in FieldRanger and kept tied to that deal. It carries the trigger depth, the measured areas, the salt rate assumed and the price under the contract type offered. A worked estimate with every line filled for one site is on the snow removal estimate template.
From signed estimate to per-push invoice
- The customer accepts the estimate, and the HubSpot deal is marked won. FieldRanger creates the job from the deal with its context carried over, and job status shows on the deal record for the rest of the season.
- When a storm reaches the trigger, each site visit is created as a job and assigned to a technician on the drag-and-drop calendar. Each day is its own job in FieldRanger, so a storm that runs overnight into a second day produces a job for each day.
- FieldRanger builds each technician's route for the day automatically. The technician's clock-in and clock-out record the location, so hours on site match the site.
- Salt is checked out of the warehouse it is stored in and logged against the job with materials tracking, so each push carries the pounds actually spread.
- Before and after photos attach to the work order, and the completion is logged to the customer's HubSpot timeline.
- For per-push and per-event contracts, the invoice is generated from the completed work order. Invoices and payments sync with QuickBooks.
A seasonal contract's installments can be charged automatically to the customer's card on file with autopay. Storm timing, trigger depth on the dispatch board and sidewalk deadlines are covered on snow removal scheduling software.
Estimate inputs that stay outside FieldRanger
FieldRanger has no weather feed and no snowfall data: the normals above are read from NCEI and entered by the estimator, and the trigger on a storm night is observed, not fed in. The arithmetic that multiplies area by a salt rate or converts normals into a seasonal price is done before the estimate is written. What FieldRanger adds is the comparison afterwards. Revenue reports show job revenue and margin by customer, and the salt logged on each push shows whether the season's salt line held.
Frequently asked questions
What is snow removal estimating software?
Software that prices plowing and salting contracts from site measurements and expected snowfall, and carries the accepted price into the season's jobs and invoices. FieldRanger builds the estimate on the HubSpot deal or in FieldRanger and turns the won deal into jobs.
How is a seasonal snow removal contract priced?
As a per-event price multiplied by the number of events expected in a normal winter. NCEI's 1991-2020 normals give that number by trigger depth: Duluth averages 13.8 days with at least 2 inches of snowfall and 24.8 with at least 1 inch.
What is the difference between per-push and per-event snow removal pricing?
Per-push pricing bills each plowing pass at or above the trigger depth, so a long storm with several passes bills several times. Per-event pricing bills each storm once, tiered by total depth.
How much salt is needed per 1,000 square feet?
University of Minnesota Extension states that about 12 ounces, a coffee mug, covers about 1,000 square feet of cleared pavement. Commercial rates vary with pavement temperature and product, so the estimate states the rate it assumes.
Does FieldRanger use weather data to estimate snow removal?
No. FieldRanger has no weather feed; snowfall normals come from NCEI and are entered by the estimator.
In a normal Duluth winter, a lot on a 2-inch trigger sees 13.8 days of work and about a ton of salt per acre at the Extension rate, and the FieldRanger record of each push shows by March how far the season ran from that estimate. The trade's full workflow is under snow removal business software, storm-night dispatch under snow removal scheduling software, and per-technician plans on pricing, with Start free trial running 14 days and no card.
FieldRanger runs field service inside HubSpot
Estimates, scheduling and dispatch, a technician app and invoicing on the HubSpot records sales already keeps. Every plan starts with a free trial.
Book a demo