SaaS outbound sales is undergoing a structural change. Account executives, not sales development representatives, are increasingly the ones opening cold outbound conversations with target accounts. Salesloft’s decision to retire its dedicated SDR function and route outbound ownership to its AE team is the most visible instance of this, but the underlying pattern is broader. As buyers get better at filtering out low context first touches, the credibility gap between a junior researcher and a senior seller who can answer real product and commercial questions on the spot becomes the deciding factor in whether a cold outreach turns into a qualified conversation at all.
For RevOps leaders this is not primarily a headcount story. It is a pipeline maths, forecasting, and compensation design problem, and it touches nearly every system RevOps owns: routing rules, quota structures, CRM stage definitions, and the automation stack that used to exist mainly to support SDR volume. This post works through what changed, why the mechanism behind it holds up, and what RevOps needs to rebuild if account executives take over sourcing.
What the Salesloft SDR Decision Signals
Salesloft removed its standalone SDR function and folded outbound prospecting into the account executive role. Its leadership has been public about the reasoning: meetings sourced by AEs closed at a meaningfully higher rate than meetings handed off from SDRs, and the company judged that the credibility an AE brings to a first call was worth more than the extra dial volume a separate prospecting team could generate. Framed that way, the change was not a cost cut dressed up as strategy. It was a bet that buyer attention is scarce enough that the seller who opens the conversation should be the one who can actually answer it.
That reasoning does not automatically transfer to every SaaS company. Salesloft could make this move because its average contract value and sales cycle support AEs spending real hours on prospecting without starving their closing pipeline. A company selling a low price, high volume product with short cycles may not have that spare AE capacity, and simply removing the SDR layer without a volume replacement will leave gaps further up the funnel. The signal worth taking from Salesloft is not “cut your SDRs.” It is that buyers increasingly expect the first outbound touch to carry real substance, and any RevOps team should test that assumption against its own conversion data before restructuring around it.
Why Senior Sellers Convert Better on Cold Outbound
The mechanism is fairly specific. A prospect who picks up a cold call has usually already done some independent research, so the first substantive question they ask is rarely a scripted qualifier. It is a product fit, integration, or compliance question that requires a real answer, not a promise to “loop in someone from the team.” An SDR working from a discovery script has to defer that question, and the deferral itself signals inexperience to a buying committee that is already screening vendors on trust.
Consider a compliance heavy vertical such as healthtech or regulated financial services selling into the UK market. The first question a buying committee asks on an outbound call is often not about the product roadmap at all. It is about data handling: where records are stored, how access is controlled, and what happens under a subject access request. Organisations selling into these buyers benefit from having someone on the call who already understands the shape of that obligation, and the Information Commissioner’s Office publishes general guidance for organisations handling personal data (ico.org.uk/for-organisations). A rep who has to say “let me check and get back to you” loses momentum in exactly the moment the buyer is deciding whether the vendor is credible.
None of this is about the outbound tooling. AEs using the same sequencing and enrichment platforms as SDRs still convert better, because automation only scales whatever judgment is sending the message. A well targeted list run through automated sequencing gets more replies when the follow up questions are answered by someone who can negotiate scope on the spot, and that gap in execution, not access to better software, is what shows up in the conversion numbers.
RevOps Consequences for Forecasting and Capacity Planning
Once AEs own sourcing, the operational maths RevOps has relied on for years stops working as written. This is where the shift becomes a systems problem rather than a sales strategy debate.
Rebuilding the Pipeline Maths
Traditional pipeline coverage ratios assume a roughly fixed supply of SDR sourced meetings flowing into a fixed pool of AE closing capacity. Remove the SDR layer and that assumption breaks: the same AE headcount is now generating and closing pipeline simultaneously, so a coverage ratio calculated on historical SDR volume will overstate what the team can actually deliver. RevOps needs to rebuild the model around AE capacity rather than lead velocity, treating sourcing hours as a constrained input rather than an assumed constant.
Capacity Planning for AE Led Sourcing
In practice this means calendar blocking prospecting time separately from closing activity, and tracking how much of an AE’s week actually goes to each. A CRM that only records outcomes (meetings booked, deals closed) cannot tell RevOps whether an AE is under capacity because they are stretched too thin across both functions or because the sourcing motion itself is inefficient. Pipeline and sequencing tooling built into a CRM, such as HubSpot’s workflow and sequence objects (see developers.hubspot.com for the underlying API structure), can automate the repetitive parts of prospecting, but the capacity constraint is the AE’s time, not the software’s throughput, and no amount of automation removes that ceiling.
Redesigning Quota and Compensation When AEs Own Sourcing
Compensation plans built purely around closed won revenue create a specific problem once AEs own sourcing: they reward closing but say nothing about the sourcing effort that produced the pipeline in the first place. An AE facing that plan has a rational incentive to spend as little time as possible on prospecting and lean on inbound or existing warm accounts instead, which quietly reintroduces the exact reliance on inbound volume the restructure was meant to reduce.
A blended structure that gives partial credit for self sourced pipeline reaching a defined stage, alongside standard closing credit, keeps the incentive pointed at both halves of the job. The harder part is defining that stage objectively. If “self sourced pipeline” is credited the moment a call gets booked, AEs can inflate the count without doing real qualification, and stage definitions in the CRM lose their meaning as a forecasting signal. Tying sourcing credit to something verifiable, such as a completed meeting with a confirmed economic buyer and a documented next step, keeps the incentive honest and keeps the pipeline data usable for forecasting rather than just for quota tracking.
What Happens to SDRs When AEs Take Over Outbound
Moving outbound calling to AEs does not have to mean eliminating the SDR function everywhere. The role that changes is what SDRs are producing. Instead of dialling and booking meetings themselves, SDRs can own the signal layer that makes an AE’s first call worth taking: account research, product usage triggers, intent data, and org chart mapping, packaged so the AE walks into the conversation with something specific to reference rather than a cold introduction.
Other companies redirect SDR capacity towards event based qualification, account based marketing support for named target lists, or customer expansion signals inside the existing base, all of which use the same research and qualification skills without requiring the SDR to be the one opening the outbound call. The failure mode to watch for is cutting SDR headcount without redefining what remains: if the research and signal work simply disappears along with the calling responsibility, AEs end up doing their own list building on top of prospecting and closing, and selling time quietly shrinks even though quota attainment might look fine for a quarter or two before the gap shows up in pipeline quality.
Phased Model for Moving Outbound to AE Ownership
Restructuring outbound ownership in one move, across the whole AE team at once, is the riskiest way to test whether the Salesloft logic holds for a given company’s buyers. A staged rollout gives RevOps a way to check the conversion assumption against real data before it is locked into forecasting and compensation.
Phase 1: SDR Led Volume. The starting state for most SaaS teams: SDRs run the full funnel of cold outreach, and AEs only see meetings after qualification.
Phase 2: AE First Touch on Named Accounts. AEs take direct outbound ownership of a defined list of top tier target accounts, usually the ones with the highest deal complexity, while SDRs continue running broad volume prospecting for the rest of the funnel. This is the stage where a company can actually measure whether AE sourced meetings convert better for its own buyers, rather than assuming Salesloft’s result applies.
Phase 3: AE Owned Sourcing, SDR Support Roles. If the pilot data supports it, AEs take over outbound ownership across their full book of accounts, and SDRs shift into the research, signal, and expansion support roles described above.
Phase 4: Fully AE Led Pipeline. AEs own sourcing and closing end to end, with automation and enrichment tooling doing the volume work that SDRs previously handled by hand.
Related Equanax Resources
Frequently Asked Questions
Does shifting outbound to AEs mean every SaaS company should eliminate its SDR team?
Not necessarily. The right approach depends on deal complexity and how much spare capacity AEs actually have. High volume, low average contract value motions often still need a dedicated prospecting layer, and many companies repurpose SDRs into account research, signal gathering and expansion support rather than removing the function outright.
How does RevOps need to change forecasting once AEs own sourcing?
Pipeline coverage ratios and forecasting models built around SDR activity volume stop being reliable once AEs own sourcing. RevOps needs to model pipeline against AE capacity, splitting each AE’s week between prospecting and closing work rather than assuming unlimited bandwidth for both.
How should AE compensation change when AEs handle both sourcing and closing?
A compensation plan built purely around closed won revenue does not reward the sourcing effort and can push AEs towards warm or inbound pipeline. Blending partial credit for self sourced pipeline that reaches a defined, objective stage with standard closing credit keeps the incentive aligned with the new workload.
What should SDRs do if AEs take over outbound calling?
Many SDRs move into a signal layer role: building account research, tracking product usage triggers and intent data, and packaging that context so an AE’s first call already has something substantive to reference. Others move into event based qualification or customer expansion support.
Is the shift from SDRs to AEs only relevant to enterprise SaaS deals?
No. The credibility gap shows up fastest in enterprise buying committees, where deal complexity and compliance conversations demand real answers from the first call. Whether a mid market or smaller SaaS company should follow the same path depends on the same factors covered in the phased rollout: deal complexity, average contract value, and how much spare AE capacity actually exists.
For more on this, see more RevOps strategy posts, including SaaS Lifecycle Optimization: Onboarding, Payment Recovery & RevOps, Accelerating Enterprise AI Sales with Privacy-Preserving Security, and Simplifying SaaS Funnels: A RevOps Guide to Conversation-Driven Growth.
Leave a Reply