Salesloft’s decision to shift weight away from a dedicated SDR to AE handoff and toward AE-owned pipeline generation is not an isolated org chart tweak. It is one data point in a wider pattern across SaaS go to market teams, where the classic split between prospecting and closing is being questioned on the basis of where deals actually stall. For a RevOps or sales operations lead, the useful question is not “should we copy Salesloft” but “where in our own funnel does ownership change hands, and what does that handoff cost us.”
This piece works through the mechanics of that handoff, what changes operationally when an AE owns a deal end to end, how to decide which structure fits your business, and the compensation, tooling and rollout sequencing that make the transition survivable rather than chaotic.
Why Salesloft’s Restructuring Signals a Wider SaaS Shift
Salesloft builds sales engagement software, so a change to how it structures its own sales org carries a certain amount of “eat your own cooking” weight. But the underlying pressure is not specific to one vendor. As SaaS buying cycles have lengthened and stakeholder counts have grown, the classic two person relay (an SDR books a meeting, an AE takes it from there) introduces a context reset at exactly the moment a buyer expects continuity. The prospect has already explained their problem once, to a person who then disappears from the deal.
That reset is a design choice, not a law of nature. It made sense when SDR teams were cheap to scale and outbound volume was the binding constraint on pipeline. It makes less sense once tooling can generate and qualify volume without a person dialling every number, and the binding constraint shifts to conversion quality further down the funnel. Restructuring toward AE ownership is, functionally, a response to that constraint moving.
Where the SDR to AE Handoff Actually Loses Deals
The handoff itself is where most of the damage happens, and it is worth being specific about the mechanism rather than treating it as vague friction. Three things typically go wrong. First, discovery gets repeated: the AE re-asks questions the SDR already covered, because CRM notes are thin, inconsistently logged, or written for the SDR’s own memory rather than for a stranger picking up the file. Second, momentum decays: there is almost always a gap between a booked meeting and the AE’s first live conversation, and buyer intent that peaked during the SDR call cools in that window. Third, accountability splits: when a deal stalls, it is genuinely unclear whether the SDR mis-qualified it or the AE mishandled it, so the feedback loop that should improve either role gets diluted.
None of these are arguments that SDRs are inherently inferior salespeople. They are arguments that a two person relay has a structural cost at the exact seam where ownership changes, and that cost scales with deal complexity. A five minute qualification call for a self-serve tool has almost nothing to lose at the handoff. A six month enterprise evaluation with four stakeholders has a great deal to lose.
What Changes When an AE Owns the Full Deal Cycle
When an AE originates their own pipeline, the first conversation and the closing conversation are held by the same person with the same memory of what was actually said. That continuity changes buyer behaviour in a few concrete ways. Objections raised early get carried forward and addressed with evidence by the time a proposal lands, rather than resurfacing as a surprise in a later stage because nobody logged them. The AE can also sequence their own outreach around what they already know about an account, rather than working a list of meetings that someone else decided were worth their time.
There is a cost side to this too, and it should not be glossed over. AE-led ownership means the AE’s calendar now carries prospecting hours that used to belong to someone else, and prospecting is a different skill set from negotiation and closing. Not every strong closer is a strong self-sourcer, and forcing the switch without support (better intent signals, cleaner target account lists, less manual list building) simply moves the bottleneck from the handoff into the AE’s own week.
The New Job of the SDR: From Volume to Intelligence
A move toward AE-led origination does not require eliminating the SDR function; it requires deciding what SDRs are for once volume outreach is partly automated. The more durable version of the role looks less like a dialler operator and more like an account researcher: building out the org chart for a target account, flagging trigger events (a funding round, a leadership change, a relevant job posting), and handing an AE a briefing rather than a meeting slot.
This reframing matters for career pathing as much as for output. SDR seats built purely around call volume tend to have high turnover, because the work is repetitive and the growth path unclear. SDR seats built around account intelligence and enablement give people a skill set (research, segmentation, signal interpretation) that transfers directly into an AE or RevOps career track, which makes the role easier to hire and retain for.
Choosing a Structure: SDR-Fed, Hybrid, or Full AE-Led
There is no single correct structure here; the right answer depends mostly on average contract value and how many stakeholders a typical deal involves. Three broad patterns cover most SaaS businesses.
A low contract value, high velocity product with a short buying cycle generally still benefits from an SDR-fed model: the handoff cost is small relative to deal size, and volume matters more than continuity. A mid-market product with moderate deal complexity often does best on a hybrid, segmented approach: SDRs handle a defined tier of accounts or inbound triage, while AEs self-source within their own named or target accounts. A high contract value, multi-stakeholder enterprise motion is where full AE-led ownership tends to pay for itself, because the continuity benefit compounds across a longer, more relationship-dependent cycle.
The diagram below sets out that decision as three branches from a single starting question, which is a useful exercise to run literally, segment by segment, rather than applying one structure across an entire book of business.
Rebuilding Compensation and Quota for AE-Led Pipeline
Comp plans built for a two person relay assume the AE’s job starts at a booked meeting. Ask an AE to also generate that meeting and their existing quota becomes unreachable in the same hours, unless something else in the plan moves. Two levers tend to do the real work here. The first is a prospecting activity component in variable pay, distinct from the closing component, so self-sourcing is rewarded on its own terms rather than treated as unpaid overhead layered on top of an unchanged closing target. The second is quota relief during the transition period, because pipeline generated by a newly self-sourcing AE takes time to reach the same close rate their previously SDR-fed pipeline achieved; ramping the number gradually avoids punishing people for a structural change leadership decided to make.
Skipping this step is the fastest way to make an otherwise sound restructuring fail. Reps optimise for what they are paid on, and a plan that still implicitly assumes someone else is filling the top of the funnel will produce exactly that behaviour: AEs quietly deprioritising self-sourcing in favour of whatever inbound trickles in, regardless of what leadership announced in the all hands.
The RevOps Infrastructure an AE-Led Motion Depends On
An AE who owns a deal end to end still needs the CRM to carry that ownership cleanly through every stage, from first touch to signature, without a manual reassignment step that introduces its own error rate. That means pipeline stages, ownership fields and routing rules need to be defined around the new model rather than inherited from the old SDR to AE handoff structure, where a lead object typically converted and reassigned at a fixed point. Object and pipeline configuration matters more here than most teams expect; both HubSpot’s and Salesforce’s platforms document how ownership, routing and stage definitions are modelled at the object level, and getting that model wrong is a common source of deals silently sitting with the wrong owner (see HubSpot’s developer documentation and Salesforce Help).
Scope creeps quickly once you start mapping this properly: pipeline stages, the automation workflows that move records between them, and the dashboards leadership actually looks at each need to be redefined together, not patched individually. One Equanax deployment mapped that exact problem to 6 pipeline stages, 13 automation workflows, and 3 dashboards, which is a reasonable order of magnitude for a mid-sized B2B SaaS team restructuring around AE ownership rather than a trivial config change.
Automation’s Real Role: Replacing Tasks, Not Judgement
The case for AE-led origination gets much stronger once genuinely repetitive tasks are automated rather than assumed away. List building, initial enrichment, and multi-step sequencing can run through workflow automation tools without a human triggering each step; platforms such as n8n document how these sequences chain data between a CRM, an enrichment source and an outreach tool as a repeatable workflow (see n8n’s documentation). What automation should not be asked to do is judge which account is worth a personal, researched approach versus a templated one; that call still benefits from a person who understands the account.
There is a compliance dimension that gets skipped surprisingly often when outreach volume scales through automation. UK direct marketing and cold outreach are governed by data protection rules that apply regardless of how the message was generated or sent, and it is the sending organisation’s responsibility to stay within them; the ICO publishes guidance for organisations on this (see the ICO’s guidance for organisations). Restructuring the sales motion is a reasonable moment to also review whether outreach volume and personalisation practices still sit comfortably within those rules, rather than treating compliance as a fixed assumption from the old SDR process.
A Sequenced Rollout Plan for Moving to AE-Led Prospecting
Teams that try to flip the whole motion in one announcement tend to lose weeks to confusion about who owns what. A staged sequence holds up better in practice. Start by mapping exactly where deals currently lose momentum in the handoff, using CRM stage timestamps rather than anecdote, so the case for change is grounded in your own funnel rather than borrowed from Salesloft’s. Next, pilot the new model on a single segment (one territory, one product line, or one AE cohort) before touching comp plans for the whole team. Once the pilot has enough closed cycles to be meaningful, rebuild the comp and quota structure based on what that pilot actually showed about ramp time, then redeploy the remaining SDR capacity into the research and enablement role described earlier rather than eliminating it outright. Only after those three stages hold should the model scale to the rest of the sales org, with dashboards in place to catch stage slippage early.
Running the stages out of order (rebuilding comp before piloting, for instance) is a common reason these transitions stall, because the organisation ends up designing pay around a guess rather than evidence.
Risks and Failure Modes to Watch For
The most common failure is quota overload without infrastructure support: an AE told to self-source without better target lists, cleaner intent signals or protected prospecting time simply produces less pipeline overall, because the hours have to come from somewhere and closing activity is usually what gets sacrificed first. A second failure mode is treating SDRs as a cost to eliminate rather than a function to redeploy; teams that cut the role entirely often rediscover, a couple of quarters later, that nobody is doing the account research an AE-led motion still depends on. A third, quieter risk sits in the CRM itself: if pipeline stage and ownership logic are not rebuilt for the new model, reporting will keep describing a handoff process that no longer exists, and leadership ends up making decisions on data that reflects the old structure rather than the new one.
Related Reading
Frequently Asked Questions
Why does the SDR to AE handoff cause deals to slow down?
Because ownership changes hands at exactly the point buyer momentum is highest. The new owner (the AE) often has to re-ask questions the buyer already answered, and there is usually a gap between a booked meeting and the AE’s first live conversation, both of which let engagement cool.
Does moving to an AE-led model mean getting rid of SDRs?
Not necessarily. The stronger version of the transition redeploys SDR capacity into account research and enablement work, briefing AEs on target accounts, rather than eliminating the role. Career pathing and retention both tend to improve when the role shifts from pure call volume to intelligence work.
How should compensation change when AEs start self-sourcing pipeline?
Two changes usually matter most: adding a prospecting activity component to variable pay so self-sourcing is rewarded on its own terms, and giving quota relief during the ramp period while self-sourced pipeline reaches the close rates the old SDR-fed pipeline achieved.
What is the biggest risk when restructuring toward AE-led prospecting?
Quota overload without infrastructure support. Asking AEs to self-source without better target lists, cleaner intent signals or protected prospecting time tends to reduce total pipeline, because the extra hours usually come out of closing activity.
What should change in the CRM before rolling out an AE-led motion?
Pipeline stages, ownership fields and routing rules need to be rebuilt around the new model rather than inherited from the old SDR to AE handoff structure, otherwise reporting keeps describing a process that no longer exists.
For more on this, see more on lead generation and outreach, including Boost SaaS Cold Outreach with Yes/No CTAs for Higher Reply Rates, Apollo.io Review: Comprehensive Apollo.io Analysis for 2026, and SaaS Growth Strategies: RevOps, Cold Email & LinkedIn Tactics.
Leave a Reply