Your First 90 Days as an SDR: What to Master in Week One, Month One, Quarter One
A ruthless prioritisation guide for new SDRs: what to master in week one, month one and quarter one, what to ignore, and how to get coached when your manager is busy.
Your onboarding portal is not a priority list
When you start as an SDR you get handed everything at once. Product certification. Competitive battlecards. A CRM training video. The security questionnaire deck. Three Slack channels. A persona doc that somebody wrote two funding rounds ago. Your manager says "just get through onboarding this week" and disappears into a forecast call.
Here is the problem. Every one of those documents was written by someone who already knows how to do the job. They are reference material for a person with context. You have no context. Reading them in week one is like being handed a car repair manual before you have ever sat in a driver's seat.
So this post is a prioritisation guide. Not a checklist of everything you could learn in your first 90 days as an SDR, but a short list of what actually moves you toward a booked meeting, plus an explicit list of what to leave alone until later. I have started businesses four times and sold inside AWS and Dell, and the pattern is always the same: the people who get good fast are the ones who narrowed early and practised the narrow thing until it was boring.
Week one: one opener, one objection response, sixty dials
Week one has exactly one job. Get you comfortable being on the phone with a stranger who does not want to speak to you. That is it. You are not trying to be good. You are trying to stop flinching.
Master one opener, word for word
Not three openers. Not a framework you adapt to the persona. One opener, memorised to the point where you can deliver it while your hands are shaking and your brain has gone blank, because both of those things will happen on the first live connect.
Something in this shape:
"Hey [Name], it's Tim calling from [Company]. I know I'm an interruption — can I have thirty seconds to tell you why I called, and you can tell me to get lost?"
Then you stop. You do not fill the silence. Whatever they say, you say your one-line reason for calling, and you ask one question.
The reason it has to be word for word is that improvisation costs working memory, and in week one you do not have any spare. Every scrap of your attention is going on the fact that a human being is on the other end of the line. If you also have to invent sentences, you will trail off, you will apologise, and you will hang up feeling like you should have gone into recruitment.
Get the exact wording from a script written for the people you are actually dialling. If you are selling into revenue leadership, the SaaS cold call script for reps dialling CROs, VPs of Sales and RevOps leaders is the artefact to internalise first — take the opener out of it, put it on a sticky note on your monitor, and read it off the note for the first hundred calls. Nobody can hear that you are reading if you have said the words enough times out loud.
Say them out loud, by the way. Out loud, standing up, before your first dial of the day. Reading a script silently is not practice. It is reading.
Master one objection response
There is one objection you will get more than any other in week one, and it is some version of "I'm not interested" or "now's not a good time". You need one response. Again, word for word.
"Totally fair, you don't know me yet. One sentence and then I'll let you go: [reason]. Worth a bad thirty seconds or should I disappear?"
That is the whole thing. You are not going to handle five objections in week one because you are not going to survive long enough in the call to hear them. You will hear the brush-off, and the brush-off comes in the first six seconds. Have an answer to the first six seconds and you have bought yourself a conversation.
When you get an objection you have no answer for — and you will, often — write the exact words down. Not a summary. The exact words the prospect used. That notepad becomes your month one curriculum.
Sixty dials a day, while you are still bad
This is the part new reps argue with, so let me be blunt about it. You should be dialling sixty times a day in week one, before you are good, before you have finished the product training, before you feel ready. Set the number, hit it, and let the quality be terrible.
The reason is not that dials are magic. It is that you cannot get feedback on a call you did not make. Every hour you spend polishing your understanding of the product is an hour producing zero data about how you sound to a stranger. Reps who wait until they feel ready spend a month feeling unready and then discover their opener does not work anyway.
The first fifteen or twenty calls will be genuinely bad. You will forget your own company name. Someone will ask a simple question and you will freeze. That is the tuition fee. Pay it in the first three days rather than spreading it across your first quarter, because your ramp clock is running either way.
One practical thing: block the dialling. Two blocks of ninety minutes, phone in hand, Slack closed, no email. Dials that happen "whenever I have a gap" do not happen. I have never once seen a rep hit a volume target on the gaps.
What to ignore in week one
Ignore the full product certification. You need one sentence about what your product does and one sentence about the problem it removes. That is all a prospect will let you say on a first call anyway. The eighty-slide deck matters when you are in a demo, and you are not in a demo.
Ignore perfect CRM hygiene. Log the outcome, log the next step, move on. Yes, your ops team will eventually want clean data, and yes, you should fix it. In week one, a rep with messy notes and sixty dials is worth ten of a rep with immaculate activity records and eleven conversations.
Ignore the competitive battlecards entirely. You will not get a competitor question in week one. If you do, "honestly, I'm new — let me find out properly and come back to you" is a completely respectable answer that prospects tend to like more than a bluffed one.
Ignore email sequences for now. Everyone's instinct in week one is to hide in email because email cannot reject you out loud. Resist it.
Month one: five objections, your own voice, and a real discovery structure
By the start of week two you have a pile of dials behind you and a notepad full of things people said that you had no answer for. Now you go from surviving to improving.
The five objections that account for most of your hang-ups
Go through your notepad. Group the brush-offs. What you will find is that almost everything you heard collapses into a handful of buckets — some version of not interested, some version of no time, some version of send me an email, some version of we already have something, and some version of we're not looking at this right now.
Your job in month one is to build a real response to each. Not a clever line. A response with a shape:
- Acknowledge it honestly, in short words.
- Say the thing they don't know that makes the objection less obviously correct.
- Ask for something smaller than what you originally wanted.
So "send me an email" becomes:
"I will, and I'll keep it short. Just so I don't send you something useless — is the way your team books meetings today mostly outbound, or is it inbound handed to reps? I'll send the relevant one."
You are not refusing to send the email. You are buying one question. One question is often enough to find out whether there is anything here at all.
Write all five out. Say all five out loud until they come without thinking. Then practise them out of order, because in a real call they arrive out of order.
Listen to your own recordings, which you will hate
This is the highest-leverage thing in month one and it is the thing nearly every rep avoids. Pull three of your own calls a week and listen to them all the way through.
It is genuinely unpleasant. Your voice sounds wrong. You will hear yourself say "just wondering if" and "sorry to bother you" and "does that make sense?" four times in ninety seconds. Good. Those are the fixes. You cannot hear your own filler while you are producing it — nobody can — so recordings are the only access you have to what the prospect actually experienced.
Listen for three specific things and ignore everything else:
Where did I talk over the pause? Silence after your opener is the prospect deciding. Most new reps kill it at the two-second mark.
Where did my voice go up at the end of a sentence? Upward inflection turns a statement into a request for permission. "I'm calling about your outbound team?" invites a no.
Where did I ask a question I did not need the answer to? Filler questions burn the goodwill you need for the one question that matters.
Pick one of the three per week. Fix that one. Trying to fix everything at once means fixing nothing.
Learn a discovery structure, not discovery questions
Around week three you will start booking meetings and, depending on how your team is set up, you may be running some of the early conversation yourself. This is where new reps fall apart, because they have a list of good questions and no idea what order to ask them in or what to do with the answers.
A list of questions produces an interrogation. A structure produces a conversation. The structure is roughly: where are they now, what does that cost them, what have they already tried, who else cares, and what happens next. Every good question you ask should be serving one of those five jobs, and you should know which job it is serving before it leaves your mouth.
The second artefact to internalise, after your opener, is a real call plan — the 25-minute discovery playbook for selling into VPs, SDR managers and CROs lays out the sequence and the timing, which matters more than the individual wording. Print it. Have it in front of you on live calls. There is no prize for doing it from memory.
Quarter one: sound like a peer, build a routine, gather evidence
Months two and three are where you stop being a new rep and start being a rep. Three things to build.
Enough patch knowledge to sound like a peer, not a vendor
Until now you have been learning your product. Now you learn their world. There is a difference between a rep who knows what their software does and a rep who knows what a Tuesday looks like for the person they are calling.
If you are calling VPs of Sales and SDR managers, you should know what pipeline coverage means and why they argue about it. You should know what happens to them when a rep misses ramp. You should know what their board asks them in a QBR and which number they are most nervous about. When you can reference that unprompted, the call changes tone — you go from being an interruption to being someone who might be worth two minutes.
The honest way to get this is not blog posts. It is talking to people. Ask your AEs what their last three deals actually turned on. Ask a customer success colleague what customers complain about after they buy. Sit in on demos with the sound on and take notes on the buyer's questions rather than the seller's answers. Dialling people who cold call for a living is its own discipline, and the sales cold call script for calling VPs of Sales and SDR managers is useful here precisely because it assumes the person picking up has heard every trick you know.
A prep routine you run without thinking
By quarter one you should have a fixed pre-call ritual that takes a small, fixed amount of time per account and never expands. Mine is: what changed recently, who reports to them, what would make this a bad week for them, and one specific sentence I can open with that no other rep could have written.
The discipline is the cap. Research expands to fill whatever time you give it, and "researching" is the most comfortable way to avoid dialling that has ever been invented. Set a timer. When it goes, you call, ready or not.
Build the same ritual for the start of the day. Mine: read the opener out loud twice, read the five objection responses out loud once, then dial. It takes a few minutes and it means call one of the day is as good as call twenty.
Evidence you can point at in a review
At the end of your first quarter someone will assess you. If you only have activity numbers, you are at the mercy of whether the meetings landed, and some of that is territory luck.
So keep a running document from month one. In it: the objections you could not handle in week one and the responses you built for them. Two recordings, one from week one and one from week twelve, so someone can hear the change. The accounts you worked that did not book but where you got further than the last rep did. The specific coaching you asked for and what you did with it.
That document does two things. It gives your manager something concrete to advocate with when they are deciding who ramps to AE. And it forces you to notice your own progress, which matters more than people admit in a job where you are told no all day.
How to get coached when your manager has no time
Most SDR managers are stretched. Waiting for a formal coaching cadence to appear is a way to burn your first quarter.
The fix is to make coaching cheap for them to give. Do not ask "can you listen to my calls?" — that is an open-ended request for an hour. Ask "can you listen to ninety seconds from 4:20 in this call, where I lost her after the brush-off, and tell me what you would have said?" A specific, timestamped, bounded question gets answered on a phone between meetings. A vague one gets a "yeah, let's find time" that never arrives.
Build peer coaching too. Find one other rep, ideally someone six months ahead of you, and trade calls once a week. Fifteen minutes each. You will learn as much from critiquing their calls as from hearing critique of yours, because it is far easier to hear a mistake in someone else's voice than in your own.
And steal shamelessly. Ask your best rep to send you a recording of a call they are proud of, and then ask them what they nearly said instead. The near-misses are where the real technique lives.
What I would do on Monday
If I were starting as an SDR next week, my whole plan would fit on an index card. Memorise one opener. Memorise one brush-off response. Sixty dials a day from day one. Write down the exact words of every objection I cannot handle. Build five responses by the end of month one. Listen to three of my own calls a week and fix one habit at a time. Learn a discovery structure before I learn discovery questions. Cap my research. Keep an evidence doc.
The hard part is not knowing that. It is the reps. You need the words in your mouth before the live call, not after, and the gap between reading a script and being able to say it under pressure is only crossed by saying it out loud, badly, many times. That is the specific problem we built DrillCall for — practising the opener and the five objections against a voice that pushes back, so your first hundred reps happen somewhere that does not cost you a real account. If your first quarter is going to include a few hundred bad calls either way, I would rather have most of them in a drill than in the pipeline.