TL;DR: Hours are an output, not an input, so stop picking a percentage and back the number out of the quota. The Bridge Group’s 2025 SDR research, 10th edition, 351 B2B companies, puts the median SDR at 112 total activities a day (44 phone, 41 email, 19 LinkedIn, 8 text or other) producing 4.1 quality conversations, with phone-centric teams at 56 dials and 4.6 quality conversations and email-centric teams at 28 dials and 3.4. That is roughly 12 dials per quality conversation on a phone-led team and about 27 activities per conversation across all channels, which is the ratio that actually sets the hours. The same study puts the median monthly quota at 10 held meetings, down 40% since 2018, with 60% of SDRs at quota, the lowest in the study’s history, average ramp at 3.0 months and average tenure at 1.9 years. Work it backward from meetings to conversations, conversations to attempts, attempts to minutes, then compare that to the day you actually have, because Salesforce’s 2026 State of Sales (4,050 sellers, 22 countries, fieldwork August to September 2025) reports the average seller spends 40% of their time selling and Gen Z reps just 35%. A “spend 40% of your week prospecting” target is not a prospecting target at all, it is the entire selling budget. Protect the block, but protect it for the right reason. The controlled study usually cited for this, Mark, Gudith and Klocke at CHI 2008, found interrupted subjects finished faster (20.31 and 20.60 minutes versus 22.77 uninterrupted) with no drop in quality, and paid for it in significantly higher stress, frustration, time pressure and effort after only 20 minutes. Interruptions do not steal the hour. They burn the rep inside it. Measure attempts per conversation, conversations per held meeting, and show rate by segment, then change the ratio before you change the schedule.
Someone on your team asked how much time SDRs should spend prospecting, and they wanted an hour count. You probably answered with a percentage. Most of page one agrees with you, and the number is almost always thirty to forty percent of the week.
Here is the problem. Where did that number come from? Nobody who gives it can tell you, and it does not move when your connect rate halves, when your list quality drops, or when half the team’s outbound numbers start getting labeled as spam by the carriers. A target that never responds to the conditions that produced it is not a target, it is a slogan with a number attached, and the first rep who misses it will work out that nothing on their side caused the miss. That is how you lose the floor.
The hours are downstream. So what do you owe the rep instead? A chain: this many held meetings requires this many quality conversations, which requires this many attempts, which takes this many focused minutes at your current ratios. Build that chain once and the hours fall out of it, and the number updates itself every time one of the inputs moves. That is the whole method.
Why the Percentage Answer on SDR Prospecting Time Breaks
A percentage target assumes the rest of the day is a constant. It is not. What does forty percent of a week even mean on a team whose meeting load changed last quarter?
Think for a second about what a percentage actually tells a rep on a Tuesday morning. It tells them how to slice a day whose size they do not control, against a quota whose difficulty they also do not control, using a ratio nobody on the team has measured since the list changed. If the team’s attempts-per-conversation ratio doubles because a carrier started flagging the outbound numbers, the percentage stays at forty and the pipeline falls through the floor. The rep did exactly what you asked. So who failed there? Nobody did. The number was measuring the wrong thing.
There is a second failure that is harder to see. Teams that count hours start optimizing for hours. A rep who hits the block target by firing low-effort emails into a list nobody validated is fully compliant and completely useless. No dashboard built on time or activity counts can tell that rep apart from the one who spent the identical block on twelve researched calls into accounts that actually fit. That is not a rep problem, it is a measurement that chose the wrong unit and then held people to it for a quarter.
So throw out the percentage and ask a better question. What has to be true, in attempts, for this rep to hit quota? And does the day actually contain room for it?
Back Into SDR Prospecting Time From the Quota
Start at the only number the business actually cares about and walk backward. How many meetings have to happen?
The Bridge Group’s 2025 SDR Models, Motions and Metrics report, the 10th round of that research across 351 B2B companies, puts the global median monthly quota at 10 held meetings at Stage 0 and 6 converted opportunities at Stage 1. The held-meeting median is down 40% since 2018. Spread across a typical month of working days, ten held meetings works out to roughly one every other day, which is the point at which most managers decide the quota is reasonable. That sounds easy right up until you price it in conversations, which is where most prospecting-time arguments quietly fall apart.
The same study puts the median SDR at 4.1 quality conversations a day. Run a month of those against a ten-meeting quota and you land somewhere near nine quality conversations for every meeting that actually happens. Be careful with that figure. The 4.1 and the 10 are separate medians across different companies, not a paired ratio inside one team, so treat the result as an order of magnitude rather than a benchmark. Your own CRM has the real version of this number. When did anyone last pull it?
Now the chain is usable, and the steps are boring on purpose. Pick the quota. Divide by your own conversation-to-meeting rate to get required conversations. Divide by your own attempts-per-conversation rate to get required attempts. Then multiply by the minutes an attempt honestly takes on your team, counting the research in front of it and the logging behind it rather than only the seconds the phone is ringing. That product is your prospecting time. It is a derived quantity, which means it is supposed to move whenever the list, the segment, or the number reputation moves underneath it. It is not a policy you set in January and defend in June.
One more thing the quota math exposes. Bridge Group reports 60% of SDRs at quota, the lowest reported in the study’s history, alongside average ramp of 3.0 months and average tenure of 1.9 years. If most of your team is under quota and most of your team is under two years in seat, is another hour on the block really the intervention? It is not. The ratio is.
The Dial to Conversation Ratio Decides the Prospecting Hours
This is the number that does the real work, and almost nobody tracks it, which is why so many teams end up arguing about hours instead.

Bridge Group breaks the median day into 112 total activities: 44 phone, 41 email, 19 LinkedIn, and 8 text or other, against 4.1 quality conversations. Across all channels that is about 27 activities per conversation. Split by motion it gets sharper. Phone-centric teams average 56 dials and 4.6 quality conversations, which is roughly 12 dials per conversation. Email-centric teams average 28 dials and 3.4 conversations. The study also notes the 4.1 figure is the first rebound in its history, so the direction is finally up.
Sit with twelve dials per conversation for a second. What does a two-hour block buy at that rate? Not two hours of talking. It buys you a handful of conversations and a lot of ringing, voicemail, and wrong numbers. So which lever has the most torque here? Not the length of the block. The denominator.
Three things move that denominator, and every one of them is operational rather than motivational, which matters because the usual response to a bad ratio is a speech about activity. List quality decides how many of those numbers are even correct and still attached to the person you think you are calling. Timing decides whether you are dialing into the hours when your particular buyer is at a desk rather than in back-to-back meetings. Number reputation decides whether the call shows up as a name or as “Spam Risk,” and a labeled number turns good dials into dead ones without anybody on the team doing a single thing wrong.
That is where tooling belongs in this conversation, and nowhere earlier. Show the process first. Kixie’s PowerDialer advances a list so a rep is not clicking and pasting between every attempt, Voicemail Drop leaves a recorded message without the rep sitting through the greeting, and ConnectionBoost combines local presence dialing, progressive caller ID, and reputation management to help increase pickup rates and reduce spam flags on outbound calls. None of that is a strategy. Does it change the ratio, and does it leave the outcome in the CRM where a manager can inspect it? That is the only test that matters when you are deciding whether a tool earned its seat on the floor.
What Is Left of the SDR Day After Everything Else
Now check your derived number against reality. How big is the day, actually?

Salesforce’s 2026 State of Sales, published 3 February 2026 from 4,050 sales professionals across 22 countries with fieldwork run from August to September 2025, reports that the average seller spends 40% of their time selling. Gen Z reps report just 35%. Everything else is the work nobody puts on a schedule, which is to say data entry, pipeline hygiene, internal meetings, tool switching, and the slow hunt for the right contact record on an account somebody already touched twice.
Read that against the standard advice and the advice falls apart. “Spend thirty to forty percent of your week prospecting” is not asking for a share of the week. It is asking for the entire selling budget, with nothing left for qualification calls, handoff coordination, or follow-up on the conversations prospecting already produced. No wonder the target feels impossible to the people carrying it, because it was never costed against the day they actually have.
So do the subtraction in the open. Take the eight hours. Remove the standing meetings, the ramp and coaching time, the CRM work that genuinely has to happen, and the inbound obligations the rep cannot refuse. What is left is the real ceiling. What if the derived requirement is larger than the ceiling? Then you have a quota problem or a ratio problem, and no amount of calendar discipline is going to close that gap. Say that out loud to the team before they conclude they are the reason.
Protect the Prospecting Block or Pay for It in Effort
Everyone tells you to protect the block. Most of them cite the wrong study, and the right one is considerably more interesting than the version that gets repeated.
The controlled experiment usually invoked here is Mark, Gudith and Klocke, “The Cost of Interrupted Work: More Speed and Stress,” published at CHI 2008. Forty-eight subjects worked a simulated office task while being interrupted by telephone or instant message every two minutes. The result surprised the authors. Slower, right? No. Interrupted subjects finished faster: 20.31 minutes with same-context interruptions and 20.60 with different-context interruptions, against 22.77 minutes with no interruptions at all, and there was no significant difference in quality. People compensate by working faster, which is exactly what a rep does when a manager keeps pinging the block.
So where did the cost go? The paper reports significantly higher stress, frustration, time pressure and effort in both interruption conditions, and puts it plainly: “After only 20 minutes of interrupted performance people reported significantly higher stress, frustration, workload, effort, and pressure.” Note the honest limits before anyone carries this into a QBR deck. It is a lab study, 48 subjects, 81% university students with a mean age of 26, working an email task rather than a call block, so do not treat the minutes as transferable to your floor.
The implication still transfers, and it reframes the whole argument. Interruptions are not stealing minutes out of the block. They are converting the block into a more expensive version of itself, paid for in the rep rather than in the clock. Your rep still makes the dials and still finishes the list. They just finish it drained, and the thing that degrades is the twentieth conversation of the day, not the clock. That is a retention and quality argument, not a productivity one, and on a team with 1.9 years of average tenure it is the argument that should move you.
So the practical rule is narrower than “protect the block.” Protect it from context switches specifically, and stop measuring whether the rep completed the block. Start measuring what the last hour of it sounded like.
Set SDR Prospecting Time by Role
The chain is the same for everyone. The inputs are not, so the derived hours should not be either.
Outbound SDR prospecting time
Outbound carries the largest derived requirement by a wide margin, because every single conversation has to be manufactured out of a cold record that gave you no signal and owes you nothing. These reps need the longest uninterrupted windows and the most defensible list, and their attempts-per-conversation ratio is the one most exposed to data decay and number reputation.
Is more block the answer here? Usually not. If the list is wrong, a second block scales the wrong work and demoralizes the rep twice as fast, because now they have two hours of evidence that calling does not work instead of one. Check the denominator before you extend the numerator.
Inbound SDR prospecting time
Inbound reps are working a different constraint. Their scarce resource is response latency rather than attempt volume, which means a rigid outbound block that parks a hand-raised lead for ninety minutes destroys more pipeline than the block creates.
Give them a smaller protected block aimed at the work inbound leaves behind, which means the leads that went quiet, the old inquiries worth a second pass, and the gaps that open when campaign volume drops. Then measure them on speed to first conversation and on qualification accuracy rather than on dials.
Hybrid SDR prospecting time
Hybrid is where prospecting time quietly disappears. Every inbound notification carries an implicit claim on the rep’s attention, and nobody ever wrote down which of those claims are real and which are just noise with a badge on it.
Fix that with a written interrupt rule, not with willpower. Define exactly which inbound events are allowed to break a block, who covers the rest during that window, and what the rep does with everything else when the block ends. Without that document in writing, the block is decorative and everyone on the floor already knows it.
Prospecting time for new SDRs
A new rep’s ratio is worse, their research is slower, and their call confidence is thinner. With average ramp at 3.0 months, expecting the median activity count in week two produces rushed research and bad attempts that teach the rep the wrong lesson about calling.
Ramp the derived number along with the skill. Start with fewer attempts and a hard requirement on call review, then raise the activity target only when the conversation rate shows the rep can hold it without cutting corners on research. The goal in month one is one repeatable attempt the rep can run without thinking, not a full block of activity that looks right in the report.
What to Inspect Before Changing SDR Prospecting Time
Before you move anyone’s calendar, pull five numbers out of your own system. You probably already have four of them.
- Attempts per quality conversation, by rep and by segment, over the last full month.
- Quality conversations per held meeting, and the show rate on the meetings that get booked.
- Median time from assignment to first attempt on inbound leads, with the outliers listed separately.
- The share of dials that connect to a live person, split by the outbound number used.
- Minutes per attempt including research and logging, measured on a sample rather than estimated.
Two of those are diagnostic rather than reportable, so keep them off the leaderboard and out of the weekly email. Attempts per conversation and minutes per attempt exist to tell you which lever to pull. A rep with high attempts and a bad ratio almost always has a list, timing, or outbound number problem rather than a skill problem. A rep with a good ratio and too few attempts has a capacity problem or a call hesitancy problem, and those two get coached very differently. Same low meeting count, opposite fix. Which one are you looking at?
When to Move the SDR Prospecting Time Target
Treat the number as a standing calculation, not a policy. Recompute it when an input moves.
- Connect rate drops in a segment or on a specific set of outbound numbers.
- Meeting volume holds but show rate or acceptance falls, which means the conversations are getting thinner.
- Reps start spending real time correcting contact data, which is an attempt cost hiding inside the block.
- Inbound volume grows enough to break the hybrid interrupt rule you wrote.
- A new segment needs materially more research per account than the one you sized against.
- A top performer is running a different sequence and beating the ratio, which is a process to copy rather than an anomaly to admire.
Change one variable at a time where you can. Move territories, messaging, the schedule, and the qualification bar in the same month and you will get a result with no idea which change produced it. The quarter bought you a number instead of a lesson. Then you run the whole thing again.
SDR Prospecting Time FAQs
How many hours a day should an SDR prospect
There is no fixed answer to how much time SDRs should spend prospecting that survives contact with a different team. Derive it: take the meeting quota, divide by your conversation-to-meeting rate, divide by your attempts-per-conversation rate, then multiply by the honest minutes an attempt takes including research and logging. Compare the result to the hours actually left after meetings, admin, and inbound obligations. If the requirement exceeds the ceiling, fix the ratio or the quota, not the calendar.
Should research and CRM work count inside prospecting time
Count them in the cost of an attempt, but track them as their own line. If research and logging are folded invisibly into one prospecting number, a rep can show a full block and almost no conversations, and nothing in the report will tell you why. Separating them is also how you find out whether a data problem is quietly eating a third of the block.
Is thirty to forty percent of the week a reasonable prospecting target
It is a reasonable upper bound to sanity-check against, and a poor target to manage to. Salesforce’s 2026 State of Sales puts the average seller at 40% of their time selling in total, so a forty percent prospecting target leaves nothing for qualification, follow-up, or handoffs. Use it as a ceiling, then derive the real figure from quota and ratios.
Should inbound and outbound SDRs have the same prospecting time target
No, and forcing it is how hybrid teams lose both motions. Outbound is constrained by attempt volume and list quality, inbound by response latency. The derivation is identical for both. The inputs are different, so the answer should be too.
What is the fastest way to improve SDR prospecting output without adding hours
Attack attempts per conversation. Validate the list, fix the outbound number reputation, dial in the windows when your buyers actually answer, and remove the manual steps between attempts. Each of those lowers the denominator, which means the same block produces more conversations. Adding an hour to a broken ratio just produces more ringing.
How much time SDRs should spend prospecting has a short honest answer, and it is a method rather than a number. Pick the quota, derive the attempts, cost them in minutes, and compare that against the day the rep actually has after meetings, admin, and inbound obligations are subtracted. Do the two reconcile? If not, you have found something more useful than a prospecting target.
Sources
How this article was built: every external figure comes from the publishing organization’s own current page or paper, read directly on the review date and linked below, with the load-bearing wording quoted rather than paraphrased so its scope travels with it. Where this article does arithmetic on published medians, such as dials per quality conversation or conversations per held meeting, the arithmetic is labeled as arithmetic in the body and the inputs are separate medians across different companies rather than a paired ratio inside any one team, so those derived figures are illustrative and are not benchmarks. The inspection list, the interrupt rule, the role splits, and the recompute triggers are operating recommendations from this article, not findings from any cited source. No Kixie performance figure, pickup rate, or time saving is cited anywhere in this article. Kixie publishes this article and sells sales engagement software for business calling and texting.
- SDR Models, Motions & Metrics: 2025 Research Report, The Bridge Group, primary research publisher, 10th edition, 351 B2B companies, published 6 February 2025, for the global median monthly quota of “10” held meetings at Stage 0 described as “↓ 40% since 2018” and “6” converted opportunities at Stage 1; for “Median total daily activities: 112 (44 phone, 41 email, 19 LinkedIn, 8 text/other)”; for “Quality Conversations: 4.1 QCs/day” described as the “First rebound in study history”; for “Phone-centric teams average 56 dials and 4.6 QCs per day vs. email-centric teams at 28 dials and 3.4 QCs”; for the “Share of SDRs at quota: 60%” described as “Lowest reported in study history”; for “Average ramp time: 3.0 mo”; and for “Average SDR tenure: 1.9 yrs”.
- Salesforce Announces State of Sales Report for 2026, Salesforce, primary publisher announcement for its own research, published 3 February 2026, for “the average seller spends 40% of their time selling”, for Gen Z sellers at “just 35%”, and for the study basis of “4,050 sales professionals” across 22 countries with fieldwork run “August through September 2025”.
- The Cost of Interrupted Work: More Speed and Stress, Gloria Mark, Daniela Gudith and Ulrich Klocke, CHI 2008, the authors’ own copy hosted at the University of California, Irvine, for the finding that “people completed interrupted tasks in less time with no difference in quality” while “experiencing more stress, higher frustration, time pressure and effort”; for the reported task times of 22.77 minutes at baseline against 20.31 minutes with same-context interruption and 20.60 minutes with different-context interruption; for the design of 48 subjects interrupted by telephone or instant message at a two-minute frequency; for the sample being “81% … German university students with a mean age of 26”; and for the conclusion that “After only 20 minutes of interrupted performance people reported significantly higher stress, frustration, workload, effort, and pressure.” Cited for the direction of the effect and its named cost, not as a transferable measurement of a sales call block.
- ConnectionBoost, Kixie, the vendor’s own current product page, cited only for the present-tense description of what the feature is, that “ConnectionBoost combines local presence dialing, progressive caller ID, and reputation management to help increase pickup rates and reduce spam flags on outbound calls.” No performance claim from that page is carried into this article.
Sources verified and content reviewed by the Kixie Research Team on October 5, 2026. All source links checked on October 5, 2026.
Ready to close more deals with Kixie?
See how Kixie's AI-powered tools can transform your sales and support operations.
Start Free Trial