Landscaping is the most route-density-sensitive business in field service. A mow crew can hit fifteen lawns in a tight zip cluster on a Tuesday or eight scattered properties in the same hours — same labor cost, half the revenue. The operator who wins is the one whose Tuesday route is a tight cluster and whose seasonal contracts are billed monthly so cash flow doesn't collapse in winter. PrimeX is built for that math.
Recurring weekly routes auto-assemble. Service plans expand into mow + edge + blow visits on cadence — weekly, every-other-week, every-three-weeks per the customer's plan. Prime sequences each route by zip cluster + drive time + crew capacity the night before. Monday morning the crew gets a route that doesn't backtrack, saves an average 35-45 minutes vs free-form, and lets the same headcount mow more lawns per day.
Seasonal pricing is first-class. The Memorial-Day-to-Labor-Day premium gets configured once at the plan level; Prime applies it to every mow visit in the window automatically. Snow-removal contracts use the inverse — December-to-March activation, weather-triggered dispatch when accumulation crosses the customer's threshold (3 inches, 4 inches, plowing-only vs salt-too). Off-season landscaping margin doesn't disappear; it just shifts categories.
Irrigation startup + blowout are templated. Spring startup: turn on the system, walk the zones, log any broken heads + replaced parts to the customer profile, bill the templated startup fee. Fall blowout: connect the compressor, blow each zone in sequence, log the closing pressure. The same crew member can run startup + blowout on hundreds of accounts because the workflow is on rails — no "what was the deal with the broken zone-3 head at 412 Maple?" guessing in October. Customer profiles hold the answer.