Drive time as a share of paid hours
The most direct link between routing and maintenance margin.
Grounds maintenance makes or loses money on windshield time. A crew that spends ninety minutes a day driving between properties in Aurora and Arvada can give away the margin on its whole route. Add a rain day, a trailer with a flat, two laborers who do not show and an enhancement job that ran long, and the account manager spends the morning rebuilding the week by phone.
Better scheduling and dispatch means routes built around geography and crew capability, a fast way to re-sequence after disruptions, and crew leads who see their day, property notes and gate codes on a phone. Aspire, LMN, Jobber and Service Autopilot all have routing and scheduling features. Often the improvement is setting them up properly and tying them to timesheets, not buying something new.
Use addresses, visit frequency and crew size to group properties into tighter routes, then review the result with account managers who know which clients need a specific day.
Agree a standard rain-day rule, such as shifting the route by a day or splitting it across crews, so re-sequencing takes a few clicks rather than a morning of calls.
Each crew lead sees properties in order, notes, photos of problem areas and scheduled extras such as aeration or bed edging, in English and Spanish where needed.
Compare clock-in and clock-out times at each property against budgeted hours, and flag properties that run consistently over budget for review.
How we deliver this: AI automation for small business or fractional CTO leadership, scoped in writing and run over 90 days. See pricing or the sample scope.
The most direct link between routing and maintenance margin.
Identifies underpriced accounts before the renewal conversation.
Shows whether rain days still cost the account manager half a day.
Protects the client experience while routes change.
For example, a company runs two maintenance crews covering 70 residential and 12 commercial properties across the west metro. Mapping the routes shows one crew driving from Lakewood to Westminster and back twice a week. Swapping fifteen properties between the crews and moving four clients by a day removes the zig-zag. The account manager calls the four affected clients before the change, and the team tracks drive time for a month to confirm the result.
In the first 30 days we would map current routes, pull a season of planned versus actual hours, and measure drive time per crew. Then we would agree on one route rebuild or a standard rain-day process as the pilot, with account managers and at least one crew lead involved from the start.
Several field service tools can suggest optimized routes, and some do it well. The output still needs a person who knows that one HOA insists on Thursdays and another property cannot be mowed before 8 a.m. We would use automated routing as a starting draft, have account managers adjust it, then lock the result for the season.
Snow removal runs on triggers and events instead of fixed routes. Crews need site priority order, trigger depths, salt rules and a way to log arrival, departure and service with photos. Many companies run snow in the same field software, others in a separate tool. We would make sure event logs feed billing cleanly, which is where disputes usually start.
Keep it simple: one app, the fewest possible taps, and a clear reason it helps the crew lead, such as fewer calls to the office and no paper route sheets. Train in the shop before the season, in the language crews use, and have the account manager check usage weekly for the first month.
Illustrative defaults for a landscaping company. Replace them with your numbers.
a month in staff time, before any lost sales
Illustration only, not a forecast or guarantee. Recovered staff time becomes a cash saving only if spending actually declines or the time goes into paid work. Tool costs are an assumption; we replace every number here with yours before recommending a scope.
Job scheduling and dispatch: full guide
In 30 minutes we look at one recurring workflow, what it costs you today and whether there is a credible case to improve it. If there is not, we will say so.
30 minutes with Phil or Martin. No technical brief, no pitch deck. Phil or Martin replies personally, usually within one business day.