How to Onboard a New SDR to Your GTM Stack

Why do new SDRs take so long to become productive?

Usually because nobody explains how the stack fits together. A new SDR gets logins to a CRM, an enrichment tool, a sequencing tool, and a dialer, then learns by trial and error. They break things, miss leads, and lose confidence. A structured onboarding to the GTM stack shortens that ramp and prevents costly mistakes.

Most SDR onboarding focuses on the pitch: the product, the ideal customer profile, objection handling, and call practice. That matters. But the tools are where new reps make the mistakes that hurt the business, such as emailing a customer by accident, overwriting a field, or ignoring a hot inbound lead because they did not know where it appeared.

I approach this as a GTM engineer. The stack is a system with rules, and a new rep needs to learn the rules as much as the buttons. Here is the two week plan I would use for a small team without a dedicated enablement function.

What should a new SDR understand before touching any tool?

They should understand how a lead moves through your system from first touch to handoff. Draw the flow on one page: where leads come from, how they are enriched, how they are scored and routed, where the SDR works them, and how they pass to an account executive. Context first, buttons second.

That single page prevents most early mistakes. A rep who knows that inbound demo requests are routed automatically will not duplicate them by hand. A rep who knows that enrichment writes certain fields will not overwrite them. The map turns a confusing set of tools into a sequence that makes sense.

If you do not have that map, build it before the rep starts. A stack inventory is the fastest way to get there, and I walked through it in writing a GTM stack inventory in a spreadsheet. The inventory also tells you which tools the new rep actually needs access to.

How should access be set up on day one?

Give the rep their own login to every tool they need, with the least access required to do the job. Do not share accounts. Set permissions so they can work their own records but cannot bulk edit, delete, or change workflows. Add access as they prove they understand each tool.

Shared accounts cause real damage. When every action is logged under one user, nobody can tell who changed a record or sent an email. Individual logins also make offboarding clean later. Use your identity provider or single sign-on where you have it, so access can be granted and revoked in one place.

Prepare their workspace too. Create their saved views in the CRM, their default sequences, their email signature, and their calendar booking link before day one. Arriving to a ready workspace signals that the team is organized, and it removes a day of setup busywork.

What should the first week cover?

Week one is about the CRM and the rules. Teach the lead flow, the fields that matter, lead statuses and what each means, how to log activity, and how to find the leads they own. End the week with the rep working a small set of real but low-risk records under supervision.

Spend time on the fields the rep must fill and the ones they must never touch. Required fields such as disqualification reason or next step make reporting work. Protected fields such as owner, lifecycle stage, or anything written by automation should be off limits. Explain why, so the rule sticks.

Cover the service level agreement between marketing and sales early. The rep needs to know how fast to respond to each lead type and what counts as a response. I described how to write one in writing a marketing to sales SLA that reps follow. A new SDR should know those rules in their first week.

What should the second week cover?

Week two is about prospecting tools: enrichment, list building, and sequencing. Teach how to build a list that matches the ICP, how enrichment adds data, how to check data quality, and how to enroll contacts in sequences safely. End the week with the rep running their first small outbound batch with review.

Data quality deserves a full session. Show the rep how to spot bad enrichment: wrong company, outdated title, personal email, or missing fields. Teach them what to do when data looks wrong, such as flagging it rather than guessing. Bad data sent to sequences damages domain reputation and wastes good accounts.

Sequencing safety matters just as much. Teach the suppression rules: never email current customers, open opportunities, or anyone on the do not contact list. Show where those rules are enforced automatically and where the rep must check. The first batch should be small and reviewed before sending.

How do you teach the handoff to account executives?

Teach it with real examples. Show a good handoff record and a bad one, explain what the account executive needs to see, and have the rep shadow a handoff call. The handoff is where SDR work turns into pipeline, so it deserves explicit training rather than assumptions.

A good handoff includes the account context, the specific pain the prospect described, who else is involved, what was promised, and the agreed next step. Without these, the account executive starts from scratch and the prospect repeats themselves, which hurts the deal.

Give the rep a checklist they can follow every time. A short handoff template in the CRM, with required fields, keeps quality consistent across reps. Review the first few handoffs together and give specific feedback while the habits are forming.

How should AI tools fit into SDR onboarding?

Teach AI tools as assistants with rules, not as autopilot. If your stack uses AI for research, email drafts, or reply classification, show the rep what each AI step does, where it can be wrong, and what they must check before anything goes to a prospect. Human review stays mandatory until trust is earned.

New reps are often tempted to send AI drafts without reading them. That is how embarrassing errors reach prospects: wrong names, invented details, or tone that does not match your brand. Set a clear rule that every AI draft is read and edited before sending, at least for the first months.

If your team uses an AI SDR tool that sends on its own, the new rep needs to understand its guardrails too. My checklist on what to check before an AI SDR sends for you covers the review points worth teaching.

How do you know onboarding worked?

Measure behavior in the CRM, not just activity counts. Check whether the rep logs activity correctly, fills required fields, responds to inbound within the SLA, sends clean handoffs, and avoids data mistakes. Review a sample of their records weekly for the first month and give specific feedback.

Activity volume can mislead. A rep who sends many emails to poorly chosen contacts looks busy but creates little pipeline and some risk. Quality signals, such as reply rates from ICP accounts and accepted handoffs, tell you more about whether the rep understood the system.

Ask the rep for feedback too. What was confusing? Which tool caused the most trouble? Their fresh eyes often spot broken steps and unclear rules that the rest of the team has stopped noticing. Fix those, and the next rep ramps faster.

What should you do next?

Before your next SDR starts, draw the one-page lead flow, set up individual logins with limited permissions, and prepare their workspace. Write a two week plan: CRM and rules in week one, prospecting tools and safe sequencing in week two, with supervised real work at the end of each.

Create a short handoff checklist and an AI review rule, and plan weekly record reviews for the first month. After onboarding, ask the rep what was confusing and update the plan. Each new hire should make the onboarding better for the next one.

If you want help mapping your stack, setting permissions, and building the guardrails that make new reps productive without breaking things, reach out through pravinkumar.co. I build the websites and the automations behind them for lead generation, and well-onboarded reps are what make those systems pay off.