Balance territories with travel-time math

Build OD matrices between reps and accounts, draw catchments around offices, normalise lead addresses at scale.

Sales territory design used to be a one-off consulting project. With Footstep it becomes a re-runnable pipeline. Geocode the account book. Build a travel-time matrix from each rep's home base to each account. Solve for territory assignments that balance workload and minimise drive time.

On the inbound side, parse_address and geocode normalise raw lead data before deduplication. batch_geocode handles bulk imports from new data providers.

When new offices open or hiring shifts, redraw catchments with get_isochrone and re-balance against the existing book.

Patterns

What this looks like in practice

Common shapes mapped to the tools you'd reach for.

Territory balancing

Compute a matrix between rep home bases and accounts. Use a balancing algorithm to assign accounts to territories that equalise total drive time per rep.

Office catchment

Draw a 60-minute drive-time isochrone from each office. Use it as the inbound-lead routing rule for that office, with overlap resolved by office capacity.

Lead-list normalisation

New data provider delivers a CSV of leads with messy addresses. parse_address structures them, batch_geocode anchors them, reverse_geocode adds admin hierarchy. Ready for deduplication and routing.

Tools you'll reach for