A whole season decided on twelve nights
Snow and ice management has the most extreme demand curve in the trades. A plumbing company's week looks roughly like last week. A snow company's entire year is compressed into a handful of unpredictable nights, and in between there are weeks where the phone barely rings and the equipment sits.
As of September 2026, the operators who come out of a winter profitable are rarely the ones with the newest equipment. They are the ones whose intake, documentation, and dispatch kept working at 3 AM in a storm, when the office is empty, every crew is moving, and the phone is ringing faster than any human can pick it up. This guide covers the operational stack for snow and ice: contract structures and what each one does to your cash and your risk, the pre-season signup window, the storm-night surge, service documentation as a discipline, route and crew dispatch in priority order, and the summer problem of keeping the business alive between seasons. It runs on the Run with Jarvis platform.
Contract structure is the single biggest decision you make
Before any software matters, the shape of your contracts determines whether a hard winter makes you or breaks you. There are four common structures and they are not interchangeable.
Per-push bills a fixed amount each time you service a site, sometimes with a trigger depth. Revenue tracks snowfall exactly. In a heavy season you earn well, and in a quiet season you earn almost nothing while your fixed costs continue. The customer carries the weather risk, which is why customers often prefer the other structures.
Per-inch tiers bill by accumulation band, for example one rate for two to four inches, a higher rate for four to eight, and so on. It is fairer to both sides than a flat per-push in a market with variable storm sizes, and it prices a twelve-inch event closer to the actual work. It also creates the largest measurement and dispute surface of any structure, because you and the customer must agree on how much fell and where it was measured.
Seasonal flat charges a fixed total for the whole season, usually split into monthly installments across the contract period. Cash flow becomes predictable, invoicing becomes trivial, and you can plan staffing. You have also taken on all of the weather risk. A record season on a portfolio of seasonal contracts is a season of unpaid work.
On-call or time and materials is unscheduled service for customers with no contract at all. Ticket sizes can be good and margins are often the best in the business because the price is set under pressure, but the volume is entirely unpredictable and it competes for crew hours you have already promised to contracted sites. Most well-run operations treat on-call work as overflow rather than a plan.
The comparison below is the summary; the choice for any given operation depends on your market's snowfall variability, your fixed cost base, and how much of your portfolio is commercial.
| Contract type | Who carries the weather risk | Cash-flow shape | Operational load it creates |
|---|---|---|---|
| Per-push | The contractor's revenue rises and falls with events; the customer pays only for service delivered | Lumpy and event-driven, heavy in storm months and near zero in a mild winter, with invoicing bunched right after each event | High billing volume, one invoice per service per site, and constant proof-of-service questions from customers reviewing charges |
| Per-inch tier | Shared, but the measurement itself becomes contested territory | Similar lumpiness to per-push with higher upside on large events and a wider spread between a mild and a severe season | The heaviest documentation burden of all four, since every invoice depends on an agreed accumulation figure and a defensible measurement source |
| Seasonal flat | Almost entirely the contractor; the customer buys certainty | Smooth and predictable, billed in equal installments regardless of events, which funds the off-season and simplifies payroll planning | Low billing load but high service-expectation load, because customers who have already paid expect fast response on every event and feel entitled to extras |
| On-call, time and materials | The customer, who pays a premium for unscheduled response | Entirely unpredictable, concentrated in the largest events when everyone calls at once | Highest intake load per dollar, because most calls arrive during the exact hours when crews and phones are already saturated |
The practical answer for most operations is a deliberate blend: a seasonal base that covers fixed costs through the winter, per-push or tiered commercial work on top of it, and a capped amount of on-call capacity taken only when the routes allow. The important part is that the blend is chosen, priced, and tracked rather than accumulated by accident.
Whichever mix you land on, recurring structure beats one-off transactions for the same reasons it does in every other trade. The general case for building contracted revenue rather than chasing individual jobs is in service agreements and membership plans, and snow is the trade where the argument is strongest, because the alternative is betting a year on the weather.
The pre-season window is a phone problem
Here is where most snow companies quietly lose the season before a single flake falls.
The signup window is short and it is almost entirely front-loaded. Commercial property managers want their vendor settled well before winter. Homeowners think about it later, usually at the first real forecast, at which point they call whoever answers. If your renewals are not closed and your new signups are not converted by then, you spend the season taking marginal on-call work at whatever hours are left.
The instinct is to treat this as a marketing problem and buy advertising. It is not. Most of the addressable list is already yours: last season's customers, the ones who cancelled mid-season and might come back, the sites you quoted and lost, the commercial contacts whose current vendor disappointed them last winter. That is an outbound calling and follow-up problem against a list you already own.
The platform's AI outbound follow-up calls are built for exactly that kind of work on your own leads and customers: renewal reminders to last year's contract holders, second touches on quotes that went quiet in August, reactivation calls to sites you have not served since two winters ago. It is follow-up on your own database, not cold prospecting. See pricing for how those capabilities sit across the tiers.
Combine that with inbound intake that never misses a pre-season call. September and October calls are worth more per call than any others in your year, because each one is a whole season of revenue rather than one visit. A missed call in October is not a missed job, it is a missed contract.
The intake itself should collect what actually determines whether you can price the site: address and lot or driveway dimensions, surface type, obstacles and islands, where snow can be stacked and where it absolutely cannot, whether there are sidewalks and entryways in scope, whether salt or another de-icer is expected and who pays for material, trigger depth expectations, required service window and whether the site must be clear before a specific hour, gate or access arrangements, and who authorises extra work at 2 AM. Photos of the property in bare conditions are worth more than any verbal description, and September is the only time of year you can get them.
The storm night, when the phone becomes unusable
Then the storm arrives and everything changes shape.
During a significant event the call volume can arrive at many times the normal rate, and it arrives concentrated in a handful of hours. The callers are your contracted customers asking when their crew is coming, on-call prospects who have no contract and want service tonight, property managers reporting a missed area or a blocked entrance, a driver reporting a broken plow, and a homeowner who watched a truck go past their street.
Every one of your people is already deployed. The person who answers the phone in normal times is either plowing or asleep after plowing. There is nobody free. So the phone rings out.
The problem is that a storm-night voicemail is functionally a lost call. Nobody snowed in at 4 AM waits for a callback. They dial the next number. And the contracted customer who could not reach anyone does not simply wait either, they escalate, they call three more times, and they remember it at renewal. A single unanswered surge does more reputational damage than a slow plow.
An AI receptionist answers all of them at once. Not a queue, not a hold, parallel handling of every simultaneous caller. It tells a contracted customer where they sit in the priority order and gives an honest window instead of silence. It captures an on-call request properly, with address, surface, and access, so it can be quoted and slotted rather than lost. It routes a genuine emergency, a blocked fire lane, an injured person, a downed line, a stuck vehicle, straight to whoever is on duty rather than into a message queue. And it does all of that in English or Spanish, which matters in most markets and matters more with a seasonal workforce.
The general playbook for a weather-driven call spike is in the storm and freeze call surge playbook, and the immediate automated text response that catches callers you could not reach is covered in missed-call text-back. For snow, the text-back layer is unusually valuable because a customer at 3 AM often prefers a text update to a phone conversation, and a text that says "your site is third on the route, expect a crew before 6 AM" prevents the next four calls from that person.
The wider pattern of a business whose call volume swings by an order of magnitude across the calendar is covered in seasonal call volume, and snow is the extreme version of it. Everything you build has to be sized for the storm night, not for the average Tuesday.
Documentation as an operational practice
Slip-and-fall claims and billing disputes do not arrive during the storm. They arrive months later, sometimes after the season has ended, when the site conditions are long gone and the crew that was there has moved on. What exists at that point is whatever you wrote down.
Treat documentation as an operational practice, not as legal protection. It supports accurate billing, resolves customer disputes about whether a site was serviced, tells you which routes are actually taking the time you priced, and gives your insurer and your attorney something factual to work with if they ever need it. What it does not do is decide any legal question, and nothing here should be read as legal advice. Your obligations, your insurance requirements, and what any record is worth in a dispute are matters for your own attorney and your carrier.
With that framing, the record you want per service visit is unremarkable and simply has to be captured every time:
The site and the specific areas serviced, including whether sidewalks and entryways were in scope. Arrival time and departure time from GPS rather than from memory. The conditions found on arrival, meaning approximate accumulation, whether it was still falling, whether the surface was ice or snow or slush. What was actually done, plow, shovel, blower, hand work at entrances. What material was applied, what type, and roughly how much. Which crew and which vehicle. And time-stamped photographs of the areas before and after service.
Almost all of that can be captured automatically rather than by a tired crew filling in a form at the end of a fourteen-hour shift. GPS tracking supplies the arrival and departure times and the route without anyone doing anything. The mobile app puts photo capture in the crew's hand at the site, where the time stamp and location are attached automatically. The CRM holds it all against the site record so it can be produced by address and date rather than reconstructed from a truck's glovebox.
The billing benefit is immediate and shows up long before any dispute does. A per-push customer who questions three charges is answered with three service records and photographs in under a minute instead of a two-day back-and-forth. A per-inch tier customer who disagrees with the accumulation gets your recorded conditions and photographs alongside your measurement source. That alone changes collection speed on commercial accounts.
The operational benefit is that you finally learn what your routes actually cost. Time on site by property, across a whole winter, is the only honest input into next season's pricing.
Routing and dispatch when the whole list is due at once
Snow dispatch is unlike any other trade's routing problem. In most trades, jobs are spread across the day and the constraint is travel time between them. In snow, every site on your list becomes due simultaneously the moment the storm passes the trigger, and the only question is order.
That order is not distance. It is a priority stack that has to be set before the season and enforced during it:
Contractual service windows come first. A site that must be clear before a 6 AM shift change or a 7 AM hospital opening is not negotiable and does not care where it sits on a map. Then the sites where a delay creates a safety exposure or an operational shutdown for the customer. Then the rest of the commercial portfolio, ordered by a route that minimises deadhead miles. Then residential contracts. Then on-call work, which should only be accepted when the contracted list is genuinely covered, because taking a lucrative on-call driveway ahead of a contracted commercial lot is how you lose the account that pays your fixed costs.
The system has to make that order visible to the crews and adaptable during the event. GPS tracking shows where every truck actually is rather than where dispatch believes it is. Route optimisation sequences within each priority band. Automatic ETA and arrival texts to customers cut a large share of the inbound "when are you coming" calls before they are dialled, which is the cheapest thing you can do to the storm-night surge. And when a truck breaks down at 2 AM, the sites on that route can be reassigned in the system rather than in a series of phone calls to drivers who are all currently plowing.
Multi-crew dispatch mechanics carry over from the rest of the field-service world, and the summer side of the same business usually runs on identical infrastructure. The route-density thinking in the landscaping and lawn care stack is directly applicable, because in most snow operations the summer routes and the winter routes are the same customers and the same trucks.
Booking and calendar sit on GetTimePad, the CRM, invoicing, and POS on IntelliDrive, and the phone answering on KeyBot. The point of having them connected is that a storm-night call, the service record it produces, the invoice it generates, and the renewal conversation next September are all attached to the same site.
Billing that matches the contract you sold
Snow billing goes wrong in predictable ways, and each contract type breaks differently.
Per-push and per-inch generate a lot of invoices, fast, right when everyone is exhausted. If invoices go out a week after the event, two things happen: the customer has forgotten the conditions and disputes the charge, and your cash arrives a week later than it should have during the only months you earn. Invoicing should fire from the completed service record, with the photos and times attached, and go out as a payment link the customer can tap. Three payment providers are supported, QuickBooks sync is bidirectional so the winter's transaction volume does not become a spring reconstruction project, and chargeback defence is included, which is relevant in a trade where a customer occasionally disputes a charge months after the fact.
Seasonal flat contracts have the opposite problem. Billing is easy and the risk moves to collections continuity: installments due in months when the customer has seen no snow and feels they are paying for nothing. That is a documentation and communication issue as much as an accounting one, and it is why sending service records after each event to seasonal customers, not just to per-push ones, materially reduces mid-season cancellation pressure.
On-call work should be collected on site or immediately after, without exception. A customer who was desperate at 3 AM is a different customer at noon the next day when the sun is out and their lot is clear.
The summer problem
A snow-only business has a structural flaw that has nothing to do with snow: for something like half the year it has no revenue, and it still has trucks, insurance, storage, a loan schedule, and the people it wants to keep for next winter.
There are three common answers and most successful operations use some combination.
Run a complementary summer trade on the same customer base and largely the same equipment. Landscaping, lawn maintenance, hardscape, parking lot sweeping, and property maintenance are the usual pairings, and the reason they work is that the commercial property manager who buys snow from you is buying grounds maintenance from someone, and would generally prefer one vendor.
Sell seasonal contracts with installments spanning more of the year, so the cash from winter work is spread across months when nothing is happening. This is a cash-flow smoothing decision, not extra revenue, and it needs to be priced deliberately rather than used to paper over a bad season.
Use the quiet months for the work that pays next winter: renewals, pre-season signups, site surveys and measurements while the ground is visible, pricing reviews built from last winter's real time-on-site data, and equipment preparation.
What ties all three together is that the customer list is the durable asset, not the service line. The value of keeping the phone answered, the CRM current, and the follow-up running year-round is that in September you are calling a maintained list rather than reconstructing one from memory and invoices.
Running the numbers on a snow operation
Treat these figures as an illustration to replace with your own.
Assume a snow operation holds 60 contracted sites, a mix of seasonal and per-push, generating $180,000 across a five-month winter. Assume that during the season the phone takes 900 calls a month, heavily concentrated into storm days, and that during a surge roughly 300 of those go unanswered because everyone is deployed.
Assume conservatively that only 6 of those missed calls a month would have become on-call jobs at an average of $280, which is $1,680 in recovered revenue, and that answering the contracted customers instead of missing them prevents a single mid-season cancellation on a $3,500 seasonal contract. Elite at $1,200 with 2,500 included minutes is the plan a business at this call volume would actually run, and even 900 calls at three minutes each is 2,700 minutes, so about 200 overage minutes at $0.35, roughly $70, for $1,270 in the month.
Now weigh the other side. The subscription is month-to-month with zero setup fees, which for a seasonal business is the part that matters most: you can size the plan to your winter and step down in the off-season rather than carry a peak-season commitment through July. That flexibility is worth more to a snow operation than to almost any other trade.
The minute arithmetic is worth doing carefully because snow is spiky. A quiet August might use 200 minutes; a January with two major events might use 3,000. Core includes 500 minutes at $0.45 overage, Pro 1,000 at $0.40, Elite 2,500 at $0.35. The right approach is to match the plan to the season you are in and let the month-to-month terms do their job. Full plan details are on the pricing page.
Rollout order
Start before the season, not during it. Attempting to configure a phone system in the middle of a January storm is not a plan.
First, answering and pre-season intake, running from late summer. That alone captures the renewal and signup window, which is the highest-leverage thing on this list.
Second, outbound follow-up against last season's customer list and your open quotes. Those are calls to people who already know you, and they close the portfolio before the weather forces the issue.
Third, dispatch, GPS, and automatic arrival texts, tested on a small early-season event rather than a blizzard. The arrival texts are what suppress the storm-night call volume, and you want them proven before you need them.
Fourth, service documentation and photo capture, which should be a habit before the first significant event because retrofitting it mid-season never happens.
Fifth, invoicing with payment links tied to the service record, so per-push billing goes out the same day.
Only then, if you are advertising for pre-season signups, look at attribution and campaign tooling. Knowing which ad produced a September call is useful once every September call is being answered.
For general small business material, the Small Business Administration publishes resources at sba.gov, and labour and industry data is available from the Bureau of Labor Statistics at bls.gov. Neither addresses your state and municipal requirements around snow and ice contracting, insurance, or de-icing material handling, which vary considerably and belong with your own advisers.
The short version
Snow is a business where the year is decided on a dozen nights and the phone stops working on every one of them.
Choose your contract mix deliberately rather than by accident, and know which side of each structure is carrying the weather. Close the season in September, using outbound follow-up against the list you already own, because a customer who is still shopping at the first forecast will take whoever answers. Answer every storm-night call in parallel, tell contracted customers where they sit in the order, and text arrival updates so people stop calling to ask. Document every visit with times, conditions, material, and photographs, as an operational habit that keeps billing clean and gives your insurer and attorney something factual if they ever need it. Run the route by priority, not by proximity. And keep the list and the phone alive through the summer, because the list is the business.
If you want that modelled against your real site count, contract mix, and storm-season call volume, get in touch or look at the plan details on the pricing page.
