FlowsBook a callSign inCreate free accountSign up
Sales and prospecting

A weekly prospect email for a sales manager: what to put in it

One email on Monday morning: new prospects by rep, the strongest ten, what changed since last week and where the gaps are. How to design it so a manager acts on it.

Part of the guide AI employee for sales prospecting

By the xMap team · · 4 min read

A good weekly prospect email gives a sales manager four things in the first screen: how many new prospects appeared in each rep's patch this week, the ten strongest across the team with a one-line reason each, what changed since last week, and any patch that came back empty. Everything else, the full list and a map, sits behind a link or an attachment. The manager reads it in two minutes on Monday and walks into the team meeting knowing who should call whom.

This article is for sales managers and team leads who want a dependable Monday view of new business, and for the operations people who build it for them. It covers what belongs in the email and what does not, how to split prospects fairly between reps, a made-up example, the mistakes that make managers stop reading, and the AI employee that sends it.

What a manager needs, and what a rep needs

Reps want a long list to work through: every new business in their patch with a phone number and a reason to call. Managers want the opposite: a short view that tells them whether the pipeline is filling, where effort should go and which deals deserve their own attention. Mixing the two produces an email that is too long for the manager and too thin for the reps. Send reps their own daily lists; send the manager this weekly summary.

The parts of the email

  1. The headline line. New prospects this week in total, against last week: "43 new prospects, up from 31."
  2. By rep. One line per rep: how many new in their patch, how many scored strongly.
  3. The top ten. The ten best across the team, each with its name, area, the rep it belongs to and one sentence on why it scored high.
  4. Changes. Prospects or customers that closed, changed name or saw a big rating drop.
  5. Gaps. Any patch with nothing new, so the manager can ask whether the search is right or the area is saturated.
  6. The full list. A link to download every prospect as a spreadsheet, and a map.

Splitting prospects fairly between reps

If reps have fixed patches, assign prospects by patch. If not, the Split by territory block shares the week's prospects out by area into compact territories of about the same size, one per rep you name, and adds each prospect's owner. A stable split matters: if territories shift every week, reps stop trusting that the leads in their patch are theirs.

A worked example

Here is a made-up case. A company selling commercial cleaning contracts in Nairobi has three reps. Every Monday at 07:30 the manager receives:

  • "38 new prospects this week, up from 29. 9 strong fits."
  • "Westlands (Amina): 16 new, 5 strong. Upper Hill (Brian): 14 new, 3 strong. Industrial Area (Carol): 8 new, 1 strong."
  • Ten named businesses: new offices, clinics and hotels, each with a sentence such as "New private clinic, 4.6 from 80 reviews, two floors, likely needs daily cleaning" and the rep's name.
  • "2 changes: one customer in Upper Hill is now marked closed; a prospect in Westlands changed its name."
  • "No gaps this week."
  • A button to download the 38 as a spreadsheet, and a map.

Every figure above is invented. The point is the order: the manager knows within seconds that Westlands is producing, that Carol's patch is thin, and that a customer may have been lost.

Mistakes that make managers stop reading

  • Sending the whole list in the body. Fifty rows in an email is a spreadsheet, not a summary. Attach it.
  • Repeating last week's prospects. If the same names come back every Monday, the email stops being news. Only new results should count as new.
  • Scores without reasons. A score of 82 means nothing on its own; a sentence saying why makes it a decision.
  • No comparison. A count without last week's count beside it cannot show whether things are getting better.
  • Sending it at the wrong time. Friday afternoon is too late to plan the week; Monday after the meeting is too late to use it.

Doing it with an AI employee

One AI employee builds and sends the whole email.

  1. Schedule every Monday at 07:30, in your time zone.
  2. Area of interest with your city or each rep's patch.
  3. Nearby places for the kinds of business you sell to, set to places opened in the last 12 months if you want only new ones, from xMap's places database.
  4. Only new, so prospects found in earlier weeks do not come back.
  5. xMap LLM to score each prospect from 0 to 100 against what you sell, with a one-line reason.
  6. Split by territory between your reps, or keep fixed patches from the area.
  7. A second xMap LLM block on the whole list, told to write the summary in the order above.
  8. Email to the manager, with the CSV link and a map.

To add the people to call at each prospect, put the Apollo block, which works with your own Apollo account, after the scoring step. The templates Morning call list with decision makers and call notes, New businesses in my territory, researched, into HubSpot and Weekly SaaS pipeline from three signals are close to this design.

Questions

Should the weekly email include every prospect?

No. Put the counts, the top ten and the changes in the body, and the full list behind a download link or attachment.

How do I stop the same prospects appearing every week?

Add the Only new block after the search. It lets through only businesses the flow has not found before.

Can the email be split by rep?

Yes. Use fixed patches in the Area of interest, or the Split by territory block to share prospects between named reps by area.

What time should it arrive?

Early on Monday, before the team meeting. Set the Schedule in your own time zone so it arrives at the same local time every week.

Templates that do this

IndustriesB2B sales

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.