Should an SDR quota count calls or conversations?

The question almost always arrives as a number: how many calls a day, how many meetings a month. That’s rarely where the subject is decided.

What you decide to count shapes what your team does with its day, well before the level where you set the bar.

The quota in dialed calls

It’s the one you run into most often, because it’s the easiest to pull out of a CRM. 80 calls a day, 100 calls a day. The number exists and it can be read at the end of the week.

If the counter tracks dialed calls, that’s the counter the SDR will push up.

That produces behaviors nobody asked for. They dial first the numbers that push the counter up fast, the ones that rarely get answered. A conversation that drags without going anywhere becomes a cost, so they cut it short. And when fifteen calls are missing at 5 pm, they always find fifteen numbers to call.

The quota in conversations

It’s the right unit on paper. A conversation is what produces a meeting, and therefore pipeline.

Except what an SDR actually holds is their attempts and the quality of what they say. The number of conversations they get also depends on the list, which they usually didn’t choose: how fresh the numbers are, the share of direct mobile numbers.

On a good list, the target gets hit without forcing. Take an eighteen-month-old list already worked twice: the same SDR with the same talk track won’t get there, and they’ll see it by the start of the week. A target you don’t control ends up demotivating, and the manager loses their lever too: the person can do everything right and still miss.

There’s a prerequisite, too. Do you count a conversation from ten seconds, where the prospect says they’re not interested, or from thirty? As long as that threshold isn’t written down, the number will move on its own. We go through these definitions in an honest conversion rate in cold calling.

A target on one side, a commitment on the other

The framing that seems to hold, to us, puts two things of a different nature on the same sheet.

A conversations target, weekly or monthly. That’s the result.

Facing it, the person commits to session time actually spent on the phone, two or three hours a day depending on the role, since that’s what they control.

The difference matters in the Monday check-in. An SDR who held their calling blocks and missed their conversations target has a list problem or a time-slot problem, and it’s not theirs to fix. The reverse happens too: the conversations are there while the blocks were never held, the sign of a good list that won’t repeat the following month. You don’t treat those two situations the same way.

Session time has to come out of the tool, not out of a declaration. Four hours blocked in a calendar don’t make four hours on the phone: we broke down the math in how an SDR’s time really gets spent. While you’re at it, check what your reports call a connected call. If voicemails are filed in there, your conversation time is skewed, and so is the quota you build on it.

Where to set the bar

What we can give is what we see come through on our side: 600,000+ calls, 50,000+ connected calls and 30,000+ real conversations, with 1,200+ meetings booked behind them. In practice, an SDR can reach 50 conversations a day on a parallel dialer. We haven’t isolated the causes of that spread; list quality and the calling slot are the two variables we see move the most.

So measure your own range before setting anything.

We also publish a 15% conversation rate over the last 30 days. There again, everything depends on the definition behind it, and that’s true of every rate in circulation, ours included.

An SDR starting out, an SDR settled in

An SDR in week 3 and an SDR in month 14 sometimes end up with the same quota.

In the first weeks, a conversations target doesn’t mean much. The conversations will come: the question is what they do with them. What you track at that point is session time and the number of calls reviewed in debrief.

Write the ramp in advance, over eight to twelve weeks, with one step per month. The SDR knows where they should be in week 4 and in week 8, and nobody renegotiates the number every Monday. Above all, it avoids the “you’re still not there” two months in, when nothing can be caught up anymore.

This reasoning assumes a team of several SDRs and some history. For a founder prospecting on their own two mornings a week, a quota is useless: there are slots to hold and a number of meetings to get.

When the list degrades mid-quarter

It happens. An enrichment source that deteriorates, a segment already called twice. The number of conversations per day drops without anyone changing the way they work.

The reflex reaction is often to change nothing, on the grounds that the quarter is underway. The team figures out fast enough that the target is out of reach, stops trying before the period ends, and the quarter is lost.

The other option is to separate what belongs to the list from what belongs to execution. Session time is still owed, the conversations target gets reset against the actual list. The drop is written down somewhere, with its cause. That’s also what will give you the argument next quarter, when you’ll have to defend a data budget.

To see the degradation coming, track the pick-up rate list by list, week after week. It degrades upstream of the number of meetings in the funnel, which leaves you room to react.

Where to start

If your quota is expressed today in dialed calls, don’t replace it overnight at the start of a quarter. For three weeks, pull the number of conversations and the actual session time per SDR without touching the published targets. You’ll see right away who dials a lot for few conversations.

Only then, put down the two numbers, with the definition of a conversation written on the same page as the quota.

Frequently asked questions

How many calls a day should you ask of an SDR?

None, if you can avoid it. Ask for session time on the phone and a number of conversations. Call volume is a consequence of those two, and it varies with the day’s list anyway.

Should variable pay be indexed on conversations?

Careful. Variable pay holds up better on meetings held and pipeline generated, because those are the only numbers the rest of the company recognizes. Conversations and session time are for weekly steering and check-ins, which is already a lot.

What about an SDR who gets their conversations but doesn’t book meetings?

The subject is somewhere other than the quota. Listen to five of their recordings with them and watch where the exchange comes off the rails; the breaking point is often the same from one call to the next. That’s where the work is.

A monthly or quarterly quota?

Monthly for conversations and session time, because they can be corrected quickly. Quarterly for meetings and pipeline, because one slow month doesn’t say much and a sales cycle takes longer to show.