How to Run a Weekly SDR Performance Review From Your CRM

A useful weekly SDR review measures outcomes, not just activity. Pull calls, emails, meetings and deals from the CRM, class each contact by lead type, trace every meeting booked back to the touches that produced it, and finish with two or three questions for the meeting. AI can assemble the report; the manager confirms what it means.

What should a weekly SDR review measure?

It should measure what the SDR produced and how: meetings booked and held, by lead type and segment; the touches that led to each meeting; replies and their quality; and the pipeline those meetings created. Activity, such as calls and emails, matters as context, not as the headline.

A practical set of measures:

Lead types make the numbers meaningful. A useful set is high intent (they asked for contact), discovery (they engaged with content), signal (a trigger fired), target accounts (named focus accounts) and cold. Meetings from each type mean different things.

Why do activity counts mislead?

Because activity measures effort, not results. A week of 400 calls and 300 emails can produce fewer meetings than a week of half that, spent on better-matched accounts with better messages. Rewarding activity encourages volume over quality, which hurts deliverability and reputation.

Perception is also unreliable. According to METR's 2025 randomised trial, experienced developers believed AI had made them 20% faster when it had made them 19% slower. That was a study of coding, not sales, but the lesson travels: measure outcomes from systems rather than asking how things went.

Leaders want this clarity. According to Microsoft and LinkedIn's 2024 Work Trend Index, 59% of leaders worry about quantifying AI's productivity gains. A weekly review grounded in CRM outcomes answers that worry for the SDR function.

How do you build a weekly SDR review from the CRM?

Pull the week's activities, contacts, meetings and deals from the CRM, read only. Assign each contact a lead type and segment, count meetings by type, and for each meeting build a short timeline of the touches before it across calls, emails and LinkedIn. Add pipeline from the meetings, then compare with recent weeks.

The meeting timelines are the most useful part. For each meeting booked, list every touch in order: the first email, the call, the LinkedIn message, the reply. Patterns appear quickly, such as meetings coming mostly from a second call after an email, or from one segment. Those patterns tell the team what to do more of.

A cumulative record helps too. Keep the weekly figures in one data file, so trends are visible and the report never depends on someone's memory of last month.

What should the weekly meeting discuss?

The meeting should discuss what the numbers suggest, not recite them. Two or three questions are enough: which lead type or segment is converting best and why, what the meeting timelines say about effective sequences, and what to change next week. Record the decisions and check them the following week.

Good questions are specific: "Signal-based meetings doubled while cold fell; do we move more time to signals?" or "Most meetings came after a second call; should the sequence add one?" Vague discussion of "activity levels" wastes the time.

How can AI help with SDR reviews without replacing judgement?

AI can pull the data, class contacts, build the meeting timelines, compare weeks and draft the commentary and questions. The manager reviews the draft, corrects any misclassified contacts, adds context the data cannot show, and owns the conclusions. AI saves hours of spreadsheet work; judgement stays with people.

Two cautions keep it honest. First, connect to the CRM read only, so the report never changes records. Second, have the manager confirm any judgement about a person's performance. Numbers support a coaching conversation; they do not replace it.

McKinsey's 2025 State of AI survey found 88% of organisations use AI in at least one function, but only 39% report enterprise-level earnings impact. Reports that tie AI-supported work to outcomes help close that gap. The guide to weekly lead reports covers the marketing side.

Skein builds weekly SDR reports that pull from the CRM read only, class leads and trace meetings, with a manager confirming the read-out; the outcomes page shows the reporting set. That suits a B2B team with at least one dedicated SDR. A founder doing their own prospecting may need only a simple weekly meeting count.

Frequently asked questions

What metrics should an SDR be measured on?

Focus on outcomes: meetings booked and held, broken down by lead type and segment, positive replies, touches per meeting and the pipeline those meetings create. Activity totals such as calls and emails are useful context, but rewarding them alone encourages volume over quality.

How do you run a weekly SDR meeting?

Review a one-page report built from the CRM, showing meetings by lead type, the touches behind each meeting and the pipeline created. Discuss two or three specific questions the numbers raise, decide what to change next week, and check those decisions at the following meeting.

What are lead types in SDR reporting?

Lead types group contacts by how they arrived, such as high intent (they asked for contact), discovery (they engaged with content), signal (a buying trigger fired), target accounts (named focus accounts) and cold. Measuring meetings by type shows which sources actually produce results.

Can AI create SDR performance reports?

Yes. AI can pull activity and meeting data from the CRM, class contacts, build touch timelines for each meeting, compare weeks and draft commentary. A manager should review the draft, correct misclassifications and own the conclusions, especially any judgement about individual performance.

Why shouldn't SDRs be measured on activity alone?

Activity measures effort, not results. High call and email counts can produce fewer meetings than focused work on well-matched accounts. Rewarding activity alone pushes volume, which can damage email deliverability and the company's reputation with prospects, while hiding what actually books meetings.

Related reading