Take a look at tomorrow's jobs. If you're like most owners we work with, they're sitting in your calendar in the order the phone rang: an 8 o'clock in Quincy, a 9:30 in Newton, an 11 back down in Braintree, then a 1 o'clock that's somehow in Newton again. Nobody planned that. It just piled up, one call at a time.
You'll untangle it eventually, probably standing in the driveway at six with the coffee going cold and the truck already running. By then you're deciding on the fly, though, and the route you grab is the one you can hold in your head, not the one that actually saves the miles.
Here's the move: spend ten minutes on it the night before instead. You already know the jobs. What you're missing is a sane drive order, and that dull bit of sorting is exactly what an AI chatbot (the kind you type a question into, like ChatGPT or Claude) is genuinely good at.
The hour you're losing to zig-zagging
Booking in call order feels efficient because it's fast. Phone rings, you grab the next open slot, hang up, done. The cost stays hidden until the next morning, when it shows up as backtracking across towns you already drove through.
Figure it this way. Three towns, jobs booked out of order, and you cross the same stretch of Route 9 or 128 twice before lunch. That's easily an extra hour of driving and a good chunk of a tank, five days a week. Nobody ever billed a customer for windshield time.
The fix isn't some expensive routing system with a monthly fee. It's reordering the list before the day starts, so you drive one clean loop instead of a zig-zag.
What to hand it
Rough is fine here, which is the good news. Open a chat and paste in tomorrow's stops with whatever you've already got written down:
- The address, or just the town, for each stop. "Maple Street in Dedham" is plenty. It doesn't need the zip code.
- Any fixed times you can't move. A 9 AM the customer dug in on, a permit inspection scheduled for 2.
- A rough job length for each one. "Quick service call, maybe half an hour" or "this one's a full day."
- Where you start and finish. Your shop, your house, or the supply house you swing by first.
Then ask it plainly: "Put these in a sensible drive order starting from my house in Woburn, give me a start time for each, and tell me where the gaps are." That's the whole prompt, and a prompt is just the instruction you type in. No need to sound technical about it.
What good output looks like
A decent answer comes back with three things, and every one of them earns its place.
First, the drive order: your stops resequenced so you're working one direction across your territory instead of pinging back and forth. Second, a start time for each stop, built off your job lengths plus its best guess at drive time between them. Third, and this is the sleeper, the gaps: it flags the 90 minutes between the Natick job and the Framingham one where you could slot a filler call, or just eat a sandwich like a person.
Picture that pinball day from above, cleaned up. Instead of Quincy, Newton, Braintree, Newton, it hands you back Quincy at 8, Braintree at 9:15, then the two Newton stops bunched together after lunch. Same jobs, half the backtracking. You didn't do anything clever. You just let it sort.
That gap list is where the ten minutes pays off a second time. You can see, the night before, whether tomorrow has room for the customer who's been waiting on a slot, or whether you're already stacked and ought to stop saying yes.
Where it guesses, and where you take over
Be clear-eyed about this, because the tool isn't magic and it'll cheerfully hand you a confident wrong answer. Two things it flat-out does not know:
- Traffic. Unless it's wired to live map data, it's estimating drive times from rough distance alone. It has no clue the Tobin's backed up or the Pike is a parking lot at 4:30. Treat its drive times as a sketch, not gospel.
- How long your jobs actually run. It only knows what you told it. If you said 30 minutes and it turns into a 90-minute fight with a seized valve, the whole afternoon slides and it has no idea.
So you still eyeball the thing. Read the order, sanity-check the times against what you know about your own towns and your own pace, and nudge whatever's off. The AI does the boring sort in seconds, and your judgment handles the last five percent. That split is the whole point.
Worth one more honest word: for two or three stops, this is overkill, so skip it. It earns its keep at five, six, seven jobs spread across a few towns, which is right where the ordering gets hard to hold in your head.
Worth doing this week
Don't overhaul anything. Just try it one night and see whether the morning feels different.
- Tonight, paste tomorrow's stops into a chatbot with towns, fixed times, and rough job lengths. Ask for a drive order, start times, and the gaps.
- Eyeball the result for two minutes. Fix any drive time that's obviously wrong for a town you know cold.
- Screenshot it or jot the order down so it's on your phone in the driveway, no thinking required at six.
- At day's end, note where it was off. Ran long? Traffic snarl? That's the feedback that sharpens tomorrow's ask.
- Give it three nights running before you judge it. One good loop and you'll feel that hour come back.
If wording the prompt every night gets old, that's the kind of small, dull-but-real workflow we help owners set up at Massachusetts AI Agency (617-398-0033). Honestly, though? A plain chat window and ten minutes tonight will show you most of the win.