Diego has been running his crew for sixteen years. Three trucks went out at 6:45 every morning — Tony's crew, Ramón's crew, Carlos's crew — to a route map Diego sketched on a whiteboard the night before. By 8am the trucks were spread across the South Bay in five different cities. By 10am Diego's phone would start ringing with property managers asking "is your crew on site yet?"
The honest answer was usually: I think so. Let me text Tony. Which is exactly the answer that loses commercial landscape accounts.
The day before OpsLight
Diego's morning used to look like this: he'd review yesterday's progress on his whiteboard, sketch today's route map in marker, photograph it with his phone, and text the photo to his three crew leads. The crew leads would tell their guys verbally which property was first, second, third. Diego would then field calls all morning from property managers wanting status updates.
The problems compounded. When a property manager called at 9:14 asking "did your guys hit the Cupertino property yet?", Diego had to text Ramón to find out. Ramón, who was on a backhoe, would reply twenty minutes later. By that point Diego had either guessed and gotten lucky or, worse, said "I'll get back to you" and forgotten.
When it rained — which happens at the worst possible times in the Bay — Diego had to call eight property managers and reschedule three trucks worth of work, mostly from his car between his own appointments. The Tuesday-pushes-to-Wednesday chain was a four-hour task that always ended at 11pm.
And the monthly visit logs his commercial PM customers demanded? Diego paid his bookkeeper to assemble those from his crew leads' weekly text recaps. The bookkeeper's fee for that alone was about $400/month. The reports were always behind by a week and never matched what the property managers thought had happened.
He'd tried two scheduling platforms designed for landscapers — LawnPro Software and Service Autopilot. Both required his crew to use an app. Both failed within six weeks. The trade-forum pattern is brutally consistent: "I bought the software for the office's benefit, not the techs', and now I have a $400/mo expense and no data."
"My guys speak Spanish. They text in Spanish. They don't download apps. They don't log in. They show up on time and work hard. Any system that makes them learn something new is a system that doesn't work."
Diego Vargas · Vargas LandscapeHow Diego found OpsLight
A property manager who owned eight buildings across San Jose had implemented OpsLight with her painter and noticed it in their monthly reports. She told Diego about it and gave him the contact during a route review.
Setup focused on multi-crew route work:
- The 28-property recurring route schedule. Each property's frequency (weekly, biweekly, monthly), scope, square footage, and crew assignment.
- The bilingual crew roster. Tony, Ramón, Carlos as crew leads plus their guys. The system accepts
IN/OUTin English and Spanish equivalents. - The daily route Game Plan. Each morning at 5:30am, OpsLight assembles the day's routes for all three trucks based on the rolling schedule, weather forecast, and prior week's progress. Crew leads receive it by SMS.
- The monthly visit log template. Per-property, per-month visit count, scope performed, observations, recommendations.
Live in three weeks. The first week, Diego didn't sketch a whiteboard. By month two, his property managers stopped asking "is your crew on site yet."
Three moments from a regular Tuesday
The Game Plan that wrote itself overnight
Before Diego was awake, OpsLight assembled the day's routes for Tony's, Ramón's, and Carlos's trucks based on the weekly schedule and the previous week's progress (one Friday property had been pushed by rain — it landed at the top of today's list). The Game Plan SMS landed on each crew lead's phone at 5:30am. They were ready before Diego texted them.
The "is your crew there yet" question that didn't get asked
A property manager who used to call Diego every morning at 9:14 didn't call. Diego found out why on Wednesday: he'd checked his phone, seen the auto-text from OpsLight that arrived at 7:42 ("Tony's crew arrived on site at Cupertino Office, est completion 11:30"), and didn't need to call. The auto-text is configurable per-account — some PMs want it, some don't.
The rain reschedule that didn't ruin Tuesday night
The forecast updated Tuesday evening: Wednesday morning was now 90% rain. Diego pinged OpsLight to push Wednesday's morning route to Thursday. OpsLight regenerated Wednesday's Game Plan (afternoon-only work, indoor maintenance at one property, equipment prep for the rest), texted the four affected customers with their new arrival window, and updated the monthly visit log expectations. Diego ate dinner with his family.
Six months later
Diego didn't grow the headcount. He didn't add a truck. His monthly bookkeeping cost dropped by $400/month — the reports now generate themselves, his bookkeeper just reviews them. His commercial PM customers' Net Promoter Score (he runs an informal annual survey) went from a 6 average to a 9.
The biggest change: when he hired his fourth crew lead in the spring — a guy named Marco who came over from a competitor — he onboarded him in three hours. The whole "where is everyone" system was now visible in a Sheet Marco could read. He didn't need to be in Diego's head.
What's configured specifically for landscaping
- Landscape-vocabulary intake classifier. Knows mowing / edging / blowing / hedge / pruning / mulch / annuals / sod / irrigation / leaf-cleanup / aeration / overseeding / dormant pruning.
- Multi-crew route engine. Three (or four, or ten) trucks dispatched in parallel. Daily Game Plan per-truck.
- Weather-aware rescheduling. Rain → push and notify. OpsLight checks the forecast at 4pm daily and surfaces conflicts.
- Bilingual crew SMS. IN/OUT in English; ENTRO/SALI in Spanish. Customizable per crew.
- Monthly visit log template per PM account. Per-property visit counts, scope, observations.
- Seasonal-service triggers. Spring startup, fall cleanup, winter dormant pruning, irrigation winterize — auto-surface in the schedule when their season approaches.
- One-off install workflow. When a recurring customer wants a hardscape or planting install, OpsLight tracks it as a project on top of the maintenance schedule.
What landscape contractors ask us
Does it handle bilingual crews?
Yes. The IN/OUT keywords and the auto-replies can be configured in English or Spanish per crew. Some crew leads use both interchangeably depending on the customer.
Can we use it for residential maintenance routes too?
Yes. The route engine doesn't care if the stops are commercial properties or residential addresses. Residential intake skews toward web forms and direct customer texts rather than PM emails — the classifier handles both.
What about pesticide / fertilizer application records?
Captured as fields on each visit. Some states require detailed application logs for pesticide use — OpsLight stores the product, EPA number, rate, area, and applicator. Not a replacement for state-mandated record-keeping software, but enough that the state reports become easy to assemble.
Can OpsLight track equipment maintenance schedules?
Partially. We can track when a mower had its last service and remind you, but we're not an equipment-management platform. Most landscapers find a simple Sheet tab is enough.
What about routing optimization — drive time between stops?
OpsLight doesn't compute optimal routes by drive-time the way a logistics platform would. We sequence stops based on geography (you tell us the cluster groupings during install) but we don't do live route optimization. Most landscapers tell us they don't want it anyway — their routes are too constrained by access windows and crew familiarity.