SDR Manager Outbound QA System

Building a repeatable outbound QA system is one of the highest-leverage activities for an SDR manager who wants to move beyond “spray and pray.” A weekly review cycle that separates list quality, message quality, and reply outcomes tends to cut list waste and improve reply rates within a matter of weeks. Here is the complete system: what to sample, how to score it, and how to turn findings into coaching that sticks.

Quick Answer

• If you’re an SDR manager whose team is hitting 1–3% reply rates and you suspect list quality is the issue → prioritize list quality scoring first, since a meaningful share of reply-rate problems trace back to wrong titles or contacts who have left the company.
• If you’re an SDR manager currently only auditing script compliance → shift to scoring all three dimensions (list quality, message quality, reply outcomes), because auditing only message quality optimizes for perfect emails sent to bad lists.
• If you’re an SDR manager with a team that has top performers hitting high reply rates but hitting a ceiling → inspect list quality weekly, because even best performers hit a ceiling when list quality degrades.
• If you’re an SDR manager looking to reduce wasted outbound effort from bad data sources → create an exception queue for systematic list quality problems, so a single bad source doesn’t keep burning outbound capacity while it’s being fixed.

Why Most QA Fails (and What This System Fixes)

Direct answer: The typical SDR QA process is a compliance check: “Did they follow the script?” That misses the point. Outbound quality has three independent dimensions that must be measured separately:

1. List quality – Are we contacting the right people at the right accounts?
2. Message quality – Is the copy relevant, concise, and personalized?
3. Reply outcomes – Did the prospect engage, and if not, why?

When you only audit message quality, you optimize for perfect emails sent to bad lists. When you only audit reply outcomes, you optimize for lucky hits. This system forces you to inspect all three every week.

The Weekly Sampling Protocol

Sample Size and Selection

A workable sample size is 20–30 outbound touches per SDR per week. That is enough to detect systemic issues without overwhelming the manager. The sample should be stratified:

• 10–15 cold emails (first touch)
• 5–10 follow-ups (second through fifth touch)
• 5 LinkedIn messages or call notes (if applicable)

A random-number generator on the CRM activity log works well for the base sample, with deliberate over-sampling from “struggling” segments: new hires, SDRs with declining reply rates, and accounts in new verticals. This is not a scientific audit; it is a diagnostic.

The Scoring Rubric

Each touch gets a score of 0–5 on three axes. A perfect score is 15. A workable rubric:

Tracking these scores in a simple spreadsheet over several weeks tends to surface patterns that no dashboard shows on its own.

How to Diagnose List Quality Issues

Direct answer: List quality is the most overlooked dimension. It’s common to see SDRs with strong message scores and few replies because they were emailing junior analysts at enterprise accounts when the actual buyer was a VP of Engineering.

The Three-Question Audit

For every sampled touch, ask:

1. Is this person in the buying group? Use the “MEDDIC” or “BANT” framework to confirm. If the SDR is contacting a “champion” who has no budget authority, that is a list quality failure.
2. Is there a recent trigger? Funding announcement, leadership change, product launch, regulatory shift. If the SDR cannot name a trigger, the list is stale.
3. Is the contact data accurate? Check LinkedIn, the company website, and a data enrichment tool. Wrong titles and contacts who have left the company are among the most common list quality failures.

The Exception Queue

When you find a systematic list quality problem—say, an SDR is pulling leads from a bad intent data source—create an exception queue. That queue holds all touches from that source until the data is re-verified. This is not punitive; it prevents wasted effort. Pausing an entire team’s outbound briefly to clean a list with a high bounce rate is often worth the short-term disruption, because the team ends up emailing real people afterward.

Message Quality: Beyond the Template

Direct answer: Message quality scoring is where most managers get subjective. A simple heuristic helps: would this email survive a five-second skim by a busy executive?

The Skim Test

Read each email for exactly five seconds, then answer: “What is the one thing the prospect would remember?” If the answer is “nothing” or “they mentioned my company name,” the message fails.

Common Patterns to Watch For

• The “value dump” – Three paragraphs of features. Score: 1. Fix: One sentence of value, one sentence of proof, one clear ask.
• The “false personalization” – “I saw you work at [Company].” Score: 2. Fix: Reference a specific project, blog post, or mutual connection.
• The “too clever” – A joke or cultural reference that falls flat. Score: 0–3 depending on execution and whether it lands with the specific recipient.

The “Reply Rate Ceiling”

Cold email reply rates across B2B are typically in the low single digits, with strong performers reaching notably higher by focusing on message quality. But even strong performers hit a ceiling when list quality degrades. That is why you must measure both.

Reply Outcomes: The Feedback Loop

Direct answer: Reply outcome scoring is the most straightforward, but it is also the most misleading if taken alone. A “not now” reply is a 3 on this scale—it is a positive signal. A meeting booked is a 5. But a “not now” from the wrong persona is still a waste of time.

The “Why Did They Reply?” Analysis

For every positive reply in the sample, ask the SDR: “Why did this prospect reply?” The answer should be specific: “Because I mentioned their recent Series B and how we helped a similar company reduce churn.” If the SDR says “I don’t know” or “they were just interested,” that is a coaching opportunity.

The “Why Didn’t They Reply?” Analysis

For every non-reply, check three things:

1. Was the subject line compelling? Track subject line open rates separately. A bad subject line kills the email before it is read.
2. Was the timing right? Weekday mid-morning is often a strong default, but timing can vary by vertical—it’s worth testing rather than assuming.
3. Was the follow-up sequence too aggressive? More than five touches in two weeks is usually counterproductive.

The Weekly Review Meeting

Direct answer: A fixed 30-minute QA review with each SDR, held on a consistent day, keeps this system running. A workable agenda:

1. List quality score (5 minutes) – Show the score and one example of a good and bad list choice.
2. Message quality score (10 minutes) – Read two emails aloud: one that scored high and one that scored low. Ask the SDR to self-critique first.
3. Reply outcome score (10 minutes) – Review one positive and one negative reply. Discuss what worked and what did not.
4. Action items (5 minutes) – One thing to start, one thing to stop, one thing to continue.

The meeting works best as data review, not judgment. The goal is to build the SDR’s own diagnostic ability.

How to Implement This System in Your Team

Here is a step-by-step walkthrough for a manager who wants to start next week.

Step 1: Define Your Scoring Rubric

Use the table above as a starting point. Adjust the thresholds to match your industry and deal size. For example, enterprise SDRs might require a higher bar for list quality (VP-level or above) than SMB SDRs.

Step 2: Set Up Your Sampling Pipeline

• Export the week’s outbound activity from your CRM (Salesforce, HubSpot, Outreach, etc.).
• Use a random number generator to select 20–30 touches per SDR.
• Over-sample from struggling segments.

Step 3: Score Each Touch

• Spend no more than 2 minutes per touch. You are looking for patterns, not perfection.
• Use a spreadsheet or a lightweight tool like Airtable to track scores over time.

Step 4: Create Exception Queues

• When you find a systemic list quality issue, pause that source immediately.
• Document the issue and the fix (e.g., “Intent data source X has a high invalid-email rate. Paused until vendor provides a clean file.”).

Step 5: Run the Weekly Review

• Schedule 30 minutes per SDR. Do not skip this even if they are hitting quota.
• Use the fixed agenda. Do not let the conversation drift into pipeline reviews or deal strategy.

Step 6: Track Trends Over Time

• After four weeks, look at the aggregate scores. Are they improving? If not, the issue is likely systemic (bad data source, bad template, bad training).
• Share the aggregate scores with the team. Transparency builds trust and accountability.

Frequently Asked Questions

How many touches should I sample per SDR per week?

20–30 is a reasonable target. Fewer than 10 and you miss patterns. More than 50 and you burn out. Stratify the sample to include first touches, follow-ups, and multi-channel touches.

What if an SDR pushes back on the scoring?

Frame it as a diagnostic, not a performance review. Say: “We are trying to understand what works and what does not. Your score is data, not a grade.” If they still resist, ask them to self-score a few touches first. They will often be harder on themselves than you would be.

Should I include call recordings in the sample?

Yes, if you have them. Call quality is harder to score, but a simplified rubric works: “Did they ask a good discovery question?” and “Did they handle an objection well?” Limit call samples to 5 per week per SDR.

How do I handle SDRs who consistently score low?

First, check if the issue is systemic (bad list source, bad template). If it is individual, increase the coaching frequency to twice a week. If there is no improvement after four weeks, consider a performance improvement plan.

What tools do you recommend for this process?

A CRM with activity logging is essential. For scoring, a simple spreadsheet works. For exception queues, most CRMs allow you to create dynamic lists or filters. Purpose-built tools for call analysis and email scoring can help, but neither is required to run this system.

How do I measure the ROI of this system?

Track reply rates, meeting booked rates, and pipeline generated per SDR before and after implementation. Teams that run this consistently tend to see fewer wasted touches (bounces, unsubscribes, wrong personas) and better reply rates within a matter of weeks—more pipeline with the same headcount.

Sources

1. Gong, “The State of Cold Outbound in 2024” – Industry benchmarks for reply rates and best practices for message personalization.
2. Lavender, “Cold Email Benchmarks Report” – Data on subject line open rates, reply rates, and optimal email length.
3. Harvard Business Review, “The Science of Strong Business Writing” (2016) – Principles of concise, persuasive writing that apply directly to SDR messaging.
4. Salesforce, “State of Sales Report” (2023) – Research on the importance of data quality and lead scoring in outbound sales.
5. U.S. Bureau of Labor Statistics, “Occupational Outlook Handbook: Sales Managers” – Context on the role and responsibilities of sales managers, including quality assurance.

The Takeaway

Direct answer: A weekly QA system that measures list quality, message quality, and reply outcomes is not busywork. It is one of the fastest ways to improve outbound performance without hiring more SDRs or buying more tools. Start with 20 touches per SDR per week, use a simple rubric, and hold a 30-minute review. Within a month, you will see the patterns. Within two months, you will see the results. The only cost is your time, and the return is a team that sends fewer, better emails to the right people.