How to Ramp New SDRs Faster: A 30-60-90 Day Plan with an Outbound Agent

Callia Peterson

Summarize this article with your favorite LLM
Table of contents

Summarize article with your LLM

SDR ramp is the period between a new sales development representative's start date and consistent quota attainment.

A structured plan shortens ramp by teaching the ideal customer profile, messaging, and reply handling early, and by letting an outbound agent absorb list building, research, and sequence setup while the new rep learns to run conversations.

A new SDR is expensive for a long time before the rep is productive. Salary, tools, manager time, and the opportunity cost of accounts handled poorly all accrue during the weeks when output is low.

Most sales development leaders know this and still run onboarding as a loose mix of shadowing, slide decks, and trial by fire.

New reps learn the product, then the tools, then the messaging, then the targeting, in whatever order the calendar permits, and many spend their first weeks on work that does not build skill at all.

The cost is hard to see because ramp is often measured only at the end. A team knows when a rep reached quota, and not which parts of the first ninety days helped or hurt. Without that visibility, leaders add more training sessions when the problem lies elsewhere.

In many teams, the largest drag on ramp is not a lack of knowledge. It is the amount of low-value work between a new rep and a conversation: finding accounts, researching them, building lists, drafting messages, and managing tools.

A rep who spends most of the week on that work has little time left to practice the skill that matters, which is talking to buyers.

Outbound agents change that equation. An agent can handle list building, research, and sequence writing, and show its reasoning, so a new rep can spend more time on conversations and also learn from how the agent targets and writes.

The result depends on how the team sets it up. Handing a new rep an agent with no training, no review, and no explanation produces a rep who does not understand the work. Pairing a structured plan with an agent that explains its decisions produces a rep who learns the logic of targeting and messaging faster.

This guide gives a practical plan for ramping new SDRs. It defines ramp and explains what slows it. It lays out a 30-60-90 day plan, shows how an outbound agent changes the first weeks, and covers coaching, review routines, metrics, and common mistakes.

It also covers ramp for enterprise motions, onboarding for remote and distributed teams, and a worked example. Finally, it explains how Rox's Outbound Agent supports ramp and how people stay in control.

The guide is written for sales development leaders, revenue operations teams, and enablement managers. It does not give benchmark ramp times, because ramp varies by market, product complexity, and team structure. It tells you how to measure your own and set your own targets.

What Is SDR Ramp?

SDR ramp is the period during which a new sales development representative moves from start date to consistent performance against quota.

Ramp has three phases that overlap.

  • Learning. The rep absorbs the product, the ideal customer profile, the messaging, the tools, and the process.

  • Practicing. The rep runs real outreach and conversations with review and feedback.

  • Owning. The rep manages a segment and results with light supervision.

Ramp time vs ramp quality

Ramp time is how long the journey takes. Ramp quality is how well the rep performs at the end. A fast ramp that produces a rep who books weak meetings is not a success. Track both. Define "consistent quota attainment" and "meeting quality" before you measure.

Ramp for SDRs vs ramp for AEs

SDR ramp focuses on activity, targeting, and conversation skills at the top of the funnel. Account executive ramp focuses on discovery, deal management, and closing. The handoff between the two roles matters for both. See SDR-to-AE handoff.

What Slows SDR Ramp?

Six blockers account for most of the delay: unclear targeting, list-building time, message writing from scratch, tool sprawl, slow feedback, and weak reply handling.

Ramp blocker

Why it slows the rep

What helps

Unclear ideal customer profile

The rep contacts poor-fit accounts and gets weak results

A written profile with examples of fit and non-fit

List-building time

Hours go to research and spreadsheets, not conversations

Automated list building and refresh

Message writing from scratch

Quality varies and takes time

Approved instructions and examples

Tool sprawl

The rep switches between systems

Fewer, connected tools. See context switching

Slow feedback

Mistakes repeat before a manager sees them

Daily review early on

Weak reply handling

Interested prospects go cold

A reply playbook and practice. See how to handle replies to cold outreach

Product knowledge gaps

The rep cannot answer basic questions

Short, structured product training

Low confidence

The rep avoids calls and difficult replies

Role-play and shadowing

The hidden cost of manual work

Manual research and list building teach little. A rep who spends two weeks building lists learns how to use a database, not how to read an account or write for a buyer. Removing that work does not skip learning. It moves learning to the activities that build skill.

Principles for a Faster, Better Ramp

  1. Define the destination. Write what a ramped rep does, in measurable terms, before you design the plan.

  2. Sequence the learning. Teach the ideal customer profile and the buyer's problem before tools and tactics.

  3. Practice early. Put reps in real conversations with review as soon as they are ready.

  4. Shorten feedback loops. Review work daily at first, then weekly.

  5. Remove low-value work. Automate list building and sequence setup where you can.

  6. Teach the reasoning. Show why an account was chosen and why a message was written that way.

  7. Measure leading indicators. Do not wait for quota attainment to know whether the plan works.

  8. Keep people in the loop. Coaching and review stay with managers and senior reps.

A 30-60-90 Day Ramp Plan

A 30-60-90 day plan moves a new rep from learning, to practicing with review, to owning a segment. Adjust the lengths to your own ramp data.

Days 1 to 30: Learn

Goal. The rep understands the buyer, the offer, the messaging, and the process, and has handled a first set of conversations with close review.

  1. Study the ideal customer profile and buying committee. Read the written profile, look at examples of good-fit and poor-fit accounts, and learn who is involved in a typical decision. See ideal customer profile in outbound sales and buying committee mapping and multi-threading.

  2. Review approved messaging and the reasoning behind it. Understand the problems the team addresses, the language it uses, and the claims it may make. Proof points must be validated and attributed, and customer references must come from approved, published case studies.

  3. Shadow calls and read real reply threads. Listen to experienced reps and read how replies were handled.

  4. Learn the tools. Keep tool training short and tied to tasks.

  5. Work a small, reviewed account set. Review each message and reply with a manager or senior rep.

  6. Practice reply handling. Use role-play for the six reply types.

Checkpoints. The rep can explain the ideal customer profile, name the main buyer roles, describe the offer in two sentences, and classify replies correctly in a review exercise.

Days 31 to 60: Practice

Goal. The rep runs live conversations and reply handling on an assigned account set, with regular review.

  1. Take over reply handling for assigned accounts. The rep answers replies within the team's service target, with a manager reviewing a sample.

  2. Run live conversations. Calls and meetings happen with feedback after each one.

  3. Propose instruction changes. The rep reads the agent's instructions and suggests improvements based on what replies show.

  4. Study results by step. The rep reviews which messages draw replies and which do not.

  5. Practice objection handling. Use real objections from the past weeks.

  6. Learn to hand off. Practice the handoff to account executives. See SDR-to-AE handoff.

Checkpoints. The rep meets the response-time target on a sample, books meetings that account executives accept, and proposes at least one instruction change that a manager approves.

Days 61 to 90: Own

Goal. The rep owns a segment and its metrics with light supervision.

  1. Own an account segment. The rep is accountable for results in a defined audience.

  2. Run a test. Design and run a simple experiment. See how to A/B test outbound sequences.

  3. Present results. The rep reviews the segment's results with the manager and proposes next steps.

  4. Coach a peer or newer rep on one skill. Teaching reinforces learning.

  5. Set the next quarter's goals. The rep and manager agree on targets based on measured results.

Checkpoints. The rep meets the team's definition of consistent performance, and the manager can describe the rep's strengths and gaps with evidence.

Adjusting the plan

Shorten or lengthen phases based on your measured ramp. Add time for complex products or long enterprise cycles, and tighten it for simple offers. Review the plan each quarter with data from recent hires.

How an Outbound Agent Changes the Ramp?

An outbound agent takes over the repeatable work that usually fills a new rep's first weeks, so more time goes to conversations, review, and learning.

Work the agent can absorb

Task

Without an agent

With an agent

List building

New rep builds lists by hand

Agent finds prospects from an audience description and refreshes the list

Account research

Rep researches each account

Agent researches and shows its reasoning

Sequence writing

Rep drafts every message

Agent drafts from reviewed instructions

Follow-up

Rep tracks touches manually

Agent runs the sequence

First-pass reply classification

Rep reads and sorts everything

Agent classifies, rep reviews

Meeting booking

Rep coordinates times

Agent offers times and books

What the new rep does instead

  • Reads the agent's reasoning to learn targeting and messaging.

  • Reviews samples of agent output and flags problems.

  • Handles replies, calls, and conversations.

  • Proposes instruction changes based on what replies show.

  • Prepares for meetings and handoffs.

The learning effect of explainable output

An agent that shows why each lead was selected and the instructions used to write each message gives a new rep a worked example for every account. The rep can compare the reasoning with the account and learn what makes a fit.

When the rep sees a weak message, the rep corrects the instruction instead of rewriting one message, and the correction applies across the sequence. That practice builds judgment about targeting and tone faster than rewriting messages one at a time.

The risk of over-reliance

A new rep who accepts every output without review does not learn. Managers should require reviews, ask reps to explain why an account fits, and rotate reps through hands-on tasks. The agent removes repeatable work and does not remove the need to build skill.

Coaching and Review Routines

Frequent, specific feedback shortens ramp more than any single training session.

Routine

Frequency

Purpose

Daily review of early output

Daily in the first weeks

Catch mistakes early

Reply-handling review

Weekly

Improve speed and accuracy

Call and meeting review

After each early call

Build conversation skill

Instruction review

Weekly

Teach targeting and tone

Segment results review

Weekly in days 61 to 90

Build ownership

Ramp check-in

Every two weeks

Compare progress with the plan

What good feedback looks like

  • Specific. Point to the exact message, reply, or call.

  • Timely. Give feedback close to the event.

  • Actionable. State what to do differently.

  • Balanced. Note what worked as well as what did not.

Who coaches

Managers own the plan. Senior reps can run role-play and review samples. Revenue operations can help with tools and data. Enablement can supply materials and track progress.

What to Measure During Ramp

Measure leading indicators during ramp and outcome metrics afterward. Set targets from your own team's history.

Metric

Type

What it shows

Time to first meeting held

Leading

How fast the rep reaches a real conversation

Conversations handled per week

Leading

Practice volume

Reply response time

Leading

Responsiveness. Compare with the team's service target

Reply classification accuracy

Leading

Reading skill, on a reviewed sample

Review score on messages and replies

Leading

Quality, scored by a manager

Instruction improvements proposed and adopted

Leading

Judgment about targeting and tone

Meetings booked and accepted by AEs

Outcome

Meeting quality

Meetings held and show rate

Outcome

Commitment of booked buyers

Quota attainment

Outcome

Final measure

Comparing cohorts

Compare each new rep with earlier cohorts at the same week of tenure. Differences show whether a change to the plan or tools helps. Control for segment and territory, since easier segments make ramp look faster.

Avoiding misleading numbers

A fast ramp on easy accounts says little. A strong first month with weak meeting quality says little. Combine speed and quality, and read the numbers with the context of each rep's segment. For definitions, see outbound prospecting KPIs and benchmarks.

Ramping SDRs for Enterprise Motions

Enterprise outbound has larger buying committees, longer cycles, and higher stakes per account, so ramp needs more emphasis on research judgment, account coordination, and multi-threading.

The context gap for new reps

New reps in enterprise teams struggle because the information they need is scattered. Account history sits in the warehouse, the inbox, call transcripts, and product data, and the CRM shows only part of it.

Rox calls this the context gap. A new rep without access to that context repeats questions that earlier conversations already answered and misses signals that experienced reps know to look for.

Onboarding Remote and Distributed SDR Teams

Remote teams need more deliberate structure, because new reps cannot pick up norms by sitting near experienced colleagues.

  • Document the plan. Write the 30-60-90 day plan and share it on day one.

  • Pair reps. Assign a senior buddy for questions and shadowing.

  • Record examples. Keep a library of strong messages, replies, and calls with notes on why they worked.

  • Schedule reviews. Do not rely on chance encounters for feedback.

  • Use shared dashboards. Make progress visible to the rep and the manager.

  • Create peer practice. Run role-play sessions across time zones in small groups.

Common Mistakes

  1. Starting reps on tools before targeting. The rep learns clicks without understanding the buyer.

  2. Skipping early review. Mistakes repeat for weeks.

  3. Measuring only quota attainment. Leading indicators show problems earlier.

  4. Handing over an agent with no training. The rep learns to accept outputs, not to judge them.

  5. Ignoring reply handling. Interested prospects go cold.

  6. Overloading the first weeks. Too much content reduces retention.

  7. Comparing reps on different segments. Easy segments flatter results.

  8. Not updating the plan. Each cohort should improve on the last.

  9. Treating the agent as a replacement for coaching. People still teach and review.

  10. Not documenting approved messaging. New reps invent claims that the team cannot support.

How Rox's Outbound Agent Supports Ramp

Rox's Outbound Agent finds prospects, researches them, writes sequences, handles replies, and books meetings from a one-sentence audience description, and it shows its reasoning, which supports both productivity and learning.

The agent follows four visible stages: Prospect, Configure, Execute, and Monitor. It combines email and LinkedIn in one sequence and refreshes prospect lists continuously, so a new rep starts with a current audience and does not spend weeks building lists.

How the stages support a new rep

Stage

What the agent does

What the new rep does

Prospect

Finds prospects that match the audience description

Reads why each lead was selected and compares it with the profile

Configure

Drafts the sequence from the instructions

Reviews the instructions and learns the team's tone and rules

Execute

Sends touches, handles replies, and books meetings

Handles replies and conversations, and reviews samples

Monitor

Shows live counts of leads found, contacts in sequence, actions taken, and meetings booked

Reviews results and proposes instruction changes

Features that support learning

  • Explainable selection. The agent shows why each lead was selected and the instructions used to write each message. A new rep gets a worked example for every account.

  • Instruction-level correction. When a message is off, a rep corrects the instruction instead of the individual message, and the correction applies across the sequence. That builds judgment about targeting and tone.

  • Live counts. The Monitor stage gives managers and reps a shared view of progress.

The data foundation

Rox is warehouse-native. Its context graph builds a system of context from the full data warehouse, so a new rep inherits account history immediately instead of reconstructing it. That narrows the context gap that slows new hires and supports revenue orchestration across the account lifecycle.

A persistent agent assigned to each account keeps that context from the first outreach through renewal and expansion.

Human oversight

AI-generated outputs are informational and should be reviewed by authorized personnel before action. Features described as automated operate within user-defined parameters and need initial configuration and ongoing oversight.

Managers should review the instructions that govern messages, sample agent output weekly with the new rep, and keep a person on objections and high-value accounts. Treat the agent as a working colleague on the account, not as a replacement for coaching.

Current limitation

Rox's Outbound Agent does not currently support contact-level activity writeback to CRM fields. Plan CRM reporting accordingly, and teach new reps which handoff details to record in the CRM themselves.

A Worked Example: Ramping Three New SDRs

Scenario. A team hires three SDRs to work operations leaders at mid-market software companies. The team uses an outbound agent for list building, research, and sequence setup.

  1. Define the destination. The manager writes what a ramped rep does: meets the response-time target, books meetings that account executives accept, and owns a segment.

  2. Prepare the materials. The team writes the ideal customer profile with examples, approved messaging, a reply playbook, and a handoff checklist.

  3. Days 1 to 30. Reps study the profile and messaging, shadow calls, read real reply threads, and work a small account set. A manager reviews every message and reply daily.

  4. Read the agent's reasoning. Each rep reviews why a set of leads was selected and compares the reasoning with the profile. The team discusses disagreements.

  5. Days 31 to 60. Reps take over reply handling for assigned accounts and run live conversations. Managers review a sample each week and give specific feedback.

  6. Propose instruction changes. Each rep suggests changes based on what replies show. A manager approves changes before they scale.

  7. Days 61 to 90. Each rep owns a segment, runs one test, and presents results.

  8. Measure. The team tracks time to first meeting held, reply response time, review scores, instruction changes adopted, and meetings accepted by account executives.

  9. Compare to earlier cohorts. The manager compares the three reps with earlier hires at the same tenure and notes what changed.

  10. Revise. The team updates the plan for the next cohort based on results and rep feedback.

What the team checks after the first cohort

  • Did reps reach their first meeting held sooner than earlier cohorts?

  • Did meeting quality hold, as judged by account executives?

  • Did reps understand why accounts fit, or did they accept outputs without thinking?

  • Did review routines catch weak messages early?

This structure is a template to test, not a promise of results.

Conclusion

SDR ramp is a design problem, not a waiting game. A new rep needs clear targeting, approved messaging, early practice with real conversations, and frequent specific feedback.

The largest drag in many teams is the manual work that sits between a new rep and a buyer: list building, research, and message writing. Removing that work gives the rep more time to practice the skill that matters.

A 30-60-90 day plan gives structure. Days 1 to 30 teach the buyer, the offer, and the process. Days 31 to 60 put the rep in live conversations with review. Days 61 to 90 give the rep a segment to own.

Leading indicators, such as time to first meeting held and review scores, show whether the plan works long before quota attainment does, and comparisons with earlier cohorts show whether changes help.

An outbound agent supports this plan by absorbing repeatable work and showing its reasoning, so a new rep learns targeting and tone from worked examples. People stay in charge: managers review instructions and samples, coach conversations, and take the sensitive accounts.

Rox's Outbound Agent works inside a visible workflow, shows why each lead was selected, and lets a rep correct an instruction once to change the sequence, with a warehouse-native system of context that gives new reps account history from day one.

To start, measure your current ramp, write the 30-60-90 day plan on one page, and compare your next cohort with the last.

Frequently Asked Questions

What is SDR ramp time?

SDR ramp time is the period from a new rep's start date to consistent quota attainment. It varies by market, product complexity, and team structure, so measure your own.

How long should it take to ramp a new SDR?

There is no universal figure. Set a target from your own history, compare each new cohort with earlier ones at the same tenure, and track meeting quality as well as speed.

What should a 30-60-90 day plan for a new SDR include?

Days 1 to 30 cover the ideal customer profile, messaging, shadowing, tools, and a small reviewed account set. Days 31 to 60 add live conversations and reply handling with review. Days 61 to 90 give the rep a segment to own, a test to run, and results to present.

What slows SDR ramp the most?

Unclear targeting, time spent on list building and research, writing messages from scratch, tool sprawl, slow feedback, and weak reply handling. Many teams find that manual work between the rep and the buyer is the largest drag.

Does an outbound agent replace SDR training?

No. It removes repeatable work and shows its reasoning, which gives new reps more time to practice conversations. Managers still coach, review, and take the sensitive accounts.

What should a new SDR own first?

Reply handling on a small, reviewed account set. It builds conversation skill, and it is the point where outbound effort turns into meetings.

How do I measure ramp progress?

Use leading indicators such as time to first meeting held, conversations handled per week, reply response time, review scores, and instruction improvements adopted. Use meetings accepted by account executives, show rate, and quota attainment as outcome metrics.

How can I tell if a new rep is relying too much on the agent?

Ask the rep to explain why an account fits and why a message was written that way. Review samples of the rep's corrections. A rep who cannot explain the reasoning is accepting outputs without judging them.

How do I ramp SDRs in a remote team?

Document the plan, pair each new rep with a buddy, keep a library of strong examples, schedule reviews instead of relying on chance contact, and run peer role-play across time zones.

What should enterprise SDRs learn that others do not?

Account reading, multi-threading across buying committees, coordination with other sellers, slower cadences for senior buyers, trigger events and account signals, and compliance rules.

Can AI help onboard SDRs?

Yes, within user-defined parameters. An outbound agent can handle list building, research, and sequence writing, and show its reasoning. People should review the instructions and sampled output and keep control of sensitive replies. AI-generated outputs are informational and should be reviewed by authorized personnel before action.

How does Rox's Outbound Agent help new reps?

The agent finds prospects, researches them, writes sequences, handles replies, and books meetings from a one-sentence audience description. It shows why each lead was selected and the instructions behind each message, and a rep can correct an instruction to change the whole sequence. Rox's system of context gives a new rep account history from the start.

How often should I update the ramp plan?

Review it each quarter with data from recent hires, and revise it after any change in product, tools, or segment.

Summarize this article with your favorite LLM

Rox is committed to the privacy and security of its users. Customer data processed through the Rox platform is encrypted in transit and at rest using AES-256 encryption and is never used to train generalized machine learning models. Rox maintains SOC 2 Type II compliance and undergoes independent third-party security audits on an annual basis. All AI-generated outputs, including but not limited to prospect recommendations, message drafts, meeting summaries, and pipeline scoring, are provided for informational purposes and should be reviewed by authorized personnel before any action is taken. Performance metrics referenced on this website, including pipeline generation figures, response rates, and revenue impact, reflect results reported by individual customers under specific configurations and may not be representative of all deployments. Actual results will vary based on factors including but not limited to data quality, CRM configuration, outreach volume, market conditions, and target audience. Rox does not guarantee specific revenue outcomes. The Rox platform integrates with third-party services including Salesforce, HubSpot, Gmail, Microsoft Outlook, Slack, and others; availability and functionality of third-party integrations are subject to the respective providers' terms of service and may change without notice. Features described as "autopilot," "autonomous," or "automated" operate within user-defined parameters and require initial configuration and ongoing oversight. Rox, the Rox logo, and "Revenue on Autopilot" are trademarks of Rox Data Corp. All other trademarks are the property of their respective owners. Service availability is subject to the terms outlined in your enterprise agreement. For questions regarding data processing, compliance certifications, or platform capabilities, contact security@rox.com.

Rox is committed to the privacy and security of its users. Customer data processed through the Rox platform is encrypted in transit and at rest using AES-256 encryption and is never used to train generalized machine learning models. Rox maintains SOC 2 Type II compliance and undergoes independent third-party security audits on an annual basis. All AI-generated outputs, including but not limited to prospect recommendations, message drafts, meeting summaries, and pipeline scoring, are provided for informational purposes and should be reviewed by authorized personnel before any action is taken. Performance metrics referenced on this website, including pipeline generation figures, response rates, and revenue impact, reflect results reported by individual customers under specific configurations and may not be representative of all deployments. Actual results will vary based on factors including but not limited to data quality, CRM configuration, outreach volume, market conditions, and target audience. Rox does not guarantee specific revenue outcomes. The Rox platform integrates with third-party services including Salesforce, HubSpot, Gmail, Microsoft Outlook, Slack, and others; availability and functionality of third-party integrations are subject to the respective providers' terms of service and may change without notice. Features described as "autopilot," "autonomous," or "automated" operate within user-defined parameters and require initial configuration and ongoing oversight. Rox, the Rox logo, and "Revenue on Autopilot" are trademarks of Rox Data Corp. All other trademarks are the property of their respective owners. Service availability is subject to the terms outlined in your enterprise agreement. For questions regarding data processing, compliance certifications, or platform capabilities, contact security@rox.com.