Dispatch
Build the day, assign crews and equipment, and push routes to the field — with double-booking caught before it happens.
The platform
From the first estimate to the last invoice, every capability lives in the same system and shares the same data. Here is what runs underneath.
Element 06 · Growth model
A calendar says “every 7 days.” A lawn doesn’t. Iteratium predicts each property’s next visit from eight research-backed factors, so crews show up when there’s work to do — not before, not after.
Elements 08 & 10 · Planning & routing
Due jobs are grouped by geography so each crew works a tight service area, not the whole map.
Workload is spread across crews and days against real durations and availability.
Each route is ordered with TSP optimization on live Google Maps drive times, then dispatched.
CREW B · TUE · 9 STOPS · 31.4 MI
Elements 09, 12 & 19 · The field
Build the day, assign crews and equipment, and push routes to the field — with double-booking caught before it happens.
Crews move jobs from en-route to started to complete. The office sees the week as it happens, with an audit trail on every change.
Standing visits regenerate automatically, timed by the growth model and the business calendar — holidays and vacations included.
Elements 24 & 26 · Billing
The moment a job is marked complete, the invoice drafts against the billing period. Card payments and autopay sync back on their own, and customers get notified by SMS and email.
Elements 21, 44 & 47 · Portals
A health dashboard over revenue, customers, and operations — plus every management screen from dispatch to the growth-model settings.
Self-service properties, twelve months of history with photos, estimate requests, and a contact channel that routes straight to your team.
The day’s route, a one-tap status workflow, job notes, and photo capture — built for a phone in a work glove.
Under the hood