SDR Playbook: A Complete Guide to AE and SDR Teamwork and AI

Open ten SDR playbooks and nine are checklists: call before ten, send four emails, post twice. They are silent on who owns which number, how a meeting turns into a deal, and what to do once the tactic wears out. Reps follow the checklist, managers audit activity, and the pipeline does not move.

This guide is the connective tissue. It shows how SDRs and AEs divide the work, which channels earn time, how the handoff should run, which numbers to trust, where AI fits and how to protect an AE's selling hours. Managers of SDRs and AEs, sales heads and founders putting together a first outbound team are the intended readers, and each section sends you to a fuller article.

What the Document Actually Is

Think of it as a written treaty between two teams. Inside it you find the target buyer, the channels in play, how a lead travels from SDR to AE, the yardstick for each side and the approved tools. A good one is short, tested against your own results and revised when those results shift.

Do not confuse it with a script, which dictates wording. A playbook dictates actions and their sequence, plus the test for whether they worked.

Two Roles, Defined Plainly

A sales development rep (SDR) generates qualified meetings. An account executive (AE) carries the deal from an accepted first meeting until it is signed. Titles blur across firms, and the difference between SDR and BDR is covered in what an SDR is.

To see the typical outline of the SDR job, look at the Bridge Group's February 2025 study, its tenth on SDRs. Its panel was 351 B2B companies, of which 78% were based in North America and 83% sold SaaS. The averages: 3.0 months to ramp, 1.9 years in the seat, a ratio near 1 SDR to 2.4 AEs, and only 60% of SDRs hitting quota, a low for the series. These are self-reported averages from one consultancy's panel, so use them as context, not as targets.

The AE side is slower. The same firm's 2026 AE study, with 158 companies, puts average AE ramp at 6.2 months, a record. That gap matters: an SDR can start producing meetings long before the AE who receives them is fully productive.

Symptoms of a Playbook That Is Not Working

• SDRs hit their activity numbers while AEs call the meetings thin.
• AEs open the first call by repeating questions the SDR already asked.
• Nobody can tie last quarter's pipeline to a channel.
• The CRM and the forecast call tell different stories.
• An AI tool was bought and nobody can say what it changed.
• AEs lose most of the week to admin and internal meetings.

Three or more of these point at the system, not at an individual.

Three Reasons Playbooks Fail

First, the two roles are paid on different things: meetings for SDRs, revenue for AEs. Absent an agreed meaning for a good meeting, each side can be right while the pipeline is wrong. Second, counting activity displaces learning: dials and emails are simple to total, and teams steer toward whatever they total. Third, tooling shows up before any rules. Sequencers, AI agents and call recorders amplify the existing process, so a flawed one just breaks at higher speed.

Channels: What the Public Data Supports

No channel carries the load alone. The better question is which touch follows the last one and why.

Phone

Gong filtered a library of more than a million recordings down to 90,380 connected outbound cold calls and labelled a call a success when a follow-up meeting was held. Winning calls lasted nearly twice as long, while question count showed no statistical gap. The authors frame the caller's job as earning time. This is correlational vendor work, first published in 2018 and updated in 2026. We unpack it in the cold calling success rate article, and related pieces cover opening lines and voicemail.

Email

Benchmarks vary with definitions. Hunter's report on 31 million emails sent by its users in 2025 gives 3% as the reply rate for sales outreach, against 4.5% across all sequences, so a blended average flatters a selling team. The reasons for the spread are in this teardown, and a day-by-day follow-up plan builds the sequence.

Social outreach

Expandi analysed 13.2 million connection requests from May 2025 to April 2026 on its own platform and reported 28.5% accepted and 3.0% replying to the connection note. Its 10.4% message reply rate counts replies to every outbound message type, including welcome messages, follow-ups and emails, so it is not a clean measure of conversations after acceptance. It is sender-side data from a vendor. A fortnight-long LinkedIn routine converts it into daily habits.

Blending the channels

Work a single list of well-fitting accounts through a brief sequence that alternates phone, email and social touches, and keep the stated reason for reaching out identical everywhere. The wider split of effort is covered in where pipeline comes from.

The Handoff Is Where Pipeline Disappears

Booking is not pipeline. A meeting counts only after an AE takes it and runs a worthwhile first call. Notes written later from memory record what the SDR retained, not necessarily what the buyer said. The remedy is a compact acceptance packet, completed inside an hour and phrased as the buyer phrased it, which the AE may send back when it falls short. It covers fit, trigger, pain, current approach, stakeholders and an agreed next step. The handoff notes guide has the fields, and five SDR discovery questions fills them.

Scorecards: Inputs, Outcomes and the Gap Between

Dials and emails are inputs. Meetings held and accepted, pipeline created and time to first held meeting are outcomes. The common error is paying on inputs. A five-line scorecard appears in the SDR metrics teardown. Measure each line against your own last four quarters before looking at any industry average. Put each SDR next to the AEs who receive their meetings. A wide gap between booked and accepted usually blames the list, the message or the handoff, not the SDR's effort.

Pay for Accepted Meetings, Not Booked Ones

The default comp plan rewards a meeting on the calendar. That is the cheapest thing to produce, and it is why AEs distrust the pipeline. A plan that pays on accepted meetings, or better on held ones, moves the SDR's attention from volume to fit, and it forces the two roles to agree on what accepted means before anyone dials.

The approach has a price. Acceptance hands discretion to AEs, and a hasty rejecter can starve an SDR. Record each rejection with its reason and read the log monthly with both sides present, so trends show up as list problems and not personal feuds. The Bridge Group found only 60% of SDRs at quota in 2025, so pressure on the role is already high and a plan change deserves a transition quarter.

High-velocity motions with short cycles and small deals sit outside this view, with no AE gate and booked meetings convert so reliably that acceptance adds paperwork. In that setting paying on held meetings may be enough.

Where AI Belongs

Current AI products research accounts, write first drafts, condense calls and refresh records. Vendor promises are big and seldom come with public samples. Run a matched pilot instead, with a human reading each message, and score it on meetings held and accepted for every hour and every dollar. A fortnight pilot plan explains the method, and the replacement question gets a data-driven treatment of its own.

Protecting AE Time and Data Quality

In Salesforce's State of Sales research, drawn from 7,775 answers gathered in late summer 2022, reps said selling took only 28% of their time. That is a four-year-old, self-reported, global average, so treat it as a pointer and audit a real week of your own. Calendars usually explain more than software does, as AE time management shows. Records matter too, because a CRM nobody trusts undermines handoffs and forecasts. The hygiene checklist sets a rhythm.

An Operating Calendar That Keeps Both Teams Honest

• Mondays, twenty minutes: both teams go through the past week's accepted and held meetings, picking one success and one miss.
• Wednesdays, half an hour: the manager and an SDR replay two recordings and choose one habit to retain and one to alter.
• Fridays, a quarter hour: AEs return any packet that failed, adding one line on the gap.
• Monthly, an hour: the manager sets the scorecard beside four quarters of history and removes one rule or field.

Expect roughly sixty minutes weekly from each manager. Keep this timetable fixed for a whole quarter; changing it sooner hides what made the difference.

Thirty Days to a First Version

1. Week one: draft a single page defining a good meeting, have SDRs and AEs sign it, and choose the one list to work.
2. Week two: adopt the acceptance packet and build the scorecard from CRM and dialer data.
3. Week three: work the list with one blend of channels, logging each touch.
4. Week four: set held and accepted meetings side by side per channel, keep the winners, cut one item, and then trial AI on a matched group.

What you end with is a trial version and a custom of revising it on evidence, rather than a final document.

When a Second Opinion Pays

Seek an outside view if the scorecard is clear yet results stay flat, if the two roles dispute what a good meeting is, or if you move into an unfamiliar segment. A coach or a fellow manager sees past your habits. Be wary of anybody guaranteeing outcomes, since market, product and timing all intervene.

FAQs on the SDR playbook

What should an SDR playbook contain?

Include the target customer, channel blend, touch timing, qualification tests, packet fields, scorecard and tool rules, and keep the whole thing short enough for a ten-minute read.

How does an SDR playbook differ from an AE playbook?

One guides the opening and screening of conversations; the other guides running the deal. The packet connects them.

Which channel should SDRs lead with?

Whichever one your own numbers favour. Run phone, email and social touches against the same list and compare accepted and held meetings.

Should a team adopt AI SDR tools?

Trial them next to a matched group, with a human checking each message. Until a sample and a control group are shown, treat vendor numbers as marketing.

How often should the playbook change?

Revisit it each quarter and adjust a single element at once, which lets you see what changed the outcome.