The first 90 days for a new in-house SDR after an agency handoff
What a new in-house SDR should do in the first 90 days after an agency handoff, with a phase by phase plan, real ramp data and where it stalls.
ON THIS PAGE · 8 SECTIONS
THE SHORT VERSION
- The first 90 days for a new in-house SDR after an agency handoff split into three phases: absorb the inherited system in days 1 to 30, run it with support in days 31 to 60 and own the number from day 61 on.
- The Bridge Group found in 2025 that the average SDR takes 3.0 months to reach full productivity, the lowest figure on record, so a 90 day plan is realistic but leaves little room to waste.
- Gallup found in 2018 that only 12% of employees strongly agree their company does a great job onboarding new hires, which is exactly why a written plan beats a verbal one for a handoff this complex.
- A handoff ramp is not a cold start. The new hire inherits reply history, a tested offer and a do not contact list. Week one should be spent reading that before sending anything new.
- The plan breaks down fastest when the inherited data arrives as a dashboard instead of a document nobody can query, so the new hire rebuilds weeks of context by hand.
The first 90 days for a new in-house SDR after an agency handoff are three phases, not a single sprint to quota. Days 1 to 30 are for absorbing what the agency already proved: the reply history, the accounts already contacted and the offers that tested well. Days 31 to 60 are for running that system with a manager watching closely. Days 61 to 90 are for owning the full number alone, on infrastructure and a playbook built before the hire started.
This article assumes the handoff itself already happened. If domains, CRM records and reply history have not been secured yet, read the handoff checklist for moving outbound in-house first, since a messy handoff makes every day of this plan harder. What follows is what the new hire and whoever manages them should actually do once the agency has stopped sending and the inbox belongs to someone new.
Why a handoff ramp is not a normal 30-60-90 plan
A generic 30-60-90 day plan assumes a cold start: no accounts touched, no message tested, no data to trust. A handoff ramp starts somewhere in the middle of a story that already has a plot. The new hire's advantage is real data on what worked, who already replied and who should never be emailed again. The risk is treating that data as noise instead of the head start it is and rebuilding from scratch anyway because nobody explained what it means.
Whether the hire moved an outbound function in-house because deal size grew or because the agency relationship soured, covered in in-house SDRs versus outsourcing, the ramp math does not change. The Bridge Group's 2025 research puts average SDR ramp time at 3.0 months, the lowest figure the firm has recorded since it started tracking the metric in 2010. A 90 day plan lines up with that average almost exactly, which means there is very little slack for wasted weeks.
Source: The Bridge Group, 2025 and Gallup, 2018.
Days 1 to 30: absorb what already works
- Read the reply history before sending anything. Every account that already replied, every one that opted out and every one mid-conversation needs to be visible before the first new email goes out. Otherwise the first week ends with a prospect getting pitched twice.
- Learn the tested offers and the accounts they ran against. The agency already found which pitch landed with which segment. That is a head start worth weeks, not a historical curiosity to skim once.
- Shadow the deliverability and domain setup. Confirm which domains are warmed, which are new and what the sending limits actually are, so the first campaign does not overload infrastructure nobody has watched in a week.
- Set up the reporting cadence early. Decide what gets reviewed weekly before the first full week of sending, using the outbound KPI scorecard as the starting list rather than inventing one from scratch.
- Send at reduced volume, on purpose. The goal of the first 30 days is proving the inherited system still works under new ownership, not hitting a volume target. A smaller, carefully watched batch beats a full send that breaks something nobody notices until week three.
Days 31 to 60: run it with support
By day 31, the new hire should be sending at a meaningful volume with a manager reviewing output weekly rather than daily. This is the phase where the inherited playbook gets tested against new judgment instead of followed by rote. Replies get classified using the same categories the agency used, covered in reply classification for B2B sales, so the data stays comparable to what came before. The first independent wins, a meeting booked without the agency's playbook being read line by line, usually land somewhere in this window.
This is also when deliverability needs a second look. A domain that performed fine under an agency's daily monitoring can slip once oversight moves to someone learning the system. Build a short weekly check into the routine: bounce rate, spam complaints and open rate by domain, not just replies.
Days 61 to 90: own the number
By day 61, the training wheels come off. The new hire owns the account list, writes or edits the next message test and runs the weekly report without a manager drafting it first. Pipeline from this phase is the first real signal of whether the hire, not the inherited system, is working. If meetings booked in days 61 to 90 come mostly from accounts the agency had already warmed up, that is expected. If no new accounts have been added to the list by day 90, that is a sign the hire is coasting on inherited momentum instead of building the next 90 days of pipeline.
Inherited pipeline proves the system works. New pipeline proves the hire does.
The plan at a glance
| Phase | Focus | What done looks like |
|---|---|---|
| Days 1 to 30 | Absorb the inherited reply history, offers and infrastructure | Sending at reduced volume with zero duplicate contacts |
| Days 31 to 60 | Run the system with weekly manager review | First independently booked meeting, consistent reply classification |
| Days 61 to 90 | Own the account list and the weekly report | New accounts added to the list, not just inherited ones worked |
What each phase of a handoff ramp should produce before moving to the next one.
What to request on day one
- The full reply history with its classification tags, not a dashboard screenshot that disappears when access changes.
- A do not contact list of every account that already opted out or closed, so week one does not start with a duplicate send.
- The list of offers tested by segment, including which ones failed, not just the one currently running.
- Which domains are warmed, which are new and the current sending limits for each.
- The weekly report template the agency used, as a starting point for the new hire's own reporting cadence.
FROM THE YARD
We handed off a client's outbound to their new in-house hire who got full CRM access and a tidy dashboard on day one and still spent the first two weeks guessing which accounts had already been contacted. The dashboard showed totals, not a queryable reply log. The fix was a single export: every account, every send date, every reply and its tag, in one sheet the new hire could filter. That sheet should exist before day one, not get built reactively in week two.
Where handoff ramps stall
THE STALLED RAMP
- The new hire gets system access but no explanation of what already worked.
- Reporting starts from a blank template instead of the agency's categories.
- Full volume sending starts in week one, before anyone has checked deliverability.
- By day 90, every meeting still traces back to accounts the agency had already warmed up.
THE WORKING RAMP
- The new hire reads the reply history and the offer tests before sending anything new.
- Reporting uses the inherited categories, so the data stays comparable.
- Volume ramps in stages while deliverability is checked weekly.
- By day 90, new accounts have been added and at least one meeting came from outside the inherited list.
None of this works without the wider system the agency was running on, the market map, signals and data that decided who got contacted in the first place. A new hire who inherits a good system and runs this plan well should be producing independent pipeline by day 90. One who inherits a weak system will hit the same wall the agency did, just later. If the handoff is still ahead of you rather than behind you, our done-for-you outbound system is built so the handoff, whenever it happens, moves a system that is already documented rather than one that only lived in someone's head.
Questions about the first 90 days for an in-house SDR
How long does it take a new in-house SDR to ramp after an agency handoff?
Plan for about 90 days to reach independent output, in line with the Bridge Group's 2025 finding that the average SDR takes 3.0 months to reach full productivity. A handoff can be faster than a cold start when the inherited reply history and offer tests are usable. It runs slower when they only exist as a dashboard nobody can query.
What should a new in-house SDR do in the first week?
Read the reply history, the do not contact list and the offers already tested before sending a single new email. The first week is about understanding what the agency already proved, not about volume.
Who should manage a new in-house SDR during a handoff ramp?
Whoever owns the outbound result, usually a sales or revenue operations lead, should run a weekly check-in for the first 60 days at minimum. Gallup found in 2018 that only 12% of employees strongly agree their company does a great job onboarding new hires. A handoff this specific rarely survives being left informal.
What does a successful 90 day ramp look like?
By day 90, the new hire should be running the weekly report independently, have added new accounts beyond the ones the agency already worked and have booked at least one meeting that did not come from inherited pipeline.
What if the agency did not leave a usable reply history?
Treat it as a cold start rather than a handoff and plan on the full 3.0 month average, since there is no inherited data to accelerate the first 30 days. This is also the clearest sign the handoff itself was not negotiated well, which is worth fixing in writing before the next contract.
Sources: The Bridge Group, 2025 SDR Models, Motions and Metrics Report and Gallup, Why the Onboarding Experience Is Key for Retention, 2018.