CRM Reports for Sales Managers: What to Read Each Week

Which CRM reports does a sales manager need each week?

You need six reports, and each one answers a question you would otherwise have to ask around the office.

The examples in this guide follow one invented team with a target of 1,000,000 for the quarter, in no particular currency. The numbers are made up and round so the arithmetic is easy to follow. They are not benchmarks, and a result that matches them tells you nothing about how your team is doing. The six reports and their questions:

Pipeline coverage: do we have enough open deals to reach the target?
Win rate: of the deals we finished, how many did we win?
Sales cycle: how long does a deal take, and can new deals still close in time?
Activity: is the work happening, and on the deals that need it?
Lead source: where do the deals we win come from?
Forecast: what will we probably close this period?

How do you read pipeline coverage?

Pipeline coverage tells you whether you have enough open deals to reach the target. The plain formula is: coverage = value of open deals with a close date in the period ÷ target for the period. Partway through a period, divide by what is left of the target, because deals you have already won no longer need covering.

Made-up example, not a benchmark: the team has won 200,000, which leaves 800,000 to close. It has 2,400,000 in open deals due this quarter. Coverage is 2,400,000 ÷ 800,000 = 3 times.

Read coverage against your own win rate. Metabase's guide to the metric calls the common 3x to 4x multiplier a rough heuristic and prefers 1 ÷ win rate as the target. With the invented 25% win rate from the next section, that is 1 ÷ 0.25 = 4 times. This team would need 3,200,000 in open deals, so it is 800,000 short.

Three things distort this report:

Deals with close dates far in the future inflate it, so count only deals due inside the period.
A deal in the first stage counts the same as one waiting for a signature. Show a weighted version next to the raw one, using each deal's value × its stage probability.
Coverage can fall after a strong period simply because won deals left the pipeline. Check how much new pipeline was created before you treat the drop as a problem.

How do you calculate and read win rate?

Win rate shows how many of your finished deals you won. The plain formula is: win rate = deals won ÷ (deals won + deals lost) × 100, counting deals closed in the same period.

Made-up example, not a benchmark: last quarter the team closed 100 deals, 25 won and 75 lost. Win rate is 25 ÷ (25 + 75) × 100 = 25%.

Check how your CRM defines it before comparing anything. Pipeline CRM's guide divides by deals in the final stage, and Zoho's velocity report adds overdue and old records to the closed deals in its denominator, so two systems can show different rates for the same deals.

Look at a rolling quarter each week, because a single week is mostly noise. If four deals closed this week, one deal moves the rate by 25 points. Split the rate by rep, pipeline and lead source, since a steady total can hide one rep falling while another rises. Calculate it by value as well as by count: a team that wins small deals and loses large ones looks healthier by count. Ask for a lost reason on every lost deal, then read the most common reasons once a month.

How do you measure the sales cycle?

The sales cycle is the average number of days a won deal takes from creation to close. The plain formula is: sales cycle = total days from created date to close date for won deals ÷ number of won deals. Zoho's velocity report measures it this way, and some teams start the clock at first contact, so write down which start date you use.

Made-up example, not a benchmark: the team won ten deals last quarter. Nine took 40 days and one took 240, which adds up to 600 days. The average is 600 ÷ 10 = 60 days, while the middle deal, the median, took 40.

Read that gap first. One long deal pulled the average up by 20 days, so show the median too, or report very large deals separately. Then use the cycle to test your coverage. With 30 days left in the quarter, even a 40-day deal created today closes next quarter, so new pipeline will help next quarter's number more than this one's.

When the cycle gets longer, a report of time spent in each stage shows where deals wait. HubSpot offers one, and many CRMs have an equivalent. A deal stuck at proposal and a deal stuck at contract approval need different conversations.

Which activity numbers are worth checking?

Check completed activity per rep and, more usefully, how many open deals have gone quiet. The plain formulas are: activity per rep = completed calls, meetings and visits in the week ÷ number of reps, and quiet deal share = open deals with no activity in the last 14 days ÷ all open deals. Choose the number of days to suit your own cycle.

Made-up example, not a benchmark: four reps completed 200 calls, meetings and visits, which is 50 per rep. Of 100 open deals, 20 had no activity in 14 days, so the quiet share is 20%.

Use activity to decide what to ask, and compare each rep with their own recent weeks. A falling count next to a healthy win rate may only mean the rep is deep in a few large deals. A count used to judge people is also easy to inflate with quick calls, so treat it as a coaching prompt.

The quiet deal list is the part you act on. Open it in the review and ask for a next step or a decision to close on each deal. Count completed work only, as HubSpot's completed activities report does, since a meeting on the calendar may never have happened. If your reps work in the field, our guide on confirming field visits covers how to make that count reliable.

How do you read a lead source report?

A lead source report shows which sources produce won deals, and that can be a very different list from the sources that produce the most leads. The plain formula is: source conversion = won deals from a source ÷ leads from that source × 100. Put revenue by source next to it, because one large deal can change the picture.

Made-up example, not a benchmark: ads brought 200 leads and 4 won deals, which is 2%. Referrals brought 20 leads and 4 won deals, which is 20%. Both produced four deals, but the ads leads took far more of the team's time to work through.

Split your reading in two. New leads by source can change within a week, so look for a sudden drop when a campaign ends or a form breaks. Won deals by source lag behind by your sales cycle, so judge a source on leads from a past period that has had time to close. Our guide on capturing and qualifying leads goes further on what a source is worth for the money.

Decide which contact gets the credit and write it down. HubSpot's attribution reports show why this matters: the first interaction model gives full credit to the first thing a contact did, and the last interaction model gives it to the final step before conversion. Keep the list of sources short and fixed, because free typing can split one source into several lines.

How do you read the sales forecast?

The forecast tells you what you will probably close this period, and it is easiest to read as a range. The plain formula is: weighted forecast = won so far + the sum of (each open deal's amount × its probability). HubSpot defines weighted amount the same way, as the amount multiplied by the deal probability.

Forecast categories add the team's judgment on top. The names vary by CRM. Microsoft's documentation describes Pipeline as early-stage or stalled deals with low confidence, Best case as deals that are progressing with no commitment yet, and Committed as deals where the customer has made a verbal or contractual commitment.

Made-up example, not a benchmark: the team's 2,400,000 in open deals splits into 400,000 in negotiation at 75%, 800,000 at proposal at 50% and 1,200,000 qualified at 25%. That gives 300,000 + 400,000 + 300,000 = 1,000,000. Adding the 200,000 already won, the weighted forecast is 1,200,000. If only the negotiation deals are committed, the committed figure is 200,000 + 400,000 = 600,000. The percentages are invented too.

Then test it against history. The team's 25% win rate on 2,400,000 gives 600,000, plus 200,000 won, which is 800,000. So there are three figures against a target of 1,000,000: 600,000 committed, 800,000 at the historical win rate and 1,200,000 weighted. The distance between the last two suggests the stage percentages may be too generous, unless these deals really are further along than usual. Set your percentages from how many deals at each stage went on to win.

Save a copy of the forecast each week and compare it with what closed, because a CRM normally shows today's data. HubSpot, for example, offers historical snapshots and a waterfall report that groups revenue movement as created, pushed, pulled, increased, decreased, won or lost. Forecast accuracy = actual ÷ forecast × 100. Made-up example, not a benchmark: 800,000 closed against a forecast of 1,000,000 is 80%. Each week, ask:

Which deals had their close date pushed again, and what changed for the customer?
Which deals moved to a higher category with no new activity behind the move?
Which single deal would change the result if it slipped?

How do you keep CRM report data trustworthy?

Agree on the definitions, make the fields your reports depend on hard to skip, and check the data on a fixed schedule. Salesforce's data quality training gives a useful frame: score records on age, completeness, usage, accuracy, consistency and duplicates, name who owns the records, and decide how often the checks run.

Put your definitions on one page: which stages count as open pipeline, which date starts the cycle, which report uses count and which uses value. If you sell in Saudi riyals, Jordanian dinars, Iraqi dinars or US dollars, also fix one reporting currency and how you convert to it, otherwise your coverage and forecast will shift with the conversion rate you happen to use.

Keep bad news safe to report as well. If a rep gets blamed for closing a dead deal as lost, the CRM fills up with dead deals, and every report in this guide gets worse. These are the checks to run:

Past close dates. Share to fix = open deals with a close date in the past ÷ all open deals. Made-up example, not a benchmark: 10 of 100 is 10%, and those ten are the first to update.
Required fields. Ask for each field at the stage where it becomes known, such as amount before a proposal and a reason at a loss. Salesforce's training notes that certain fields may be required at each stage, and its validation rules stop a save that breaks your rule.
Dead deals. Close them as lost. While they stay open they inflate coverage and never count against your win rate.
Duplicates. Keep one record per customer. Salesforce's training says duplicates cause sales teams to lose trust in their CRM, and its rules can either block a new duplicate or allow it with an alert.
Owners. Every open deal needs one owner, and deals need a new owner when a rep leaves, or the reports by rep stop meaning anything.
Spot checks. Each week, open a few deals at random with their owners and compare the record with what the customer actually said.

What should the weekly review look like?

A short meeting in a fixed order works well, moving from the overall number down to individual deals. Fix the data before the meeting, so the time goes on decisions. This is a suggested order, and you should adjust it to your team size:

Before the meeting, each rep updates past close dates and closes dead deals.
Start with the forecast: committed, weighted and what changed since last week.
Move to coverage: how far is it from what your win rate requires, and how much new pipeline is needed?
Go through quiet deals and deals with moved close dates, and agree on a next step or a decision to close.
Glance at new leads by source and at activity, and follow up on anything that dropped sharply.
Once a month, read win rate, sales cycle and won deals by source over a longer period.

How does Repzo handle this?

In Repzo Workstation, Analytics & Reporting covers leads, deals, activities, tickets, projects and dashboard-level KPIs. You can filter reports by date range, owner and pipeline, group trends by day, week, month, quarter or year, and show them as line, bar, pie, funnel or area charts. Reports can be exported and shared.

The Sales CRM keeps amount, probability, forecast category and expected close date on each opportunity. It supports more than one pipeline and multi-currency deal values, and it includes win/loss analytics and stage velocity. Lead management has source and channel fields for reporting on campaigns and referrals, tracks conversion by source and rep, and can enforce required fields at each qualification stage. KPI targets can be assigned to users or teams and followed in dashboards.

The public feature pages do not list pipeline coverage or a past close date check as named reports. If you want those ready made, ask our sales team to show how they would be set up. Workstation also has a 7-day free trial, and one fair test is to enter some of your own closed deals and see whether the reports match the numbers you worked out by hand.

Frequently asked questions

What is a good pipeline coverage ratio?

No single number fits every business. Start from 1 ÷ your own win rate, so a win rate of 25% points to 4 times and 50% points to 2 times. Metabase's guide calls the common 3x to 4x multiplier a rough heuristic. Then adjust using what your own past quarters show.

Should win rate be calculated by number of deals or by value?

Look at both. Count shows how often you win, and value shows whether you win the deals that matter most to revenue. A large gap between the two usually means deal size is affecting your results, so split the report by size.

Should open deals count in the win rate?

No. Include only deals closed as won or lost in the period, because open deals have no result yet. This is why dead deals do so much harm: while they stay open, they never count as losses, so the rate looks better than it is.

We close only a few deals a month. Are these reports still useful?

Yes, over longer periods. Read win rate and sales cycle across six or twelve months, because a handful of deals can swing them sharply. Each week, focus on the forecast, the quiet deals and the next step on each open deal.

What is the difference between a deal stage and a forecast category?

A stage records where a deal is in your sales process, and a category records how likely it is to close. Systems handle the link differently: HubSpot maps stages to categories, while Microsoft has the seller set the category on each opportunity.

Can I run these reports in a spreadsheet?

Yes, if your records hold the created date, close date, amount, stage, owner and lead source for each deal. The formulas in this guide work in any spreadsheet. The harder part is keeping one current copy that everyone updates, which becomes more difficult as the team grows.