How long it takes to get an SDR team onto a dialer

SDR productivity15 April 2026Benjamin Foraison

The calling screen isn't the problem. What takes the two weeks is fitting the tool into your CRM, your statuses and your sequences.

The question that comes up before signing is often about ramp-up: how long before the SDRs are comfortable? That’s rarely where things get stuck.

For an SDR who has done cold calling before, the calling screen is not the problem. What really fills the first two weeks is fitting the tool into what you already do: your CRM, your statuses, your running sequences, and the person who decides what gets written back. That part can’t be standardized.

The calling screen is not the problem

Open a list, start a session, talk to someone, qualify, move on to the next one. There’s nothing complicated about the calling screen, and SDRs don’t ask many questions about it.

Ubic calls up to 3 prospects at the same time. Voicemails, faxes and invalid numbers are filtered out before they reach the SDR: what shows up on screen is someone who picked up.

What takes some adjusting is physical. Conversations come one after another, without the dead time that used to serve as a breather between two calls, and SDRs tell us a session is more tiring than a classic day of calling. The adjustment happens fast, but it’s not immediate. The volume of real conversations runs from 6 to 25+ per SDR per day, depending on the list and the industry.

What takes time: fitting into your processes

A dialer writes into your CRM. That’s the whole point, and it’s also what calls for decisions many teams have never made.

The topics that come up at every start:

Which tool is the source of truth: the CRM, or the sequencing tool your SDRs already spend their days in?
Which statuses already exist, and which ones a call is allowed to write.
Who owns the lead after a call. The SDR who had the conversation, or the AE the meeting was handed to?
How calls fit with the email and LinkedIn sequences already running. Does a called prospect leave their sequence, or is the call just one step among others?

None of these questions is technical. They get settled in a meeting, with the people who have authority over the CRM.

Decide what should sync before you connect anything

This is the only real piece of advice here. Connecting a CRM takes a few minutes: the 15 native integrations are there for that, and the sync works both ways. The conversation that should come before that connection takes longer.

What has to be settled first: does every call attempt sync, or only conversations? Do you write an activity, a status on the lead, or both? Does the full transcript go into the CRM, or only the notes summary? And in the other direction, what comes back down: a lead disqualified on the CRM side has to leave the calling lists, otherwise your SDRs call back prospects who have already been handled.

A team that connects first and decides later ends up with a CRM full of unanswered attempts nobody will ever read. The cleanup then happens by hand, lead by lead. We’ve written elsewhere about why the CRM ends up no longer reflecting outbound activity: it often starts there.

Week 1

Day 1. Import a list, set the cadence, run a first short session. The goal is to call on day one, even on an imperfect list. That’s what surfaces the real questions.

Days 2 and 3. One hour with the person who owns the CRM, without the SDRs. You write down in black and white what trace a call should leave. Meanwhile, the SDRs keep calling: the tool works perfectly well before the CRM is connected, calls are transcribed, and recorded if you’ve turned the feature on.

Days 4 and 5. You connect the integration, then you open the CRM and look at what got written on about ten real calls. There will be surprises. That’s normal, this is the moment to see them.

A customer wrote to us that “in the space of just 4 days, Ubic helped us generate 6 meetings.” That happens when the team calls from day one instead of waiting for everything to be configured.

Week 2

The second week is mostly for fixing what the first one showed.

This is often when you realize a status is missing. “Wrong contact” and “not interested” don’t mean the same thing, and if both fall into the same bucket, your end-of-month reporting will tell you nothing.

It’s also the week when you set the progressive pause list by list: after how long a prospect who didn’t pick up becomes callable again, and what happens at the end of the cycle. Exit with a status synced to the CRM, switch to an SMS or a voicemail message, it depends on what you do with the rest.

That leaves how it all fits with what’s already in place. If your SDRs already work in a sequencing tool, the second week is for naming who decides, and at what moment. Both options are defensible, as long as the decision is made once for the whole team.

Where the timeline slips

This timeline holds when the CRM is well kept and someone has the power to decide. That’s not always the case.

If your statuses already mean nothing, the dialer won’t change that. That work has to happen first, and it has nothing to do with the tool.

In larger organizations, the mapping often waits on RevOps, who has ten other priorities and an approval process to follow. That’s where the timeline slips most often. Give them a heads-up at the start rather than at the moment you need them.

At the other end, the advice doesn’t really apply to a founder prospecting alone, or to a two-person team without a structured CRM. There, call first and deal with the mapping when there’s something to map.

The test after two weeks

One test only: can a manager open the CRM and understand what happened without asking the SDRs. If the answer is no, go back to the mapping before adding lists.

One practical note if you’re comparing tools right now: the free trial lasts 7 days. That’s enough to judge the calling side, not to finish the CRM hookup. If you want to test both, start the mapping during the trial instead of saving it for after you sign.

Frequently asked questions

How long does it take an SDR to be autonomous on the dialer?

The calling screen is understood quickly. It’s the pace that takes some adjusting: it happens fast, but it’s not immediate. An SDR who has done cold calling before doesn’t need long training. Onboarding and support are in French, so questions get handled as they come.

Do you need a RevOps to connect the CRM?

No, the integration connects without any technical skills. What you do need is someone with authority over the CRM’s statuses and fields. In a small team that’s the Head of Sales, in a bigger one it’s RevOps.

We already use Lemlist or Salesloft, do we have to stop everything?

No. These tools are part of the integrations, and many teams keep their email sequences in place. The only decision to make is whether the call counts as a step in the sequence or as a parallel channel, and then stick to it.

Can you start without a CRM?

Yes, calls work without one. You lose the historical trail and cross-referenced reporting, which becomes a problem once the team grows past two or three SDRs. For a test of a few days, it doesn’t matter at all.