Get Paid for Every Push and Salt Run, Automatically, Before Spring

The 3 a.m. push that never made it onto an invoice

It is the third storm of February. Mike runs operations for a commercial snow and ice contractor outside Buffalo: 18 plow trucks, a fleet of salters, and ninety-odd commercial accounts on a mix of per-event and seasonal contracts. At 2 a.m. the DTN weather feed reads two inches and climbing. He is texting drivers, checking which lots have crossed their trigger, and waiting on route sheets his crews fill out on clipboards with cold hands. Salt gets logged on the back of the sheet, when there is time. By the time the lots are clear at 6 a.m., his crews have plowed forty properties and salted most of them.

Then the second job starts. His office manager spends the next three days keying route sheets into QuickBooks and matching them to events in Service Autopilot. Two sheets came back unreadable. One driver forgot to note the second salt run at the medical plaza. A subcontractor texted his hours instead of logging them. Every one of those is a push or a salt run the company actually did, paid a driver and fuel and material for, and will never bill. Across a full season of storms, the number that leaks out is not rounding error. It is a truck payment.

This is the quiet math of a paper-run snow operation. The work happens in the dark, per event, triggered by weather, and the billing depends on a clipboard surviving a blizzard and a memory surviving three days. By the time spring reconciliation rolls around, nobody can prove half of what was done. This guide stays narrow on purpose: getting paid for every push and every salt run, automatically, before the snow melts and takes the evidence with it.

Per-event billing that leaks from clipboard to invoice

The core leak is the handoff. A driver clears a lot at 3 a.m., scribbles a time, maybe notes the salt, and the sheet rides around in a wet truck until someone in the office translates it days later. Seasonal accounts hide the leak worse, because the push feels already paid for, so nobody logs the extra salt runs that are billable on top of the contract. By spring you are reconciling from memory.

General field-service tools were not built for this. Service Autopilot and Aspire treat snow as one more service line on top of a lawn-care spine. They can bill a job, but they do not natively tie a weather trigger to an auto-generated billable event, and they leave the salt run as a manual note a tired crew has to remember to enter. ServiceTitan and Jobber are even further from the per-event, weather-driven reality of a plow route.

A custom build closes the handoff. Crews log each push and each salt run on a phone the moment it happens, tagged with time, GPS location, and a photo of the cleared and salted lot. The system pulls the storm's accumulation from a weather feed like DTN or WeatherWorks and checks it against the trigger written into each contract. A two-inch storm on a two-inch account generates the plow line and the salt line automatically, priced by that account's rules, ready to invoice before the driver is home. The same time-stamped, geo-tagged photo record doubles as your slip-and-fall defense file, which is the document your insurer and your lawyer actually want when a claim lands in April.

The 9 p.m. storm call that went to voicemail

The forecast turns at dinner. A property manager whose regular contractor just flaked calls three snow companies at 9 p.m. looking for someone to cover a plaza tonight. Mike's office closed at 5. His cell is buried under driver texts. The call goes to voicemail, and by the time he hears it the plaza belongs to whoever picked up.

No off-the-shelf field-service CRM (Customer Relationship Management) answers a phone. Voicemail, an answering service that knows nothing about snow, or a missed call is the whole menu, and every one of them loses the account that was ready to sign tonight.

An AI phone agent picks up on the first ring, at 9 p.m. or 3 a.m., during the exact hours snow work gets bought. It knows your service area, your triggers, and your pricing bands. It answers the caller's questions, captures the address, the lot size, and the urgency, and either books the visit into the dispatch board or flags an active slip hazard for an immediate human callback. The recording, transcript, and new account land in your system automatically, so a call that used to die in voicemail is a booked job by morning.

The commercial bid that sat three days and lost the lot

A regional retail account asks for a full-season quote in October. Mike measures the lots, builds the number, sends it, and then the season starts and the estimate sits. He means to follow up. Three days become ten. The prospect signs with the contractor who called back the next morning. The quote was fine. The silence lost it.

Aspire and Service Autopilot will store that estimate and show it as open forever. Neither one chases it for you. Follow-up is a human task that competes with a live storm, and the storm always wins.

AI follow-up works the open estimates while your crews plow. The system watches for quotes that have gone quiet and sends a timed, written-in-your-voice nudge by text or email: a check-in, an answer to the usual objection, a reminder that routes fill before the first storm. It escalates the ones that reply to a human and keeps the cold ones warm. The estimate that used to sit three days now gets touched the same day, every day, without anyone remembering to do it.

The account you saved at 4 a.m. that never left a review

Reputation is how commercial snow gets sold, and the best proof is a property manager saying you showed up during the worst storm of the year. But at 4 a.m., nobody is thinking about a Google review, and by the time the office reopens the moment has passed. So the outfit that cleared forty lots overnight has the same online footprint as the one that no-showed.

Generic CRMs have a review feature buried three menus deep that nobody triggers during a storm week. It sits unused all winter.

A custom flow fires the ask at the right moment automatically. When an event closes clean at a property, the system waits a sensible beat and sends the site contact a one-tap review request, routed to Google or the profile that matters, personalized to that property and that storm. The same engine can request the seasonal renewal and surface referral moments. The work you already did quietly builds the reputation that wins next October's contracts.

Two salt trucks on one lot, and a lot with none

Dispatch on a storm night is a whiteboard and a memory. Two salters end up crossing at the same plaza while a strip mall on the other side of town waits an hour past its trigger. Drivers freelance the order of their stops. A sub runs a route nobody can see in real time. Fuel and salt and hours burn on overlap while an account that is about to call and complain gets missed.

Route features in general tools optimize a static daily schedule for lawn crews. They do not react to a storm that hit one zone harder, or re-sequence around a truck that broke down at 2 a.m., or hold a salt-only account until ice actually forms.

Smarter dispatch is built around the weather and the trigger. The system generates routes per event from live accumulation by zone, assigns trucks and subs to properties, and shows every vehicle on one live map. When one side of the county gets six inches and the other gets two, the board re-sequences so the hardest-hit, highest-priority accounts clear first. Salt-only stops release when ice conditions and the contract say so, not on a fixed loop. You stop paying for two trucks on one lot and start proving response times you can put in front of a client.

Ten seasons of accounts nobody has ever asked a question

Mike's Service Autopilot has eight years of accounts, sites, contracts, event logs, and salt usage in it. Nobody has ever run a real question against that data. It is a filing cabinet, not an asset.

That is the norm, and it is the most overlooked opportunity in the business. The CRM your competitors also own does nothing with its own history either.

Mining it changes how you price and who you keep. The system reads your event history and prices next season's contracts off the real number of pushes and salt runs each property took, not a guess. It flags seasonal accounts whose event counts drifted so far from their contract that you lost money, so you can re-price at renewal. It finds salt-only accounts that should be full-service, contracts trending toward non-renewal, and properties clustered tightly enough to justify a new route. The same years that sat dead in the CRM become the sharpest pricing and retention tool you have.

What this costs and how long it takes

These bands come from Digital Heroes delivery experience across more than 2,000 projects, not a menu. A focused first release, usually the mobile event logging and the weather-triggered auto-invoicing that stops the billing leak, typically runs 50,000 to 120,000 dollars and ships in 10 to 16 weeks. A full operations platform that ties billing, the AI phone agent, dispatch, documentation, and CRM mining into one system typically runs 150,000 to 350,000 dollars, phased across 6 to 12 months so you get the money-saving pieces first.

What drives price up in snow and ice specifically: live weather-feed integrations and the logic that maps accumulation to each contract's trigger, real-time GPS or AVL truck tracking, billing rules that juggle per-event, per-inch, seasonal, and time-and-materials on the same account, slip-and-fall-grade documentation with an audit trail your insurer will accept, subcontractor payment splits, and clean two-way sync with QuickBooks and whatever CRM you keep. The more of those you need at once, the closer you sit to the top of the band. Starting a build in spring or summer is the cheapest insurance that it is live before the first storm.

When Aspire is enough, and when it is time to build

Be honest about this. If you run a handful of trucks, bill mostly simple seasonal contracts, work one region, and your crews already get every event into Aspire or Service Autopilot cleanly, you do not need a custom platform. Those tools are good at what they do, and rebuilding them is a waste of your budget.

The signals that it is time to build or to layer AI on top are specific. You are exporting your CRM to spreadsheets every spring to reconcile a season by hand. You know you are losing pushes and salt runs to paper but cannot say how many. Your after-hours calls go to voicemail during the exact hours snow is bought. Your estimates sit for days. You have years of data nobody has ever queried, and you have the volume and the margin to protect that make a fix pay for itself in a season or two.

Here is the position: do not rip out ServiceTitan or Aspire on day one. Layer AI automation on top of the system you already run, the phone agent, the estimate follow-up, the review and renewal flow, the data mining, and get outcomes in weeks. Build custom only for the places the off-the-shelf tool structurally cannot go, which for snow is almost always the weather-triggered per-event billing and the documentation that stands up in a claim.

How to choose a developer for snow and ice management software

Most software shops have never watched a plow route reconcile in April, so vet for the specifics of this trade.

First, make sure they understand weather-triggered, per-event billing and treat slip-and-fall documentation as a legal artifact, not just another job photo. If they talk about jobs and customers but go blank on triggers, salt runs, and seasonal-versus-per-event billing, keep looking. Second, ask what they have integrated: DTN or WeatherWorks feeds, GPS or AVL, QuickBooks, and your actual CRM, Aspire or Service Autopilot, including migrating years of your history out of it. Third, confirm they ship during your off-season and can support the software live on a storm night, not only 9 to 5 on weekdays, because your system's hardest hours are 2 a.m. in January. Fourth, get code ownership in writing: you should own the build and your data outright, not rent your own operation back from a vendor. A developer who clears those four is worth far more than the one with the slickest demo.