FlowsBook a callSign inCreate free accountSign up
Sales and prospecting

A weekly review of a sales territory: what changed and who to call

A field rep's Monday is better spent on a short list of what changed in the territory than on the whole map. What a weekly territory review covers and how to automate it.

Part of the guide AI employee for sales prospecting

By the xMap team · · 4 min read

A weekly review of a sales territory answers three questions every Monday: what is new in my patch (businesses that opened or appeared since last week), what changed among the ones I already know (closed, a rating that fell, a new phone or website), and which handful deserve a call or a visit this week. Done by hand it takes a morning and is often skipped; done by an AI employee it lands in the rep's inbox before the first coffee, as one short list.

This is for field sales reps, area managers and small sales teams that sell to local businesses: suppliers to restaurants, salons, clinics, shops, offices or workshops. It covers what to include, what to leave out, a worked example, how managers read it across several reps, and the blocks that build it.

What belongs in the review

  • New businesses of the kinds you sell to, found since last week, with how long ago each opened when the date is known. New businesses are choosing their suppliers now.
  • Closures among businesses you know, so nobody drives to an empty shop and accounts can be cleaned up.
  • Ratings that dropped, which can mean a business under pressure: a chance for a supplier who solves the problem, or a credit risk to watch.
  • Businesses hiring, from public job postings: a company adding staff is growing and buying.
  • A short ranked call list, five to fifteen names, each with one reason.

Leave out the businesses you already serve, unless something about them changed. A review that lists the whole territory every week stops being read by the third week.

Drawing the territory once

A territory is easiest to keep as a drawn shape: draw it on the map in the Area of interest block, or list the districts it covers. If several reps share a city, Split by territory divides the week's results between them by area, in compact territories of about the same size, so each rep's review holds only their own patch.

A worked example

A made-up case: a rep for a coffee and kitchen equipment supplier covers Westlands and the neighbouring districts of Nairobi, selling to cafés, restaurants and bakeries. Her Monday review, one week in October, reads:

  • New this week (4): two cafés and a bakery found for the first time, one restaurant listed as opened last month.
  • Closed (1): a café she visited in the summer is now marked closed.
  • Rating dropped (2): a restaurant from 4.4 to 3.9, a bakery from 4.6 to 4.2.
  • Hiring (2): a restaurant group posting for a head chef and a café posting for baristas.
  • Call first: the newly opened restaurant (choosing suppliers), the restaurant group that is hiring (growing), and the restaurant whose rating fell (may need better equipment).

She plans Tuesday around those three, and the route for the visits comes from the same list. The businesses, ratings and counts in this example are invented.

Reading it as a manager

A manager with six reps does not want six emails. Two habits help:

  • Look at the counts before the names: a territory with no new businesses for a month may be saturated, or its search may need new kinds of place.
  • Read closures and rating drops across all territories together. A cluster of closures in one district is a market signal, not bad luck.
  • The Team findings block reads what all the reps' AI employees found this week against last and gives a manager a one-page brief with the figures counted, not guessed.

The AI employee behind the review

  1. Schedule: every Monday at 06:30, in the rep's time zone.
  2. Area of interest: the territory, drawn on the map.
  3. Nearby places: the kinds of business you sell to, across the area.
  4. Only new, and beside it What changed for closures, rating moves and new phone numbers or websites.
  5. Match with my table: leave out current customers.
  6. Job postings: who in the territory is hiring.
  7. xMap LLM: a fit score and one sentence of reason for each.
  8. Sort and limit: the best fifteen first.
  9. Email to the rep, with a map; or Route planner to put the week's visits in order.

What the rep receives is one email: the new, the changed and the hiring, each with its address, phone, website, rating and the reason it made the list, plus a map. A week with nothing new says so in one line.

Ready-made versions: New businesses in my territory, researched, into HubSpot, New openings to the field rep on WhatsApp, Split my city into fair sales territories and New places every morning, only new for reps who want it daily.

Questions

Why weekly rather than daily?

Weekly suits territories where a rep visits in person and plans the week ahead. Daily suits phone-based selling or fast-moving markets with many openings.

Can it skip businesses we already serve?

Yes. Upload your customers to My data and use Match with my table to keep only the businesses not found there.

How does it know a business closed?

The What changed block compares each business the flow found before with how it looks now and reports those marked closed, along with ratings that moved and new phone numbers or websites.

Can several reps share one flow?

Yes. Split by territory shares the results out by area, giving each item an owner, so each rep can get their own part.

Templates that do this

Read next

More on sales and prospecting · Every article · Templates

Put it to work

An AI employee in xMap Flows does this on live data, on its own timetable. Start from a template or describe it in plain words.