How Do Snow Removal Contractors Send Estimates? Sold in September
Short answer: How do snow removal contractors send estimates? On bare ground, in September, as a contract proposal rather than a price. The document names a trigger depth, a push interval, a service window, a marked site map, and snow storage locations, and it prices deicing on its own line. Three models go on one page so the customer chooses who carries the weather risk: per-event, seasonal fixed, or hourly. Signatures and certificates of insurance close before the first measurable event.
Every other trade quotes work it can see. Snow contractors quote work that does not exist yet, for a season nobody can forecast, on a site that currently looks like a parking lot. A proposal here is not a price sheet, it is a risk allocation with a number attached, and the number is the least important part of it. The collection consequences of getting that wrong are in snow removal customer won’t pay.
When does snow actually get sold?
In a window that closes long before winter starts, which is the first thing operators new to commercial work get wrong.
| Month | What happens |
|---|---|
| April to May | Multi-year renewals and post-season reviews with existing accounts |
| July to August | Commercial and municipal RFPs and bid packages go out |
| September | Site walks, proposals delivered, insurance certificates exchanged |
| October | Signatures, subcontractor commitments, equipment and salt secured |
| November onward | Route is full; anything new degrades service for accounts already signed |
A proposal sent in January sells into a different market entirely — property managers whose contractor did not show up. That work exists and it is worth chasing, but it is priced per event, never seasonally, and it should not be your plan.
Why does the site walk have to happen on bare ground?
Because in December you cannot see what you are about to plow into, and by then the estimate is already wrong.
Walk the site in daylight, on dry pavement, with a wheel or a measuring app, and record:
- Pavement area, separated into drive lanes, parking bays, loading areas, and anything a truck cannot reach.
- Walks, steps, and entries, measured separately — they are hand and blower labor, not plow labor, and they are the biggest single reason a lot estimate goes wrong.
- Obstacles, marked and photographed: curbs, islands, wheel stops, bollards, hydrants, catch basins, sprinkler heads, light poles, speed bumps, gas meters.
- Pre-existing damage to curbs, pavement, sod edges, and signage, photographed with a date. That set of photos is what ends the spring claim about damage you did not cause.
- Snow storage, identified and staked. If the site has nowhere to put a heavy year’s accumulation, hauling is a line item on the proposal, not a surprise in February.
- Slope and drainage, because the low spot that refreezes every night is where the slip-and-fall claim comes from.
- Occupancy hours, since a 24-hour facility, a 7 a.m. retail opening, and a Monday-to-Friday office each imply a different service window.
Then stake the site before the ground freezes. Markers set in November on frozen ground are a bad night’s work; markers set in October take an hour.
Which of the three models am I quoting, and who is buying the weather?
Put all three on the page. The customer choosing knowingly is worth more than the customer accepting a number they did not understand.
| Model | Who carries the weather risk | Where it fits |
|---|---|---|
| Per event or per push | The customer | A new site, a market you have not run before, an unpredictable snow belt |
| Seasonal fixed | You | Established accounts, enough sites to average across, and real local event history |
| Hourly, time and materials | The customer | Hauling, ice events, storms outside the contract’s definitions |
A seasonal contract is an insurance policy you are writing without an actuary. In a light year it is the best money in the business, and in a heavy year it pays for the customer’s winter out of your pocket. That asymmetry is why the honest middle ground exists and sells well: a seasonal price with a collar, where the fixed number covers a stated band of events, per-event billing resumes above the cap, and a credit applies below the floor.
What has to be defined in the proposal before a flake falls?
The specifications are the product. A proposal that names a price and skips these is an argument scheduled for 3 a.m. in January.
| Term | What it has to state |
|---|---|
| Trigger depth | The accumulation at which you deploy without being called |
| Push interval | On a continuous storm, whether you return every stated depth or every stated number of hours |
| Event definition | How a 36-hour storm counts — one event or several |
| Service window | Hours to complete after snowfall ends, or an open-by time for a retail site |
| Scope map | The marked site plan, attached, showing what is and is not serviced |
| Snow storage | Named piling areas, plus the trigger that converts stacking into hauling |
| Deicing policy | Automatic on every visit, on-call, or by pavement condition — and who decides |
| Clearance standard | Standard service versus a continuous zero-tolerance site |
| Exclusions | Freezing rain, drifting after service, areas blocked by parked vehicles, roof and gutter ice |
| Insurance and indemnity | Certificate, additional insured endorsement, hold-harmless language |
| Documentation | A time-stamped service log for every visit, naming product and quantity |
The last row is the one that pays for itself. Slip-and-fall claims arrive months after the storm, and the service log is the entire defense. Promise it in the proposal and then actually produce it.
Why does deicing never go inside the seasonal number?
Because you cannot forecast consumption, and one ice event can burn more product than a month of plowing. Freeze-thaw cycles, pavement temperature, rain that arrives before a hard freeze, and a site with a shaded north face all move salt usage independently of how many inches fell.
Price it on its own line, every time, using a coverage rate you measured on your own spreader rather than one off a bag. Per ton applied or per application, with the site’s application rate stated. When a customer insists on an all-in seasonal number, cap it: a stated number of applications or tons included, then per-unit beyond. Add a supplier escalation clause, because bulk salt is the input most likely to spike mid-season in exactly the year you can least afford it.
How does the proposal go out, and how long does it hold?
As an emailed PDF with the marked site map attached and your certificate of insurance behind it. Commercial and municipal buyers get the RFP’s own format, filled out exactly as asked, because bid packages get disqualified on formatting more often than on price.
| Buyer | Format | Validity |
|---|---|---|
| Small commercial, single lot | PDF with map, one page of specs | Until October 31 or the first measurable event |
| Property management portfolio | PDF per site plus a rate sheet | 30 days, repriced if salt moves |
| HOA or condo board | PDF plus a version written for a board meeting | Through their next scheduled meeting |
| Municipal or institutional bid | Their forms, their sequence | The bid date on the package |
| Mid-season pickup | Short form, per event only | 48 hours |
Write the expiry as a calendar date and give the true reason with it. Route capacity in a storm is finite: every site added after your route fills lengthens the service window for every account already signed. That is not a sales line, and customers who run buildings understand it immediately.
When do I follow up, and where is the second selling window?
On a September calendar, then once more after the first storm. Send the proposal, check in about two weeks later, and around October 1 tell them honestly how much route capacity is left. Mid-October is the last call; after that, the answer to a new seasonal request is a per-event price or nothing.
The second window opens 24 to 72 hours after the first significant event, when the sites whose contractor did not show up start calling. Have a short-form, per-event proposal ready to send from your phone that week. Mid-season signings are per event only — a seasonal fixed contract taken on in January prices the unknown half of a winter with no light-season upside left in it.
How do I build a seasonal price that survives a heavy year?
From your own time on your own equipment, then against a bad winter rather than an average one.
- Cost one push on the actual site. Time a full service with the equipment you will send — plow, skid steer, blower, hand crew — and load the hour with wages, payroll burden, fuel, cutting edges, insurance, equipment payments, and subcontractor rates.
- Count events, not inches. What matters is how many times per season accumulation crosses your trigger depth. Station-level snowfall statistics in NOAA’s 1991–2020 U.S. Climate Normals let you count qualifying days for the station nearest the site instead of guessing.
- Build three seasons: light, normal, heavy. Take the heavy case from the worst winter in your record window, not from the average. The average year is the one that never happens.
- Add standby cost. Twenty-four-hour readiness, on-call wages, equipment insured and fueled and sitting still, subcontractor retainers, and the phone that has to be answered at 2 a.m. That cost exists in a zero-snow season and belongs in the seasonal number.
- Price the seasonal number against the heavy case, then check what it implies per push and whether the site will accept it. When it will not, sell per event or sell the collar instead of quietly betting on a mild winter.
- Add profit as a margin, not a markup. A 20 percent markup on $1,000 of cost bills $1,200 and keeps $200 — a 17 percent margin. To actually keep 20 percent you divide by 0.80 and bill $1,250. Across a portfolio of seasonal contracts, that gap is the difference between a good winter and a flat one.
Published per-acre and per-push ranges are a sanity check only. They swing enormously with snow belt, lot layout, hand work, salt policy, and equipment mix. The figure that decides whether a contract was worth signing is your own cost per push against your own event count, and the equipment and standby costs behind it are the deductions covered in self-employed tax deductions.
How does the yes get recorded before the season starts?
Signed contract, certificate of insurance with the additional insured endorsement, initialed site map, W-9, and a purchase order where the property manager requires one. Then a storm contact tree: names, mobile numbers, and the channel you will actually use at 4 a.m.
No plowing without a signed contract. Snow work carries slip-and-fall exposure that arrives long after the invoice, and running a site without an indemnity in place is not worth the revenue on it. The billing follow-through afterward is the ordinary subject of how to get clients to pay; the signature and the certificate are what make that conversation possible at all.
What has to be logged once the season begins?
Every visit, time-stamped: arrival, departure, conditions, depth on arrival, product applied and quantity, and before-and-after photos. Salt tickets and fuel receipts from storm nights are the documents most likely to be lost, and they are the ones that support both a per-ton invoice and a deduction. The habit that fixes that is described in contractor receipt organizer.
Keel handles the after-the-signature side from the phone, entirely on the device: no account, no bank connection, no cloud, no login, and an App Store privacy label reading Data Not Collected. Per-event invoices go out the morning after the storm in about a minute each, with your own numbering, logo, and brand color, and a payment link rendered as a QR code — which matters in a trade where one week can generate more invoices than the previous two months. Salt tickets and fuel stops get photographed at the counter and read on-device by Apple Intelligence, so a per-ton line has a scale ticket behind it. Freeboard shows cash minus a tax reserve, minus committed invoices, minus a buffer, which in a business earning its whole year in four months is the only honest read on what you can spend in June. Year end exports as one file, or as the Accountant Pack: a CSV plus a one-page summary PDF, on an append-only hash-chained ledger. Free is $0 with unlimited invoices, receipts, and mileage; Keel Pro is a one-time $249.99 Lifetime purchase, not a subscription.
Frequently asked questions
When should snow removal proposals go out?
Site walks in September and signatures by the end of October, with commercial and municipal bid packages usually landing in July or August. Winter sells before winter arrives. Anything you sign after the first measurable event is a per-event agreement, because a seasonal price set in January covers an unknown remaining winter with none of the light-season upside left in it.
Should I quote per event or by the season?
Put both on the page and let the customer choose who carries the weather. Per event moves the risk to them and suits a new site or an unfamiliar snow belt. Seasonal fixed moves it to you and only works with real local event history and enough accounts to average across. A collared seasonal price — capped above, credited below — splits the risk and sells more easily than either extreme.
What has to be in a snow removal proposal besides the price?
Trigger depth, push interval, how a long storm counts as events, the service window, a marked site map, named snow storage areas with a hauling trigger, the deicing policy, exclusions, insurance and indemnity terms, and a promise of a time-stamped service log. Those specifications are the product. A number without them is an argument scheduled for the middle of a January night.
Should salt be included in a seasonal price?
Not without a cap. Deicing consumption depends on freeze-thaw cycles, pavement temperature, and rain-before-freeze events, and a single ice storm can use more product than a month of plowing. Price it per ton applied or per application on its own line. If a customer demands an all-in number, include a stated tonnage or application count and bill per unit beyond it.
How long should a snow removal estimate stay valid?
Until October 31 or the first measurable event, whichever comes first, written as a calendar date. Give the real reason: route capacity in a storm is finite, and every site added after the route fills stretches the service window for everyone already under contract. Portfolio rate sheets can run longer if they allow repricing when bulk salt moves.
How do I estimate how many times it will snow?
Count events that cross your trigger depth rather than total inches. Station-level snowfall statistics in NOAA’s 1991–2020 climate normals give you qualifying-day counts for the weather station nearest the site. Then build light, normal, and heavy seasons, and price a seasonal contract against the heavy case taken from the worst winter in your record, not against the average.
This article is general information, not professional or tax advice.
How do I bill for it?
Once they say yes
Turn the agreed number into an invoice.
Describe the work in a sentence — "invoice Acme $1,500 for a brand sprint" — and Apple Intelligence drafts it on device for you to confirm.
On-device · No account · Data Not Collected