For sales and territory reps
Plan account visits with less backtracking
Typical route setup
- Route size
- The accounts selected for one territory day
- What drives the order
- A couple of booked meetings anchor the day; the drop-ins flex around them.
- Where the list comes from
- A CRM export, a territory list, or a saved view filtered to this week.
Why CRM order and geographic order differ
CRM exports are often sorted by account name, owner or record number. None of those fields describes the road network, so the exported sequence can bounce between parts of a territory.
Plot the same list as a geographic sweep and compare the estimated driving totals. The difference is route-specific; the useful outcome is seeing the trade before appointments are confirmed.
Working from a CRM export
Export the view you already use
Most CRMs will export a filtered list view to CSV. Accounts due for a visit this week, with their addresses, is the list you need. Include the account name so that column becomes the note attached to each stop.
Paste the column, do not retype it
A single column of complete addresses works, as do separate street, city, state, and ZIP code columns. Common header names are recognized without any setup.
Review old CRM addresses
Every CRM has them: the billing address instead of the site, a suite number in the street field, a record that has not been touched since the customer moved. Anything the geocoder cannot place confidently is flagged with candidates on a map rather than dropped or guessed. The review step can also reveal stale records in your territory data.
Plan around booked meetings
Booked meetings and flexible drop-ins are different kinds of stop and should be treated differently.
First optimize all selected accounts to see the efficient drive-time order. Then move the booked meetings into the positions their times demand and place flexible drop-ins around them manually. The updated leg estimates show the travel cost of those choices.
Leave more slack than the drive time suggests. The planner does not know how long parking, security, reception or the conversation itself will take. Add overhead based on your own records instead of using a generic per-stop assumption.
Frequently asked questions
Can I import accounts from Salesforce or HubSpot?
There is no direct CRM integration. Export a report to CSV or copy the address column from a list view and paste it into the planner. Include the account name in a notes column so it stays with the stop.
How do I handle a booked meeting mid-day?
Optimize the full list to get a drive-time baseline, then drag the meeting into the required position. The optimizer keeps only the chosen start and finish fixed; it does not pin an intermediate meeting or enforce its time.
Can I plan a multi-day territory sweep?
Plan each day as its own route. A useful method: sort the territory roughly into geographic clusters first, then optimize within each cluster as a day. That is closer to how a good rep works a territory anyway.
Is it worth it for only ten accounts?
It depends on the territory. Optimize the list and compare its estimated drive time with the original order. In a compact area the difference may be small; across a wider metro the map may reveal obvious backtracking.
Can I keep the account name with each address?
Yes. A notes column stays with each stop in the planner and printout, and within the first-25-stop mobile checklist. Keep confidential CRM information out of notes and shared links.
Does it show which accounts are near each other?
The route map makes nearby accounts easier to spot. Use those clusters as one input when deciding which accounts belong on a future territory day.
Try it with tomorrow's stop list
Choose the start and finish, optimize the stops between them, and compare the result with your current order.
Open the optimizer