Outsourced SDR: What to Expect in the First 90 Days (2026)

Outsourced SDR: What to Expect in the First 90 Days (2026)

Last updated: October 2026

The first 90 days determine whether your outsourced SDR engagement produces pipeline or churns silently. Here is what a good phone-led one looks like week by week.

Most failed outsourced SDR programmes I get called in to review did not fail in Month 6. They failed in the first few weeks and nobody noticed until the quarter-end pipeline review. The kickoff was rushed, the script never got signed off, the list was full of switchboard numbers, and by Week 6 the SDRs were dialling the wrong people with an opener nobody had tested. The account manager kept sending optimistic weekly updates. The pipeline never showed up.

I am Jamie Partridge, founder of UpliftSales. We run phone-only outsourced SDR programmes, delivered by Australian-based SDRs, for B2B technology companies across Australia. This guide is the week-by-week playbook I wish every buyer had before they signed the contract, what should happen, what you should be doing in parallel, and the red flags that mean the programme is off track well before pipeline goes missing. It complements our outsourced SDR buyer's guide and the Day 90 numbers you should hold your provider to.

Australian buyers deserve special mention. Because our market is smaller, list-burn risk is higher, and a badly-run first month of calling can genuinely close off segments of the Sydney and Melbourne tech buyer universe for months. Discipline in the first 90 days is not optional.

---

The 90-day timeline at a glance

Before we go section by section, here is the full arc for a healthy engagement:

Week	Phase	What happens	What you should see
1	Kickoff and build	ICP alignment, messaging and script workshop, list build, dialer and CRM setup	Signed script, ICP written, first list loaded, calls logging to CRM
2-3	First dials, first meetings	Calling goes live, early conversation data, script tuning	First conversations logged, first meetings booked
4-8	Volume builds	List expansion, AE feedback loop, opener and objection iteration	A steady weekly flow of booked meetings
9-13	Consistent pipeline	Weekly booked rate stabilises, reporting cadence embedded	5-10 meetings per week, monthly business review

This is what a well-run phone programme looks like. Anything that promises a flood of meetings in week one is usually burning a warm list. Anything materially slower is a problem you need to name in writing.

---

Week 1: Kickoff and build

What happens: the agency loads context, aligns on ICP, writes the call script, builds the first list, and sets up the dialer. No calls go to real prospects yet.

The single biggest predictor of programme performance is the quality of the Week 1 kickoff. If the agency turns up with a generic slide template and starts talking about their process, that is a bad sign. A good kickoff is 80% questions from them, 20% answers from you.

What data you must share

Come to Week 1 with these documents ready. If you do not have them, the agency should help you build them, but delaying data handover pushes the first dials out by a week for every week it slips.

• ICP definition. Firmographic (industry, size, revenue, geo) and technographic (tech stack, tooling, integrations) filters.
• Buyer personas. Titles, seniority, day-to-day pain points, buying triggers.
• Case studies. Three to five recent wins with named customers, use case, and outcome.
• Positioning and messaging docs. How you describe the product, what competitors you displace, what you don't do.
• Pricing bands. So the agency can filter out prospects who cannot afford you.
• CRM access. Read/write access with a defined SDR role, custom fields for source and campaign, and mapped stages.
• Calendar access. Round-robin or dedicated AE calendar for booking.
• Historical pipeline data. Won-lost analysis, average sales cycle, average contract value.

Our provider selection walkthrough covers the buyer-side setup in more depth.

ICP alignment session

The ICP session is not a rubber-stamp of what you sent through. A competent agency will push back on ICP that is too broad, ask for evidence behind each filter (why 100-500 employees, why this vertical), and often narrow it. In our engagements this session typically produces a tighter ICP than what the client walked in with, because we can see what has actually converted historically versus what the client hoped would convert.

Australian ICP work has an extra dimension: TAM (total addressable market) inside Australia is often smaller than founders assume. If your ICP filters produce fewer than 2,000 target accounts in-country, you either need to widen the ICP, expand to NZ, or accept that outbound will hit ICP exhaustion in 6-9 months. Better to name that in Week 1.

Messaging and script workshop

The messaging workshop is where most agencies fall over. A good one produces a written call script (signed off by you before calling starts) covering:

• Three primary pain points ranked by persona
• The specific trigger events that make each pain acute
• Positioning against the two or three most common status-quo alternatives
• Proof points (case studies, metrics, named customers) mapped to each pain
• Two or three cold call openers per persona, plus a short voicemail script
• Objection responses for the top five objections

If your agency wants to start dialling without this document existing, stop. Calls without a signed script are just guesses. Our cold calling scripts show the shape a good one takes.

UpliftSales runs a structured Week 1 workshop for every engagement. If your last SDR programme skipped this step and quietly underperformed, book a scoping call and we will show you the artefact you should have received.

List build and dialer setup

By the end of Week 1 the agency should have:

• Built the first target list against the agreed ICP, with direct dials and mobiles verified rather than switchboard numbers
• Configured the dialer with local Australian caller ID
• Connected the dialer to your CRM so every dial, conversation and disposition is logged automatically
• Tested the booking flow end to end

---

Week 1-2: CRM and booking flow

What happens: the CRM integration goes live and the calendar-to-CRM flow is tested before the first meeting is booked.

CRM integration

Before the first dial, the CRM integration should be live and tested. That means:

• SDR user role created with appropriate permissions
• Lead source, campaign, and call disposition captured as fields
• Two-way sync between the dialer and the CRM (HubSpot, Salesforce, Pipedrive)
• Meeting-booked and meeting-held stages mapped
• Notification flow to the AE when a meeting is booked

Our SDR playbook has more detail on how the operating rhythm fits together.

Meeting-booking flow

Run through the booking flow yourself as if you were a prospect: accept a calendar invite, check the confirmation and reminder, and check that the meeting shows up correctly in the AE calendar and CRM with all the context from the call attached.

This is where I see silly problems every week, calendar timezone bugs, invites with no context so the AE walks in cold, reminders that never send. Fix them in Week 1, not Week 6.

---

Week 2-3: First dials, first meetings

What happens: calling goes live, the first conversations come in, and the first meetings are booked. The script gets tuned against real conversations.

Week 2 is the emotional turning point of the engagement. The phones start ringing. Most calls go to voicemail, some conversations are short "not now"s, and a few are the start of a real meeting. This is all normal.

Volume

A dedicated SDR should reach a steady daily dial volume from the first week of calling rather than ramping over a month. A phone programme has no sending domains to protect, so the constraint is list quality and script quality, not volume.

First conversation data

By the end of Week 3 you should be able to see:

• Connect rate by list source and time of day
• Conversations per day per SDR
• Conversation-to-meeting rate by persona and opener
• The first booked meetings, with notes from the call attached in the CRM

If connect rates are very low, stop and fix the data before pushing more dials. Every dial into a switchboard is wasted. Our full guide to SDR metrics breaks down what each number is telling you.

Script iteration

The first two weeks of calling produce enough data to make one meaningful script iteration. Not five. One good iteration beats five noisy ones. The agency should propose a specific change (usually to the opener, the reason for the call, or the close), you sign off, and the new version runs for another week before the next iteration.

Common early changes:

• A shorter opener that gets to the reason for the call faster
• A more specific pain reference for each persona
• A clearer close that asks for a specific time rather than "a quick chat"
• A sharper response to the most common objection

If the agency proposes "let's rewrite the whole script" in Week 3, push back. That is panic, not analysis.

---

Week 4-8: Volume builds

What happens: booked meetings become a weekly flow, AE feedback comes back on quality, and the script and list get refined against the AE signal.

What to expect by Week 8

By the end of Week 8 a healthy programme should be producing a steady weekly flow of booked meetings for a mid-market B2B tech ICP. The rate depends on ICP size, ACV, and how tight the targeting is. Enterprise programmes with $150k+ AUD ACV and a 500-account TAM sit at the lower end.

Bridge Group's SDR ramp research on internal SDRs shows most reps take 3-5 months to reach full productivity, and outsourced programmes should hit steady state faster because the playbook, data sources and dialer exist from Day 1. If you are past Week 6 with almost nothing booked and held, that is a structural problem, not a ramp issue.

AE feedback loop on meeting quality

The most important input to Week 4-8 optimisation is the AE feedback loop. After every meeting the AE should fill in a short form covering:

• Was the meeting worth taking? (yes/no)
• Was the contact the right person or role?
• What was the pain that got them to say yes?
• Were they aware of the product before the call?
• Would you rate this a 1-5?

The agency uses this signal to refine ICP filters and the script. Meetings that AEs consistently rate 1-2 are a signal to tighten qualification on the call. Meetings that AEs rate 4-5 tell you what the winning pattern looks like, the agency should be reverse-engineering that pattern into the script and the list.

If your agency is not asking for this data, they cannot improve the programme. That is a Week 6 red flag.

A weekly AE-agency sync is non-negotiable in Weeks 4-12. If your provider is not running one, they are flying blind on quality. Our SDR agency team builds this cadence into every engagement from the start.

Script and list optimisation

Weeks 4-8 is where the script should evolve from "what the agency wrote in Week 1" to "what actually works for your ICP". Expect two or three material iterations across this window. If the metrics are not moving at all across four weeks, either the iterations are not real changes, or the underlying setup is broken and needs a rebuild rather than a tune.

---

Week 9-13: Consistent pipeline

What happens: the programme reaches steady state and the reporting rhythm embeds. This is where you either sign the extension or start looking for a replacement.

The programme is producing predictably

By Week 12 a healthy programme is producing:

• Booked meetings: 5-10 per week (varies by ICP and volume)
• Held meetings: 75-85% of booked
• AE-qualified SQLs: 30-50% of held meetings
• Pipeline generated: dependent on ACV, but expect $150k-$500k AUD per month in new pipeline for a mid-market programme

For a full benchmark table by ICP and stage, see our detailed benchmark breakdown. For a full pipeline-to-payback model, see the payback and ROI model.

Reporting rhythm

By Week 12 you should have three reporting cadences running:

1. Weekly written update. Sent every Monday for the prior week. Includes activity (dials, connects, conversations), meetings booked and held, what changed in the script, and what is planned this week.
2. Weekly 30-minute sync. AE, agency account manager, and sales leader. Reviews the week, discusses meeting quality, agrees any changes.
3. Monthly business review. 60-90 minutes with the founder or CRO. Broader trend view, pipeline attribution, next month's plan.

If any of these are missing at Week 12, your engagement is under-managed by the agency.

Iteration priorities

At steady state the iteration cycle shifts from "get it working" to "make it better". The three highest-leverage areas at Week 12 onwards:

• ICP expansion or refinement based on the winning patterns from Weeks 4-8
• Opener and objection testing on the most-used parts of the script
• Call timing, which days and hours connect best for each persona

---

What the buyer (you) needs to do at each stage

The number one reason outsourced SDR programmes underperform is not the agency. It is the buyer treating the engagement as fully hands-off. It is not. Here is what you own.

Stage	Buyer accountability
Week 1	Attend kickoff, hand over ICP/personas/case studies, grant CRM and calendar access, sign off the call script
Week 2-3	Name your AE point of contact, take the first meetings promptly, give fast feedback on early conversations
Week 4-8	AE completes meeting-quality form after every meeting, join weekly sync, sign off on script changes
Week 9-13	Attend monthly business review, discuss ICP expansion or narrowing, plan next quarter's targets

If you cannot commit an AE to fill in the meeting-quality form and attend a weekly 30-minute sync, the programme will underperform its potential. That is not the agency's fault.

---

Red flags at each milestone

Here is what to watch for at each of the three main checkpoints. If you see two or more red flags at any milestone, request a written recovery plan from the agency within 5 business days.

Milestone	Red flag	What it usually means
Week 3	No signed call script	Agency skipped discovery, calls will be generic
Week 3	No calls logged in your CRM	Attribution will be broken from Day 1
Week 3	No meetings booked or close to booked	Targeting, data quality, or the opener is off
Week 6	Very low connect rates	The list is full of switchboard or stale numbers
Week 6	No AE feedback loop running	Agency cannot optimise for meeting quality
Week 12	No monthly business review scheduled	Engagement is under-managed by agency
Week 12	Meetings inconsistent week to week	Volume or targeting is not stable enough for reliable output
Week 12	Same script as Week 2	No iteration has happened, programme is on autopilot

Any Week 6 red flag on its own is manageable. Two or more together, or any single red flag persisting into Week 8, warrants a serious conversation about whether the engagement should continue.

---

How to fix a stalled ramp: 4 diagnostic questions

If you are at Week 6 and the programme is under-producing, work through these four questions in order. In our experience, one of them almost always identifies the fix.

1. Is the data reaching the right people?

Check connect rate by list source. If one source connects far worse than the others, it is full of switchboards, stale numbers or wrong contacts. Ask the agency to pull it, re-verify the numbers, and prioritise direct dials and mobiles.

2. Is targeting right?

Pull a random sample of 50 contacts dialled in the last two weeks. Do they all fit the ICP? Are the titles right? Are the companies actually in-market for what you sell? If more than 20% of the sample looks off, the enrichment source or the ICP filters are broken and no script tweak will fix it.

3. Is the script landing?

Look at what prospects actually say, not just the conversion rate. If conversations end with "not relevant" or "wrong person", targeting is off. If they end with "not right now" or "no budget", the script is landing but timing is wrong (schedule a call-back). If prospects hang up inside the first 20 seconds, the opener is not earning the right to continue, rewrite it.

4. Is the dial volume sufficient?

Sanity check the maths. Take your connect rate and your conversation-to-meeting rate and work backwards from the meetings you want each week. If the dial volume cannot get you there at realistic conversion rates, you need more dials, better data, or a sharper script. Use our outbound activity calculator to model the numbers.

---

What "success" looks like at Day 90

Here is the Day 90 scorecard for a healthy outsourced SDR engagement. If you are hitting most of these, extend the contract. If you are missing more than three, have a serious diagnostic conversation.

Metric	Day 90 target (mid-market B2B tech, AU)
Booked meetings per week	5-10
Held meetings per week	4-8
SQLs per month	8-18
Pipeline generated per month	$150k-$500k AUD
Cost per meeting held	$400-$900 AUD
Cost per SQL	$1,200-$2,500 AUD

Salesforce's State of Sales report puts industry-wide sales team ramp cycles in a similar range. See our full benchmarks table for the breakdown by ICP, ACV, and industry vertical.

Typical vs slow ramp, here is the shape of the two curves side by side:

Metric	Typical ramp	Slow ramp
First meeting booked	Week 2-3	Week 6+
Steady-state weekly booked	Week 12	Week 20+ or never
Weeks to first closed-won	16-24	30+ or never

A slow ramp is not always a failed ramp, some enterprise motions with $250k+ AUD ACV genuinely need longer. But name it up-front so nobody is surprised in Month 3.

Want to benchmark your current programme against these numbers? Our team runs a free 30-minute diagnostic against your last 90 days of SDR data. Book a scoping call or explore our outsourced SDR service to see how we structure engagements.

---

Frequently Asked Questions

What happens in the first 30 days of outsourced SDR?

The first week is onboarding: an ICP alignment session, a messaging and script workshop, list building, dialer and caller ID setup, and CRM integration. Calling starts in week two. On a well-run phone programme the first meetings are booked in weeks two to three, and by day 30 you should have real conversation data showing which openers, personas and call times are working. There are no sending domains to warm up on a phone-only programme, so there is no reason for a month of silence.

When do you get first meetings from an outsourced SDR?

On a well-run phone programme, first meetings land in weeks two to three. Volume then builds as the list, scripts and call timing are tuned, and by the end of Week 12 the programme should be producing at a predictable weekly rate. If you are past Week 6 with almost nothing booked and held, something is structurally wrong with targeting, data quality, or messaging.

How long does outsourced SDR onboarding take?

About a week before calling starts. Onboarding covers discovery, ICP alignment, the first target list, call scripts and objection responses, dialer and local caller ID setup, CRM integration, and the calendar and qualification flow. Calling starts in week two at a steady volume, and the script and list are refined weekly from there.

What is a normal outsourced SDR ramp curve?

Week one is setup with no dials. Calling starts in week two, the first meetings are booked in weeks two to three, volume builds through weeks four to eight as scripts and lists are tuned, and a healthy mid-market programme reaches 5 to 10 meetings per week by Week 12. A good agency reaches steady state faster than an internal hire because it already owns the playbook, the data sources and the dialer.

Whose responsibility is the calling setup, the agency or the client?

The agency should own it end to end: sourcing and verifying phone data, configuring the dialer with local Australian caller ID, logging every call to your CRM, and writing and maintaining the scripts. Your job is to sign off the messaging, give CRM and calendar access, and name the AE who takes the meetings.

What data do I need to hand over to an outsourced SDR provider?

Hand over your ICP, personas, pipeline data, three to five case studies, positioning docs, pricing bands, CRM access, and calendar access. If you do not have written ICP or messaging docs, the agency should build them with you in Week 1. The messaging and script workshop is the single most important input to programme performance, and delaying it pushes the first dials out week for week.

What are the red flags at Week 3 of outsourced SDR onboarding?

Watch for five things at Week 3. No signed-off call script, no calls made yet, no calls logged in your CRM, no meetings booked or close to booked, and no weekly written update from the account manager. Any of these signals that the programme is behind. Push for a written recovery plan immediately rather than waiting to see if it corrects itself.

How do I fix a stalled outsourced SDR ramp?

Work through four diagnostic questions in order. Is the data reaching the right people, is targeting right, is the script landing, and is the dial volume sufficient? Fixing any one usually unblocks the others. Do not panic-fire the agency in Week 6, most ramps recover within one iteration cycle if the underlying setup is sound and the diagnosis is honest.

---

Summary

The first 90 days of a phone-led outsourced SDR engagement are about disciplined onboarding that produces a predictable pipeline engine by Week 12. Week 1 is discovery, scripts, list build and dialer setup. Weeks 2-3 are the first dials and the first booked meetings. Weeks 4-8 are volume building and quality feedback. Weeks 9-13 are steady state and the reporting rhythm that will run for the life of the engagement.

The buyer owns real work at every stage, ICP handover, script sign-off, meeting-quality feedback, and the weekly sync attendance. The provider owns data, calling, iteration, and reporting cadence. When both sides do their job, Day 90 shows 5-10 meetings per week and $150k-$500k AUD per month in new pipeline. When either side skips steps, the engagement quietly fails.

The single biggest predictor of success is a Week 1 kickoff that produces a signed call script and a clean, verified first list. Get those two right and the rest is iteration. Get either wrong and you will still be arguing about pipeline in Month 6.

---

Related reading: our outsourced SDR buyer's guide, Day 90 benchmarks by ICP, and ROI framework. If you want to see what a well-run first 90 days looks like in practice, talk to our outsourced SDR team.