Tracking Serves Two Purposes — Payment and Performance
Before building the tracking system, clarify what it needs to do. SDR performance tracking for a web agency serves two distinct purposes simultaneously, and conflating them produces a tracking system that does neither well.
Tracking for Payment — Accurate Commission Calculation
The verified close record that drives commission calculation, monthly statement generation, and dispute prevention. This tracking must be accurate down to the invoiced amount, timestamped with both close date and verification date, and visible to both parties in real time so the month-end statement confirms rather than reveals. Without accurate payment tracking, every commission conversation is a negotiation.
Tracking for Performance — Coaching and Management Decisions
The metrics that tell you whether the SDR is doing enough (effort), doing it well (skill), and building toward future closes (leading indicators). Performance tracking is the diagnostic layer — it tells you which management conversation to have and what specifically to say in it. Without performance tracking, every coaching conversation is a guess about what is causing the problem.
The tracking system must serve both purposes. An agency that only tracks for payment produces accurate commission statements but has no visibility into why performance is declining before it shows up in close count. An agency that only tracks for performance has coaching capability but no commission record, producing disputes at month end. The complete system covers both — with a shared verified close record that feeds into commission calculation and performance analysis simultaneously.
What to Set Up Before the First Call — Day 1 Tracking Configuration
The most common tracking mistake is starting to track after the first month and then trying to reconstruct what happened from memory. Tracking infrastructure must be in place before the first dial — because the first session's data is already meaningful and because establishing the tracking habit from day 1 prevents it from feeling like a new monitoring imposition after the SDR has already been working independently.
Configure quota and commission structure in the tracking system
Enter the monthly close quota (e.g., 3 closes minimum), ramp quota if applicable (e.g., 2 closes in months 1–2), and commission rate structure (e.g., 10% under £1,000 / 15% £1,000–£2,500 / 18% above £2,500) before the first session. Both parties should be able to see these configured values — the quota zone calculation and commission calculation both depend on them being set in advance, not inferred retroactively.
Establish the session minimum standard in writing
Document and communicate: minimum 35 dials per session, minimum 3 sessions per week, real-time status updates required (not end-of-session batch logging). The SDR should see these standards before their first session — not receive them as feedback after a session where they made 15 dials. Standards set before day 1 are expectations. Standards introduced after underperformance begins are criticisms.
Load the campaign list and assign leads to the SDR
Every contact the SDR will call must be in the pipeline system before calling begins — not added progressively from a separate spreadsheet. This ensures: (a) the SDR's dial count is recorded against contacts that appear in the shared system; (b) status updates go to the shared authoritative record, not a personal log; (c) the agency owner can see exactly what territory is being worked and approximately how much list is remaining.
Confirm the owner's daily verification routine
The owner's daily verification queue review — clearing pending closes within 24 hours — must be established as a habit before the first close is logged, not started when the first close arrives. An SDR who logs their first close and waits 4 days for verification has had a poor introduction to the commission payment experience. The owner's morning routine must be operational before there is anything in the queue.
The Three-Layer Tracking Cadence — Daily, Weekly, Monthly
Ramp-Phase Tracking vs Established SDR Tracking
The metrics you track and the thresholds you apply differ significantly between months 1–2 (ramp phase) and month 3+ (established SDR). Applying established-SDR standards to a ramp-phase SDR produces premature performance conversations that damage confidence at exactly the point when it should be building. Applying ramp-phase standards to an established SDR masks genuine performance problems by excusing them as "still developing."
What to track and what to expect
What to track and what to expect
The Monthly SDR Performance Review — Format and Questions
The monthly performance review is a 20-minute structured conversation that turns the tracking data into a shared understanding of what happened and what changes next month. It is not a performance judgement — it is a joint diagnostic session where both the owner and the SDR review the same data and arrive at the same conclusions. Both parties have access to the leaderboard, so neither is presenting information to the other that they have not already seen.
When Tracking Data Triggers Action vs When to Simply Observe
| What the Tracking Shows | Act — Specific Conversation This Week | Observe — Check Again Next Period |
|---|---|---|
| SDR below 50% quota pace at day 15 | Specific pipeline conversation this week. Not at month end — there are still 15 days to recover if you act now. | N/A — this threshold always triggers action |
| Single session with under 20 dials | Only if it is the 2nd consecutive low-dial session. Single low session may have an explainable cause. | One low-dial session — note it and check the next session before messaging |
| Close count drops by 1–2 from last month | Single-month variation is not a trend. Check whether dials were consistent. Wait for second month if dials were adequate. | Only if dials also dropped this month — then it is an effort issue requiring action |
| Warm pipeline at 0 on Friday afternoon | Message this afternoon — there is still time to build pipeline before Monday. Do not wait for Monday morning. | N/A — Friday empty pipeline always warrants a Friday message |
| Callback conversion declining for 2+ months | Close conversation coaching conversation this month. Specifically the audit PDF delivery and close call structure. | First month of declining callback conversion — could be sample size noise. Monitor next month before acting. |
| Warm contacts per 100 dials declining over 4 weeks | Start building next campaign list this week. List fatigue is starting — act before close count declines. | Single week of fewer warm contacts per 100 dials — may be geographic variation. Check over 3–4 weeks. |
| SDR self-reports motivation issue | Immediate diagnostic conversation — niche rotation, burnout, personal situation, or commission problem? Do not defer to next month's review. | N/A — any direct communication about motivation requires same-week response |
The tracking failure that produces the worst outcomes: Setting up tracking and then reviewing it only at month end — without the daily and weekly check cadence. By the time a month-end review reveals a problem (SDR with 1 close, 0 warm pipeline, declining dial count), 30 days have been lost. The daily and weekly cadence exists specifically to catch problems at week 2, not week 4. A tracking system that is only reviewed monthly is a payment system, not a management system.
- Quota and commission configured before day 1 — both parties see the same standards on the leaderboard from the first session
- Daily tracking: verification queue + leaderboard (close count, quota zone, warm pipeline) + activity log (dial count) — all in one view
- Weekly tracking: session count, close count, warm pipeline entering next week — leaderboard provides all three without manual compilation
- Monthly tracking: all 7 performance metrics + verified close record for commission statement — from the same data source both parties have been watching
- Ramp vs established configuration: quota zone and commission structure adjustable for ramp period without affecting established SDR tracking
How do you track SDR performance at a web agency from day 1?
How often should you review SDR performance at a web agency?
What should a monthly SDR performance review cover?
Track SDR Performance From Day 1. Daily. Weekly. Monthly.
Quota configured before first call. Verification queue clearing every morning. Leaderboard showing all 7 metrics in real time. Monthly review from shared verified data. The complete tracking system — not bolted on after problems appear, built before the first dial. $249/month.
Start Free Trial — No Credit Card →