Built for the dead zone, not the demo
Most field software assumes a signal. Crews work behind tree lines, in basements and out past the last tower. Every action in CutRoute is written locally first and synced when the phone finds a bar, so the day never stops because the network did.
Join the waitlist
The day loads before it starts
Schedule, property details, chemical plans, pricebook and map tiles download each morning.
Nothing is lost in a dead zone
Every write is timestamped, UUID-keyed and queued. Replaying it twice cannot double-post.
Conflicts resolve by rule
Each record type has an explicit resolution rule, so a merge never silently picks the wrong version.
What's in it
3 modules
Daily pre-load
All plans
The phone has everything it needs before the truck leaves the yard.
- Today's schedule, property details and gate codes
- Chemical plans and the full flat-rate pricebook
- Mapbox tiles for the day's route area plus a 20% buffer
- Everything readable with the device in airplane mode
Mutation queue
All plans
Every crew action is a durable, replayable record.
- Clock-ins, job updates and chemical logs are timestamped and UUID-keyed
- Mutations are idempotent, so a retry cannot create a duplicate
- The queue persists across app restarts and phone reboots
- Retry uses exponential backoff rather than hammering a weak connection
Conflict resolution
All plans
Explicit rules per record type instead of last-write-wins guesswork.
- Job status: the server wins if the job is already closed
- Chemical logs: append-only, so they can never conflict
- Time entries: the device timestamp wins, because the device was there
- Schedule edits: merge and alert the crew to the change
- Anything unresolvable escalates to the owner dashboard rather than being dropped
The rest of the platform
Waitlist
Get works offline first
Early access this winter, founding pricing at launch.
Questions
What actually happens with no signal all day?
The crew works normally. Every clock-in, job update and chemical log is written to the device and queued. When the phone reconnects, the queue uploads in batch and any changes made elsewhere merge back down.
Can a sync lose or duplicate an entry?
Each mutation carries a UUID and is idempotent, so replaying the queue cannot double-post. Anything the rules cannot resolve is escalated to the owner dashboard instead of being silently discarded.
Does navigation work offline too?
Yes. Map tiles for the day's route area, plus a 20% buffer, are cached each morning, so turn-by-turn keeps working past the last tower.