Short answer: The sales team KPIs worth reviewing every week are the few that tell you what to do on Monday: new leads by source, first response time, open leads with no next step, overdue follow-ups, deals that moved forward, and deals stuck in a stage. Keep win rate and lost reasons for a monthly look.
Most small sales teams I’ve worked with either track nothing or track everything, and in both cases nobody acts on the numbers. Picking sales team KPIs is mostly about choosing what to leave out. This post gives you a short weekly scorecard, explains how to count each number, and lists the metrics I’d stop putting in front of the team. It sits under our guide to CRM for sales teams. If you’re looking for how reps should log calls and meetings in the first place, read sales activity tracking first. That post is about capturing the work. This one is about which numbers you review once the work is captured.
Where I’m coming from: I run Diligent Creators, a software and design agency, and I build CRM software, including EloSync. A lot of that work has been sitting with founders and sales managers while they decide what a report should show. In my experience the first request is often a leaderboard of calls per rep, and it rarely stays useful for long.
What are sales team KPIs?
Sales team KPIs are the handful of numbers a team agrees to review on a fixed schedule because each one points to an action. If a number can move and nobody would do anything differently, it’s a metric you can look at occasionally, not a KPI.
A small team has one manager, often the founder, and maybe twenty minutes a week for this. For each candidate KPI, ask: “If this goes red, who does what by Friday?” If you can’t answer, drop it.
Why review sales KPIs weekly?
Weekly is short enough to catch a lead that’s going cold and long enough for the numbers to mean something. Daily reviews turn into noise for a small team, and monthly reviews find problems after the deals are already lost.
Some numbers are too small to judge in a week. If your team closes a few deals a month, one result swings a weekly win rate wildly, so those belong in a monthly read.
The weekly sales KPI scorecard
These are the KPIs I’d put on a small team’s weekly sheet, roughly in the order a lead experiences them.
| KPI | What it tells you | How to count it | Typical action when it’s off |
|---|---|---|---|
| New leads by source | Whether the top of the pipeline is filling, and from where | Leads created this week, grouped by source field | Look into a source that dropped; check its form or ad is still running |
| First response time | How long a new lead waits for a human reply | Time from lead created to first logged contact, median for the week | Fix routing or notifications; cover the hours when leads sit |
| Open leads with no next step | Leads that will quietly disappear | Open leads with no open task or follow-up date | Each rep gives every one a dated task or closes it |
| Overdue follow-ups | Workload and slipping promises | Follow-up tasks past due date, per rep | Rebalance leads if one rep is overloaded |
| Deals moved forward | Real progress, as opposed to activity | Deals that changed to a later stage this week | If it’s flat, look at the stage where deals are piling up |
| Stalled deals | Where the process is stuck | Open deals unchanged in their stage for longer than your usual cycle for that stage | Decide on each: push, re-qualify or close as lost |
| Pipeline added | Whether next month has enough to work with | Value (or count) of new deals that entered a qualified stage this week | If it’s thin for a few weeks, shift time to prospecting |
Seven rows is plenty. Starting from nothing, pick three: open leads with no next step, overdue follow-ups and stalled deals. They catch deals lost to neglect rather than to a real “no”.
Notes on counting
- Use the median for response time, not the average. One Friday-night lead answered on Monday drags an average a long way.
- Define “stalled” per stage. A deal can reasonably sit in “Proposal sent” longer than in “New”. Our post on sales pipeline stages covers how to set stages with clear exit criteria, which makes this number far easier to count.
Monthly and quarterly KPIs: read them, don’t chase them
Win rate, deal size, cycle length and lost reasons need more than a week of data on a small team.
- Win rate. Won deals divided by won plus lost, for deals closed in the period. Read it monthly at the earliest, and compare it by source or by service rather than by rep when the numbers are small.
- Lost reasons. One short line per lost deal, read together once a month. It tells you what to change in the offer or the process.
- Sales cycle length and average deal size. Watch the trend over a quarter, not week to week.
These also feed your forecast. If you want to turn them into a number for next month, our sales forecasting method for small teams walks through it.
Leading vs lagging sales KPIs
Leading KPIs move before revenue does, so you can still change the outcome. Lagging KPIs record what already happened. Weekly reviews should lean on leading ones.
Response time, open leads with no next step, overdue follow-ups and stalled deals are leading: you can fix each this week, and that changes what closes next month. Revenue, win rate and cycle length are lagging, so they tell you the result after the work is done.
Sales KPIs I’d stop reviewing every week
Some numbers look like KPIs but mostly create anxiety or busywork. I’d take these off the weekly sheet:
- Raw call and email counts per rep. They reward volume over judgement. If you want a capacity check, overdue follow-ups does that job better.
- Total pipeline value with no ageing. Deals nobody has touched in two months still look healthy on paper. Pair value with the stalled-deals count.
- Anything nobody owns. If a number has no name next to it, it will be read aloud and ignored.
When I plan software work with small businesses, the useful question is always “what problem does this help us fix?” My post on technology strategy for small businesses uses the same idea of prioritising by business pain, and it applies just as well to a KPI sheet.
Per-rep KPIs vs team KPIs
Review hygiene KPIs per rep and outcome KPIs at team level. Splitting outcomes per rep on a small team mostly measures luck and lead quality.
Each rep can fix their own no-next-step count, overdue follow-ups and response time, and seeing them side by side shows who’s overloaded. Deals moved forward, pipeline added and win rate depend on which leads a rep happened to get, so read those for the whole team. If one rep’s queue is always the longest, that’s usually a lead routing problem rather than a performance problem.
An example weekly KPI sheet (illustrative)
The table below is an illustrative layout with made-up numbers for a fictional three-person team. It isn’t data from any real company or from EloSync. It shows the shape: this week, last week, a target the team chose, and one action.
| KPI (illustrative) | This week | Last week | Team target | Action |
|---|---|---|---|---|
| New leads (web form / Facebook lead forms / referral) | 14 / 9 / 2 | 15 / 3 / 1 | No target, watch trend | Facebook form volume jumped; check lead quality |
| Median first response | 3 hrs | 1 hr | Under 1 hr in working hours | Weekend leads waited; set a Monday 9 AM sweep |
| Open leads with no next step | 6 | 2 | 0 | Each rep clears theirs today |
| Overdue follow-ups (A / B / C) | 1 / 7 / 0 | 2 / 4 / 1 | Under 3 each | Move new leads from B to C for two weeks |
| Stalled deals | 4 | 4 | Under 3 | Same four as last week: decide on each now |
The target column is something the team set for itself, not an industry benchmark, and the action column is never empty when a number misses. For the response-time row, our post on lead response time goes into what a sensible target looks like.
How to run a 20-minute weekly KPI review
Fill in the sheet before the meeting starts, and hold it at the same time each week.
- Two minutes: what’s red. Read only the rows that missed their target or moved sharply.
- Ten minutes: hygiene rows per rep. No next step, overdue follow-ups, response time. Agree fixes and owners.
- Five minutes: stalled deals. Name each one and decide: push, re-qualify or close.
- Three minutes: last week’s actions. Did they happen? If not, why?
Keep this separate from a forecast review, which is about what will close; combined meetings tend to skip the hygiene rows. If stalled deals keep coming up, check whether the follow-up rhythm itself is the problem; our sales follow up cadence post covers how many touches to make before you close a lead out.
Getting the numbers out of your CRM
Every KPI above comes from three things: leads with a source and created date, tasks with owners and due dates, and a stage history on each deal. With those captured, counting is filters and a spreadsheet.
- Make source a required field on every lead, and set it automatically wherever leads arrive through a form or integration.
- Every open lead gets a task. This is what makes “no next step” countable.
- Move the stage when the deal moves. A stage change has a date; a note saying “sent proposal” can’t be counted.
- Pull the numbers on the same day each week into one sheet, this week beside last week. For the source row, Diligent Creators’ guide to LinkedIn marketing for founders and small businesses shows how to tell which LinkedIn conversations turn into leads.
Where EloSync fits
EloSync is the CRM we’re building for small teams, so here is what it covers today, stated plainly. The Leads, Tasks and ToDos modules are free. Leads can be added manually, sent in through a webhook, or arrive straight from Meta Lead Ads (Facebook lead forms), so the source and created time are captured without anyone retyping. Follow-ups live as tasks on a Kanban board with owners, and roles control who sees and edits what, which keeps per-rep numbers honest. Extra features come as Marketplace add-ons, and the REST API and webhooks let you pull leads and tasks into your own sheet for the weekly count.
I’d still keep the KPI sheet itself in a spreadsheet at first, so the team agrees on definitions before anything is automated. If you run a small sales team and want to see the setup, have a look at EloSync for sales teams.
FAQ
How many KPIs should a small sales team track?
Three to seven on the weekly sheet. Start with open leads with no next step, overdue follow-ups and stalled deals, then add response time and leads by source once those are under control.
What is the difference between a sales metric and a sales KPI?
A metric is any number you can measure. A KPI is a metric the team has agreed to review on a schedule because it leads to a specific action and has an owner. Most metrics should stay off the weekly sheet.
Should I set targets for every sales KPI?
No. Hygiene KPIs, such as leads with no next step, can have firm targets because you control them fully. Volume numbers like new leads are better watched as a trend until you have enough history to set a sensible target.
Are calls per rep a good sales KPI?
Usually not on their own. They reward volume and are easy to inflate. Overdue follow-ups and open leads with no next step give a clearer picture of whether the right leads are getting attention.
How often should sales KPIs be reviewed?
Weekly for leading KPIs you can act on straight away, monthly for win rate and lost reasons, and quarterly for sales cycle length and average deal size on a small team.
