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

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

Last updated: July 2026

The first 90 days determine whether your outsourced SDR engagement produces pipeline or churns silently. Here is what a good 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 four weeks and nobody noticed until the quarter-end pipeline review. The kickoff was rushed, the messaging document never got signed off, the sending domains were never warmed properly, and by Week 8 the programme was pushing volume through cold infrastructure into inboxes that were spam-filtering everything. The account manager kept sending optimistic weekly updates. The pipeline never showed up.

I am Jamie Partridge, founder of UpliftSales. We run outsourced SDR programmes 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 broader Australia hub 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 30 days 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-2	Kickoff and discovery	ICP alignment, messaging workshop, data handover, domain purchase	Signed messaging doc, ICP written, kickoff notes shared
2-4	Infrastructure and warming	DNS/DKIM/DMARC, mailbox setup, warming, CRM integration	Warming dashboard, CRM sync live, calendar booking flow tested
4-6	First sequences live	Low-volume launch, initial reply data, sequence tuning	First 200-500 contacts sent, opens above 40%, first replies
6-10	Meetings start landing	Volume ramp, AE feedback loop, message iteration	5-15 meetings booked by end of Week 8
10-13	Consistent pipeline	Weekly booked rate stabilises, reporting cadence embedded	5-10 meetings per week, monthly business review

This is what a well-run programme looks like. Anything materially faster is usually shortcut-driven and will backfire. Anything materially slower is a problem you need to name in writing.

---

Week 1-2: Kickoff and discovery

What happens: the agency loads context, aligns on ICP, drafts messaging, and buys the sending infrastructure. No emails go out 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 launch 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 buyer-side prep walkthrough covers this 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 workshop

The messaging workshop is where most agencies fall over. A good one produces a written messaging document (signed off by you before Week 3) 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
• 5-8 first-touch email variants across cold email, LinkedIn, and cold call opener
• Objection responses for the top five objections

If your agency wants to launch sequences in Week 3 without this document existing, stop. Sequences without a signed messaging doc are just guesses.

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.

Domain and mailbox setup

By end of Week 2 the agency should have:

• Purchased 2-4 look-alike sending domains (never your primary domain)
• Set up 6-12 mailboxes across those domains (Google Workspace or Microsoft 365)
• Configured SPF, DKIM, and DMARC records correctly
• Started domain warming (typically Instantly, Smartlead, or Warmy for 14-21 days)

If they are proposing to send from your primary domain, that is a hard veto. It puts your transactional and customer email at risk for zero upside. Our deep-dive on cold outreach deliverability covers why this matters.

---

Week 2-4: Infrastructure and warming

What happens: DNS setup completes, warming ramps, CRM integration goes live, and the calendar-to-CRM flow is tested end to end.

This is the phase where impatient founders panic. "We're four weeks in and nothing has gone out. Are they even working?" Yes — they are doing the work that determines whether Week 8 produces pipeline or nothing. Rushing this phase is the single most common cause of programme failure.

DNS, DKIM, DMARC setup

Google and Yahoo tightened bulk sender requirements in February 2024. Every sender pushing more than 5,000 emails per day to Gmail addresses must now authenticate with SPF, DKIM, and DMARC, and stay under a 0.3% spam complaint rate. Enterprise inbox providers have followed suit. The full Google Workspace bulk sender guidelines are worth reading if you are doing this in-house, but for an outsourced programme the agency should own it.

Verify that they have:

• SPF records set with the correct include for the sending platform
• DKIM signing configured on each sending domain
• DMARC records at policy p=none initially (moving to p=quarantine later once volume stabilises)
• MX records for reply catching
• BIMI where the brand qualifies (nice to have, not critical)

Ask for a screenshot of each domain's DNS panel. If the agency cannot produce it, they are not managing infrastructure properly.

Domain warming ramp

Warming is the process of gradually building sender reputation on each domain and mailbox before real cold outreach starts. In 2026, credible warming takes 14-21 days minimum. Common warming tools (Instantly, Smartlead, Warmy, Mailreach) simulate legitimate email conversations across a network of seed inboxes, so mailbox providers see the domains sending and receiving human-like email.

Volume ramp during warming should follow a curve like:

Warming week	Emails per mailbox per day	Notes
Days 1-3	5-10	Seed conversations only
Days 4-7	15-25	Mixed inbox placement checks
Days 8-14	30-50	Real content templates seeded in
Days 15-21	50-80	Approaching production volume
Day 21+	80-100	Steady state for cold outreach

Anyone launching cold sequences at 40+ emails per mailbox per day inside two weeks of buying the domain is asking to be spam-filtered by Week 5. Slow warming is not the agency being slow — it is them protecting the programme.

CRM integration

By end of Week 3, the CRM integration should be live and tested. That means:

• SDR user role created with appropriate permissions
• Lead source, campaign, and sequence step captured as custom fields
• Two-way sync between the outreach tool (Salesloft, Outreach, Smartlead, Instantly) and CRM (HubSpot, Salesforce, Pipedrive)
• Meeting-booked and meeting-held stages mapped
• Notification flow to AE when a meeting is booked

Our operational stack walkthrough has more detail on how the tooling fits together.

Meeting-booking flow

The last piece to test before sequences go live is the booking-to-meeting flow. Run through it yourself as if you were a prospect: click the calendar link in a test email, book a slot, complete the qualification form, receive the confirmation and reminder emails, and check that the meeting shows up correctly in the AE calendar and CRM with all context attached.

This is where I see silly problems every week — qualification form fields that don't map to CRM, calendar timezone bugs, reminder emails going to spam, no context in the calendar invite so the AE walks in cold. Fix them in Week 3, not Week 8.

---

Week 4-6: First sequences live

What happens: low-volume production sequences launch, first reply data comes in, messaging gets iterated based on real signal.

Week 4 is the emotional turning point of the engagement. Emails finally start going out. Reply notifications start pinging. Some are positive, most are neutral or negative, and a few are the classic "please remove me" or "how did you get my email". This is all normal.

Volume ramp

Production volume should ramp cautiously over Weeks 4-6:

• Week 4: 200-500 emails sent per week, 100-200 LinkedIn touches
• Week 5: 500-1,200 emails per week, 300-500 LinkedIn touches, dials start
• Week 6: 1,500-3,000 emails per week, full multichannel cadence live

Ramping too fast burns the newly-warmed domains. Ramping too slowly starves the programme of signal to iterate against. A good agency lands in the middle.

First reply rates

By end of Week 5 you should see:

• Open rate: 40-55% across the sequence (below 30% signals deliverability trouble)
• Reply rate: 3-8% (below 1.5% signals a messaging or targeting problem)
• Positive reply rate: 15-25% of replies (the rest are opt-outs, wrong contacts, or negative)
• Meeting-booked rate: roughly 15-30% of positive replies

If open rates are below 30% at Week 5, stop and diagnose deliverability before pushing more volume. Every additional send with degraded deliverability makes the recovery harder. Our full guide to funnel metrics breaks down what each number is telling you.

Sequence iteration

The first two weeks of live sending produce enough data to make one meaningful sequence iteration. Not five. One good iteration beats five noisy ones. The agency should propose a specific change (usually to subject line, opener, or CTA), you sign off, and the new variant runs for another week before the next iteration.

Common Week 5 changes:

• Shorter subject lines (2-4 words often beats 6-8 in 2026)
• More specific pain reference in the opener
• CTA reduced from "15 min call" to "worth exchanging notes"
• Third-touch that reframes the problem rather than following up

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

---

Week 6-10: Meetings start landing

What happens: the first booked meetings appear, AE feedback comes back on quality, and messaging gets refined against the AE signal.

What to expect at Week 8

By end of Week 8 a healthy programme should have produced 5-15 booked meetings for a mid-market B2B tech ICP. The range is wide because it depends on ICP size, ACV, and how tight the targeting is. Enterprise programmes with $150k+ AUD ACV and 500-account TAM often sit at 5-8 meetings by Week 8. SMB programmes with broad ICPs can hit 15-25.

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 infrastructure and playbook exist from Day 1. If you are past Week 10 with fewer than 5 meetings, that is a structural problem, not a ramp issue.

AE feedback loop on meeting quality

The most important input to Week 6-10 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 outreach?
• Would you rate this a 1-5?

The agency uses this signal to refine ICP filters and messaging. Meetings that AEs consistently rate 1-2 are a signal to tighten qualification at the SDR stage. Meetings that AEs rate 4-5 tell you what the winning pattern looks like — the agency should be reverse-engineering that pattern into the sequences.

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

A weekly AE-agency sync is non-negotiable in Weeks 6-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.

Sequence optimisation

Weeks 6-10 is where the sequence should evolve from "what the agency wrote in Week 3" to "what actually works for your ICP". Expect two or three material iterations across this window, each producing a 20-40% lift in the relevant metric. 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 10-13: Consistent pipeline

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

The engine 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 (emails, dials, LinkedIn), funnel metrics (opens, replies, meetings), what changed in the sequence, 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 6-10
• Sequence A/B testing on the most-used templates
• Channel mix optimisation — more or less LinkedIn, more or less phone, more or less video

---

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-2	Attend kickoff, hand over ICP/personas/case studies, grant CRM and calendar access, sign off messaging doc
Week 2-4	Approve sending domains, review qualification form, test booking flow, name your AE point of contact
Week 4-6	Review first sequence performance in weekly sync, sign off on iteration changes, flag any deliverability concerns
Week 6-10	AE completes meeting-quality form after every meeting, join weekly sync, provide fast turnaround on message tweaks
Week 10-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. Our provider selection walkthrough covers what the ideal buyer-side setup looks like.

---

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 4	No signed messaging doc	Agency skipped discovery — sequences will be generic
Week 4	No domain warming started	Launch will slip by 2+ weeks or deliverability will suffer
Week 4	No CRM integration mapped	Attribution will be broken from Day 1
Week 8	Fewer than 5 meetings booked	Structural issue with targeting, deliverability, or messaging
Week 8	Open rates below 30%	Deliverability is degraded — likely warming was too fast
Week 8	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 sequence as Week 4	No iteration has happened — programme is on autopilot

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

---

How to fix a stalled ramp — 4 diagnostic questions

If you are at Week 8 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 deliverability working?

Check open rates by sending domain and mailbox. If any domain is below 30%, it is compromised. Ask the agency to pause that domain, run a fresh warm-up, and check DNS/DKIM/DMARC records. Also check spam placement using tools like GlockApps or Mailreach — if inbox placement is below 60%, you have a deliverability problem that pushing more volume will make worse. HubSpot's research on email deliverability is a good primer if you want to go deeper.

2. Is targeting right?

Pull a random sample of 50 contacts from the last two weeks of sequences. 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 messaging tweak will fix it.

3. Is messaging landing?

Look at reply content, not just reply rate. If replies are mostly "not relevant" or "wrong person", targeting is off. If replies are mostly "not right now" or "no budget", messaging is landing but timing is wrong (add a nurture sequence). If replies are silent (opens without replies), the message is not compelling — rewrite the opener and CTA.

4. Is volume sufficient?

Sanity check the maths. If you are sending 800 emails per week at a 3% reply rate and a 20% positive-reply rate and a 30% booked-from-positive rate, that is 1.5 meetings per week. If you want 5 meetings per week, you need roughly 2,700 emails per week or dramatically better conversion at each stage. LinkedIn's Sales Solutions blog publishes activity benchmarks that are worth cross-referencing. 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
Open rate	40-55%
Reply rate	3-8%
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 6-7	Week 10+
First meeting held	Week 7-8	Week 12+
Steady-state weekly booked	Week 12	Week 20+ or never
Weeks to first SQL	8-10	14+
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 30 days are onboarding and infrastructure, not meetings. Expect an ICP alignment session, a messaging workshop, DNS and DKIM setup, domain warming, CRM integration, and the first live sequences going out around Week 4. Any provider promising booked meetings inside 30 days is either using pre-warmed shared infrastructure that will burn your deliverability, or has cut corners on setup that will hurt you later.

When do you get first meetings from an outsourced SDR?

First meetings typically land between Week 6 and Week 8 in a well-run programme. By the end of Week 8 you should see between 5 and 15 booked meetings depending on ICP, ACV, and channel mix. By the end of Week 12 the engine should be producing at a predictable weekly rate.

How long does outsourced SDR onboarding take?

Structured onboarding runs 4 to 6 weeks before sequences go live at full volume. The first two weeks cover discovery, ICP alignment, and messaging. Weeks 2 to 4 handle DNS, DKIM, DMARC, domain warming, CRM integration, and the calendar and qualification flow. Sequences launch at low volume in Week 4 and ramp through Week 6.

What is a normal outsourced SDR ramp curve?

A normal ramp follows 0 meetings in weeks 1 to 4, 1 to 3 meetings in weeks 5 to 6, 3 to 8 meetings per week by weeks 7 to 8, and 5 to 10 meetings per week by Week 12. This mirrors the internal SDR ramp curve documented by Bridge Group, though a good agency reaches steady state faster because they own the infrastructure and playbook.

Whose responsibility is domain warming — the agency or the client?

The agency should own domain warming end to end. That means the agency buys the sending domains (typically look-alikes of your primary domain), sets up DNS, DKIM, DMARC, configures inbox providers, and runs warming tools for 14 to 21 days before real send volume. You keep your primary domain clean.

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

Hand over your ICP definition, buyer personas, current pipeline data if available, three to five recent case studies, positioning documents, competitor comparisons, pricing bands, sales collateral, CRM access with a defined SDR role, and calendar access for booking. If you do not have written ICP or messaging docs, the agency should build them with you in Week 1.

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

At Week 4 the red flags are: no domain warming started, no messaging document signed off, no CRM integration mapped, no test sequences sent, and no weekly written update from the account manager. Any of these signals that the programme will miss its Week 6 launch and Week 8 first-meetings milestone.

How do I fix a stalled outsourced SDR ramp?

Start with four diagnostic questions: is deliverability working (open rates above 40%), is targeting right (is the ICP tight and enriched properly), is messaging landing (are replies happening), and is the volume sufficient. Fixing any one usually unblocks the others. Do not panic-fire the agency in Week 8 — most ramps recover within one iteration cycle if the underlying setup is sound.

---

Summary

The first 90 days of an outsourced SDR engagement is not about meetings booked in Week 2. It is about disciplined onboarding that produces a predictable pipeline engine by Week 12. Weeks 1-2 are discovery and messaging. Weeks 2-4 are infrastructure and warming. Weeks 4-6 are first sequences and initial iteration. Weeks 6-10 are meetings landing and quality feedback. Weeks 10-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, messaging sign-off, meeting-quality feedback, and the weekly sync attendance. The provider owns infrastructure, sequencing, 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 messaging document and a Week 4 infrastructure milestone with warming complete and CRM live. 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 Australia hub 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.