# SDR productivity benchmarks: quality and capacity > SDR productivity comparisons should distinguish booked, held and accepted meetings while accounting for ramp and the reachable account universe. Review definitions, sampling choices and common comparison errors. Source: https://saas-marketing.net/research/sdr-productivity-benchmarks/ Topic: SaaS Sales Type: research Published: 2026-09-17 Last updated: 2026-09-17 Publisher: SaaS Marketing (saas-marketing.net) License: CC BY 4.0. Quote or republish with attribution and a link to https://saas-marketing.net/research/sdr-productivity-benchmarks/ ## Short answer SDR productivity comparisons should distinguish booked, held and accepted meetings while accounting for ramp and the reachable account universe. ## Key takeaways - Track effort, held meetings, accepted opportunities and cost with consistent role definitions. Include manager and tool costs where the comparison requires them. - A high meeting count can reward poor-fit bookings that consume sales capacity without producing useful pipeline. - Keep source dates, population definitions and limitations beside any numerical claim. - This is a measurement and source-evaluation guide. It does not present an original customer survey or an industry-wide target. --- Use this guide with the [saas sales hub](/saas-sales/). The goal is a defensible comparison: a result whose definition and limitations another person can understand. ## Define the comparison SDR productivity comparisons should distinguish booked, held and accepted meetings while accounting for ramp and the reachable account universe. | Dimension | What to record | | --- | --- | | Inbound or outbound role | State the exact scope for your data and for the external comparison. | | Ramp status | State the exact scope for your data and for the external comparison. | | Territory | State the exact scope for your data and for the external comparison. | | Acceptance criteria | State the exact scope for your data and for the external comparison. | | Support resources | State the exact scope for your data and for the external comparison. | A useful benchmark answers a specific management question. Write that question before collecting numbers. A figure can be accurate for its source population and still be inappropriate for your company's segment or decision. ## Measure it consistently Track effort, held meetings, accepted opportunities and cost with consistent role definitions. Include manager and tool costs where the comparison requires them. Keep the underlying counts and dates, not only a final percentage or ratio. If a record is incomplete, distinguish unknown from zero. Record changes to definitions so a later trend does not silently combine incompatible periods. ## Avoid the main interpretation trap A high meeting count can reward poor-fit bookings that consume sales capacity without producing useful pipeline. Separate observation from explanation. The report may show that two things moved together; that does not identify which caused the other. List plausible alternative explanations and the additional evidence required to choose between them. ## Build an evidence register | Field | Required entry | | --- | --- | | Decision | The action this evidence could change | | Source | Original publisher and exact URL | | Dates | Publication date and underlying collection window | | Population | Who or what was included and excluded | | Definition | Numerator, denominator, unit and treatment of edge cases | | Method | Survey, product records, experiment, estimate or forecast | | Limitation | The reason the comparison may not transfer | | Owner | Person responsible for verification and the next review | Use the [benchmark evaluation worksheet](/resources/) to keep these fields with the proposed claim. Do not replace a missing method or sample description with assumptions based on the publisher's reputation. ## Turn the evidence into a decision Compare your own consistent historical cohorts first, then use external evidence to identify questions worth investigating. If the external population differs materially, state the difference instead of forcing the number into a target. Record the proposed action, its uncertainty and the next review date. - [Choosing a SaaS sales model by ACV](/guides/saas-sales-models-by-acv/) - [Self serve sales and when to add humans](/guides/self-serve-saas-sales/) - [Inside sales for mid market SaaS](/guides/inside-sales-for-saas/) - [The enterprise SaaS sales process](/guides/enterprise-saas-sales-process/) - [SaaS selling strategies that move deals](/guides/saas-selling-strategies/) The [metrics library](/saas-metrics/) explains related definitions, and the [calculators](/calculators/) can help check the arithmetic of a scenario. {/* expanded-practice-2026-09 */} ## Apply sdr productivity benchmarks: quality and capacity in a working review Build a source record before drawing a comparison. Capture the original publisher, collection period, sample, metric definition and relevant exclusions. Separate reported observations from forecasts and your own planning assumptions. If two sources use different populations or denominators, explain the difference instead of averaging them into a single number. For this topic, involve the sales owner and the buyer’s relevant decision participants and work from discovery notes, stage evidence and the next agreed action. The relevant unit is one qualified opportunity with a current buying process. State the question the review should resolve before choosing a chart, an asset or a tool. If participants disagree about the unit or scope, resolve that disagreement before combining their evidence. ### Evidence to prepare Use buyer evidence to define progression. A completed seller task, such as a proposal or presentation, is not the same as a buyer commitment. Preserve the customer’s actual question and unresolved dependencies so follow-up can help rather than repeat the pitch. | Review field | What to record | | --- | --- | | Topic | SDR productivity benchmarks: quality and capacity | | Decision | The specific action this explanation should help you choose | | Working evidence | discovery notes, stage evidence and the next agreed action | | Unit and scope | one qualified opportunity with a current buying process | | Responsible people | sales owner and the buyer’s relevant decision participants | | Remaining uncertainty | The missing fact that could change the decision | ### Two situations that can change the interpretation #### When a proposal omits implementation ownership A contract for software access does not automatically resolve data preparation, training or integration responsibilities. Use this check: List customer and vendor responsibilities, prerequisites, acceptance criteria and support boundaries. Do not create delivery commitments without the responsible team's agreement. The [focused diagnostic guide](/guides/sales-proposal-has-no-implementation-owner/) provides the correction process and a working evidence sheet. #### When follow-up adds no new value A verified migration answer is more useful than another generic message asking whether the prospect saw the proposal. Use this check: Identify the last agreed question or dependency and the evidence needed next. Respect communication preferences and avoid escalating pressure after silence. The [focused diagnostic guide](/guides/sales-follow-up-repeats-the-pitch/) provides the correction process and a working evidence sheet. ### Record the decision and the limit An opportunity with a named technical review and an agreed next meeting is different from one with a favorable comment and no decision path. Both can remain in the CRM, but forecasting and follow-up should reflect the evidence actually available. Keep the conclusion beside the evidence that supports it. Record what the team will do, who owns the next action and which event or date will trigger a review. If the underlying definition, audience or product behavior changes, revisit the conclusion rather than assuming the old result still applies. A clear limit is useful information; it tells the next reader where additional investigation is required. Use the [complete topic collection](/topics/saas-sales/) for related methods and the [category field guides](/industries/) when the product's buying situation or implementation requirements change how the method should be applied. ## Frequently asked questions ### Does this page report an original industry study? No. It explains how to evaluate evidence and measure the topic. It does not claim a proprietary survey, a sampled customer panel or an industry-wide benchmark that has not been collected. ### What needs to match before comparing results? Check inbound or outbound role, ramp status, territory, acceptance criteria, support resources. Differences in these fields can change the interpretation even when the reported metric has the same name. ### What is the main comparison error? A high meeting count can reward poor-fit bookings that consume sales capacity without producing useful pipeline. ### How should I record a source? Save the original URL, publisher, publication and collection dates, population, metric definition and relevant table or passage. Label an estimate as an estimate and retain the source limitations.