How do you write a GTM playbook for an ideal SDR in 2027?
PULSEKNOWLEDGE LIBRARY
To write a GTM playbook for an ideal SDR in 2027, define the target buyer's trigger events first, then map the SDR's weekly time budget to specific outreach plays across email, phone, and social channels. The playbook must codify qualification criteria, sequence cadence, and handoff rules so any SDR can execute predictably. It should be a living document, revised monthly based on conversion data.
What changes by company stage
The ideal SDR playbook for 2027 is not a one-size-fits-all document. A seed-stage startup with a founder-led sales motion needs a fundamentally different playbook than a Series C company with an established outbound engine. The differences are stark enough that copying a playbook from one stage to another will produce poor results. Understanding these stage-based differences is the first step in writing a playbook that actually gets used.
At the seed stage, typically pre-Series A with fewer than 15 employees, the SDR is often the first revenue hire. The playbook must be simple because the SDR is also helping define the ICP, build the initial list, and test messaging. The weekly volume target might be 60 to 80 personalized emails and 30 to 40 calls, but the bigger goal is learning what resonates. The playbook should include a daily standup with the founder to review which messages got replies and which accounts showed interest. The qualification criteria are loose — a prospect who responds to two touches and has a budget conversation scheduled is a qualified lead. The handoff is informal, often a Slack message to the founder.
By Series A, typically 15 to 40 employees with product-market fit assumed, the playbook needs more structure. The SDR role becomes more specialized, and the playbook should reflect that. Weekly volume targets might be 100 to 150 emails and 50 to 60 calls, with a mix of inbound and outbound. The playbook should include a defined ICP with firmographic and technographic filters, a messaging framework with three to four value propositions tied to specific pain points, and a qualification framework like BANT or MEDDIC simplified for the SDR level. The handoff to an Account Executive becomes a formal process with a shared Slack channel or a CRM status change.

At Series B and beyond, 40 to 100 employees, the playbook becomes a more comprehensive document. The SDR team might be five to ten people, so the playbook must ensure consistency. Weekly volume targets might be 150 to 200 emails and 60 to 75 calls, but the emphasis shifts from volume to quality. The playbook should include a detailed ICP with buying committee maps, a multi-channel sequence that spans 14 to 21 days, and a clear service-level agreement with the AE team. The playbook should also include a defined process for account selection, with the SDR working a specific number of target accounts per week rather than just a list of leads.
Enterprise companies with 100 or more employees and mature sales organizations face a different challenge. The playbook must account for complex buying committees, longer sales cycles, and the need for account-based strategies. An SDR at this stage might handle only 10 to 15 target accounts at a time, running deep, personalized plays that involve multiple stakeholders. The playbook should include detailed research templates, custom messaging for each persona within the account, and a clear escalation path when an account shows buying signals. The weekly volume target might be lower, but the quality bar is much higher.
The 2027 twist is that AI tools have changed the volume game. An SDR using AI-assisted personalization can send 200 to 300 emails per week without sacrificing quality, because the AI drafts the first version and the SDR edits it. The playbook should acknowledge this and set expectations accordingly. But the playbook must also warn against the trap of over-automation. Buyers in 2027 are more sophisticated and can spot generic AI outreach immediately. The playbook should include a rule: every email must contain at least one specific detail that could only come from a human reading the prospect's LinkedIn profile or company news.

Stage-by-stage playbook
The structure of the playbook itself should follow a consistent framework regardless of company stage. This framework ensures that the SDR knows exactly what to do on any given day, how to prioritize, and when to escalate. The following flowchart shows the core decision path an SDR follows when working a new account.
The playbook should begin with a section on account selection. This is where the SDR learns which accounts to prioritize and why. The section should include the firmographic filters, the technographic signals, and the trigger events that indicate a buying intent. For example, a company that just raised a Series B round, hired a new VP of Sales, or announced a new product line is showing signals that they might need the SDR's solution. The playbook should list the top ten trigger events to monitor, with instructions on how to set up alerts for each one.
The next section covers messaging. The playbook should include email templates for each stage of the sequence, but with a critical caveat: templates are starting points, not scripts. Each template should have placeholders for personalization, and the playbook should include examples of what good personalization looks like versus lazy personalization. A good example might reference a specific quote from the prospect's recent podcast appearance. A lazy example might just mention the company name. The playbook should also include phone scripts for the initial call, the follow-up call, and the breakthrough call when the SDR is trying to reach a gatekeeper.

The sequence section of the playbook is where the cadence is defined. In 2027, the old model of 10 to 12 touches over 30 days has evolved. Buyers expect a shorter, more intense burst followed by a longer nurture period. A typical sequence might be: Day 1 email, Day 2 LinkedIn connection request, Day 3 phone call, Day 5 second email with a new angle, Day 7 phone call again, Day 10 social engagement on a company post, Day 12 third email with a customer story, Day 15 breakup email. After the breakup email, the prospect moves to a monthly newsletter-style nurture that lasts for 90 days.
The qualification section is where the SDR learns how to determine if a prospect is worth the AE's time. The playbook should include the specific questions to ask, the responses that qualify, and the responses that disqualify. For example, a prospect who says they have a budget line item for this type of solution in the next quarter is qualified. A prospect who says they are just researching for next year is not. The playbook should also include a section on handling objections, with scripts for the five most common objections and guidance on when to push back versus when to accept the objection and move on.
The handoff section is the final piece of the playbook. This is where the SDR learns exactly what to do when a prospect is qualified. The playbook should include a checklist of information to gather before the meeting, a template for the handoff email or Slack message, and instructions for the pre-meeting briefing with the AE. The playbook should also define what happens if the AE does not respond to the handoff within a certain time frame — typically 24 hours — and the SDR needs to follow up.

Numbers that matter at each stage
A playbook without numbers is just a collection of suggestions. The ideal SDR playbook for 2027 must include specific, measurable targets that the SDR can track against. These numbers vary by company stage, but they provide the guardrails that keep the SDR focused on the right activities.
For a seed-stage company, the key numbers are: 60 to 80 personalized emails per week, 30 to 40 calls per week, 15 to 20 new accounts added to the pipeline per week, and a response rate target of 15 to 20 percent. The conversion rate from response to qualified meeting should be 20 to 30 percent, meaning the SDR should book 3 to 6 meetings per week. The playbook should include a simple tracking spreadsheet or a basic CRM dashboard that shows these metrics.
At Series A, the numbers scale up: 100 to 150 emails per week, 50 to 60 calls per week, 25 to 30 new accounts added, and a response rate target of 10 to 15 percent. The response-to-meeting conversion drops slightly to 15 to 25 percent because the volume is higher and the targeting is less precise. The SDR should book 5 to 8 meetings per week. The playbook should also include a target for the number of qualified leads passed to the AE, with a definition of what qualifies — typically a prospect with a confirmed budget, a timeline within 90 days, and authority or access to the authority.

Series B and later companies see volume targets of 150 to 200 emails and 60 to 75 calls per week, but the response rate target drops to 8 to 12 percent. The playbook should emphasize quality over quantity, with a focus on account selection. The SDR might add only 15 to 20 new accounts per week, but each account should be deeply researched. The booking target is 6 to 10 meetings per week, with a higher conversion rate from meeting to qualified opportunity because the qualification criteria are stricter.
Enterprise companies flip the model. The SDR works 10 to 15 target accounts at a time, running multi-threaded plays that involve multiple stakeholders. The email volume might be only 30 to 40 per week, but each email is deeply personalized. The call volume is 10 to 15 per week, focused on specific stakeholders. The response rate target is 25 to 35 percent because the research is so deep. The booking target is 2 to 4 meetings per week, but each meeting is with a senior decision-maker at a large account.

Beyond these activity metrics, the playbook should include efficiency metrics that help the SDR improve over time. The first is the personalization-to-response correlation. The playbook should instruct the SDR to track which emails got responses and analyze what made them effective. Was it the specific trigger event referenced? Was it the industry-specific example? Was it the timing? The SDR should review this weekly and adjust the approach.
The second efficiency metric is the time-to-response. The playbook should set a target of responding to any inbound lead within five minutes during business hours. In 2027, speed-to-lead is still one of the strongest predictors of conversion. A lead that gets a response within five minutes is 21 times more likely to convert than one that waits 30 minutes. The playbook should include a process for the SDR to check inbound leads regularly and respond immediately.
The third metric is the meeting-show rate. The playbook should track how many booked meetings actually happen. A show rate below 80 percent indicates that the qualification process is weak — the SDR is booking meetings with prospects who are not truly interested. The playbook should include a confirmation process: a reminder email 24 hours before, a confirmation call or text two hours before, and a clear process for rescheduling.

The fourth metric is the conversion rate from meeting to opportunity. This is the ultimate measure of qualification quality. If the AE is only converting 30 percent of SDR-booked meetings into opportunities, the SDR is booking too many unqualified meetings. The playbook should set a target of 60 to 70 percent conversion, and if the number falls below that, the SDR and AE should review the qualification questions and adjust.
The fifth metric is the pipeline contribution. The playbook should track how much pipeline revenue the SDR generates each month. A good target is 4 to 6 times the SDR's fully loaded cost. If the SDR costs $8,000 per month in salary and benefits, the pipeline contribution should be $32,000 to $48,000 per month. This metric helps the company understand the return on investment for the SDR role.
Decision framework
The playbook needs a decision framework that helps the SDR make judgment calls in real time. These are the moments that are not covered by a script — when a prospect says something unexpected, when a competitor is mentioned, or when the prospect asks a question the SDR does not know how to answer. The decision framework gives the SDR a process for handling these moments consistently.

The first decision point is when to stop pursuing an account. The playbook should define clear criteria for when an account is dead. These might include: no response after the full sequence plus two follow-up attempts, a clear "not interested" from the prospect, or a company announcement that indicates the budget is frozen. The SDR should not spend more than 30 days on a single account without a positive signal. The playbook should include a rule: if the prospect has not responded to any touch in 15 days, the account moves to long-term nurture, and the SDR starts working a new account.
The second decision point is when to escalate to the AE. The playbook should define the qualification criteria clearly and instruct the SDR to escalate as soon as the criteria are met. Waiting too long risks losing momentum. The playbook should include a rule: if the prospect expresses a clear pain point, has a budget, and wants to see a demo, the SDR should book the meeting immediately, even if the sequence is not complete.
The third decision point is how to handle a prospect who wants to talk to the AE before the SDR qualification is complete. This happens when the prospect is senior and does not want to talk to an SDR. The playbook should instruct the SDR to honor the request but to gather as much information as possible before the handoff. The SDR should ask the prospect for their key priorities, the timeline, and the budget range, then pass that information to the AE in the handoff.

The fourth decision point is how to respond to a prospect who says they are already using a competitor. The playbook should include a competitive response framework. The SDR should not badmouth the competitor but should ask questions to understand what the prospect likes and dislikes about the current solution. The playbook should provide three to four value propositions that differentiate the company's solution, and the SDR should use these to position the company as a better alternative.
The fifth decision point is when to use a different channel. The playbook should default to email, phone, and LinkedIn, but it should also include guidance on when to try other channels. If the prospect is active on Twitter, a thoughtful public reply to their post might get their attention. If the prospect has a public speaking engagement, a congratulatory note after the event could be the breakthrough. The playbook should encourage the SDR to be creative but should also set boundaries on what is acceptable.
The sixth decision point is how to handle a prospect who is interested but says the timing is wrong. The playbook should instruct the SDR to ask follow-up questions to understand the timeline. If the prospect says they will revisit in six months, the SDR should set a reminder and add the prospect to a nurture campaign. If the prospect says the timing will never be right, the SDR should accept the answer and move on.

The following flowchart shows how the SDR should decide between continuing to pursue an account, moving it to nurture, or discontinuing entirely.
The decision framework should also include guidance on when to break the rules. The playbook is a starting point, not a cage. If an SDR discovers a new approach that works — a new email angle, a different call time, a creative use of a channel — they should document it and share it with the team. The playbook should be updated monthly to incorporate the best practices that emerge from the team's experience.
The final part of the decision framework is the weekly review process. The playbook should include a template for a weekly self-assessment where the SDR reviews their numbers, identifies what worked and what did not, and sets goals for the next week. The SDR should also meet with their manager or the AE team lead to review the pipeline and adjust the approach. This weekly review is the mechanism that turns the playbook from a static document into a living system.
Related questions
What tools does an ideal SDR use in 2027?
An ideal SDR in 2027 uses a CRM for tracking, a sales engagement platform for sequences, LinkedIn Sales Navigator for research, and AI-assisted personalization tools. The key is integration — all tools should sync so the SDR has a single view of each prospect.
How long should an SDR sequence be?
A typical sequence runs 14 to 21 days with 8 to 12 touches across email, phone, and social. After the sequence ends without a response, the prospect moves to a monthly nurture campaign for up to 90 days.
What is the ideal SDR to AE ratio?
The ideal ratio is typically 1 SDR to 1 AE at early stages, shifting to 2 SDRs per AE as the company grows and the AE spends more time in discovery and demos.
How do you measure SDR performance?
Key metrics include emails sent, response rate, meetings booked, meeting show rate, and conversion from meeting to opportunity. The most important metric is qualified pipeline generated, typically 4 to 6 times the SDR's fully loaded cost.
FAQ
What is the most important section of an SDR playbook?
The qualification criteria section is the most important because it determines which prospects move forward. If the qualification criteria are too loose, the AE wastes time on unqualified meetings. If they are too strict, the SDR misses good opportunities. The playbook should include specific questions and the responses that qualify or disqualify, and it should be reviewed monthly with the AE team to ensure alignment.
How often should an SDR playbook be updated?
A playbook should be reviewed monthly and updated quarterly. The monthly review focuses on messaging and sequence adjustments based on response data. The quarterly review looks at the broader strategy, including ICP changes, new channels, and the qualification framework. The playbook should also be updated whenever there is a significant change in the product, the market, or the competitive landscape.
Should the SDR playbook include email templates?
Yes, but with a caveat: templates are starting points, not scripts. The playbook should include templates for each stage of the sequence, but it should also include a personalization checklist that ensures every email has at least one specific detail about the prospect or their company. In 2027, generic AI-written emails are easily spotted and ignored.
How do you handle a prospect who asks for pricing before the demo?
The playbook should instruct the SDR to acknowledge the question and defer the detailed answer to the AE. The SDR can share a general range if the company allows it, but the goal is to get the prospect to the demo where the AE can frame the pricing in the context of the solution's value.
What is the role of AI in the 2027 SDR playbook?
AI assists with research, personalization drafts, and sequence optimization, but the SDR still owns the relationship. The playbook should set clear rules: AI can draft the first version of an email, but the SDR must add a human insight. AI can suggest the best time to call, but the SDR must be present and engaged on the call.
How do you write a playbook for an SDR with no prior sales experience?
Focus on the fundamentals: account research, messaging, and qualification. Include detailed examples of good emails and calls, and provide a checklist for every step. The playbook should also include a 30-day ramp plan that starts with shadowing, moves to assisted outreach, and ends with independent execution.
Sources
HubSpot - Sales Playbook Template
Salesforce - Sales Playbook Best Practices
Harvard Business Review - Sales Process Design
LinkedIn Sales Solutions - SDR Best Practices
Related on PULSE
- Building a multi-channel outbound motion that scales
- The changing role of the SDR in an AI-assisted sales stack
- Qualification frameworks that reduce AE friction
- Designing a sales development compensation plan
- From SDR to AE: building a career progression path
- Measuring pipeline contribution beyond meetings booked









